Drive devices and APIs from their W3C Thing Description. You gate every operation.
Connect Runs on your machine
claude mcp add thingctx -e THINGCTX_POLICY=<THINGCTX_POLICY> -e THINGCTX_APPROVE_WHEN=<THINGCTX_APPROVE_WHEN> -e THINGCTX_FS_ROOT=<THINGCTX_FS_ROOT> -- uvx thingctx==0.2.2
{
"mcpServers": {
"thingctx": {
"command": "uvx",
"args": [
"thingctx==0.2.2"
],
"env": {
"THINGCTX_POLICY": "<THINGCTX_POLICY>",
"THINGCTX_APPROVE_WHEN": "<THINGCTX_APPROVE_WHEN>",
"THINGCTX_FS_ROOT": "<THINGCTX_FS_ROOT>"
}
}
}
}
{
"mcpServers": {
"thingctx": {
"command": "uvx",
"args": [
"thingctx==0.2.2"
],
"env": {
"THINGCTX_POLICY": "<THINGCTX_POLICY>",
"THINGCTX_APPROVE_WHEN": "<THINGCTX_APPROVE_WHEN>",
"THINGCTX_FS_ROOT": "<THINGCTX_FS_ROOT>"
}
}
}
}
{
"servers": {
"thingctx": {
"type": "stdio",
"command": "uvx",
"args": [
"thingctx==0.2.2"
],
"env": {
"THINGCTX_POLICY": "<THINGCTX_POLICY>",
"THINGCTX_APPROVE_WHEN": "<THINGCTX_APPROVE_WHEN>",
"THINGCTX_FS_ROOT": "<THINGCTX_FS_ROOT>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
THINGCTX_POLICYOptional | What the agent may do: read-only | full. |
THINGCTX_APPROVE_WHENOptional | When the agent asks before acting: declared | destructive | all | never. |
THINGCTX_FS_ROOTOptional | Sandbox directory for the filesystem Thing. Unset = refuse every filesystem call. |
Details
| Package | [email protected] (PYPI, stdio) |
| First published | 26 Jul 2026 |
| Last updated | 26 Jul 2026 |
| Registry name | com.thingctx/thingctx |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
