MCP Tools DirectoryAbout this integration
Drive devices and APIs from their W3C Thing Description. You gate every operation.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- unknown
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.2.2
- Package
- thingctx
- Last compatibility test
- Not independently tested
Connect your agent
thingctxAuthentication and prerequisites depend on each supplied Thing Description and optional transport extras, so they remain unknown rather than being flattened to one method. The package and described systems were not executed.
Capabilities: Project W3C Thing Descriptions into agent tools, Route calls across local, HTTP, MQTT, Redis, and extensible transports, Apply per-operation approval and authorization policies
Connected profiles
Additional details
com.thingctx/thingctx
Source ↗ · Checked 2026-09-170.2.2
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17thingctx
Source ↗ · Checked 2026-09-200.2.3
Source ↗ · Checked 2026-09-20thingctx-mcp is a generic local MCP bridge serving a registry of descriptions; a static description path, approval policy, and any per-Thing secrets can be configured before launch.
Source ↗ · Checked 2026-09-20Authentication varies per described Thing: nosec descriptions need no secret, while the MCP bridge can bind environment secrets named THINGCTX_TOKEN_; other optional providers are transport-specific.
Source ↗ · Checked 2026-09-20Run thingctx-mcp with a path or URL for the description registry; the reviewed existing listing remains stdio with no endpoint.
Source ↗ · Checked 2026-09-20Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-20