Skip to main content
The hosted server is https://thingery.dev/mcp. Pick your client: it finds the sign-in flow on its own, you approve once in the browser, and its tokens rotate automatically. You can review and revoke connected apps at thingery.dev/apps. A self-hosted instance works the same way at its own URL.

MCP Inspector

Choose the Streamable HTTP transport, enter https://thingery.dev/mcp and connect. The Inspector offers the sign-in.

Use an API key instead

Scripts, CI and clients without OAuth send an API key as a bearer token. See Authentication to get one.
Leave out the Authorization header to use only the public tools, such as search.

Local server over stdio

The thingery npm package also runs as a local stdio server against your own Postgres. See Self-hosting.

Plain HTTP

No client is needed. List the tools:
The accept header is required by the transport; without it the server answers 406.

Machine discovery

  • llms.txt: the endpoint and tool reference for language models.
  • /.well-known/agents.json: the agent capabilities manifest.
  • The server is listed in the official MCP registry as io.github.thingery/thingery.