Connect the shelf to your agent

TinyTools speaks MCP over Streamable HTTP. Point any harness at one endpoint and it gets every tool on the shelf — with new tools appearing automatically, no reinstall. Same key works for the HTTP API.

First, get your key

The MCP server is a Pro feature. Open your dashboard, copy your key (tt_live_…), and paste it wherever you see <YOUR_KEY> below. The key stops working if your Pro pass lapses and resumes the moment you renew — you don't need a new one.

Claude Code

Run this once. It registers the server for every project.

shell

claude mcp add --transport http tinytools \
  https://tinytools.pro/api/mcp \
  --header "Authorization: Bearer <YOUR_KEY>"

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project), then enable tinytools in Settings → MCP.

json

{
  "mcpServers": {
    "tinytools": {
      "url": "https://tinytools.pro/api/mcp",
      "headers": { "Authorization": "Bearer <YOUR_KEY>" }
    }
  }
}

Claude Desktop

Desktop connects through the mcp-remote bridge (it forwards your key over the HTTP transport). Edit Settings → Developer → Edit Config and add:

json

{
  "mcpServers": {
    "tinytools": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://tinytools.pro/api/mcp",
        "--header",
        "Authorization: Bearer <YOUR_KEY>"
      ]
    }
  }
}

Restart Claude Desktop; the tools appear under the connectors menu.

Zed & other harnesses

Any app that runs a command-based (stdio) MCP server can use the same mcp-remote bridge. In Zed, add it as a custom context server in settings.json; the command is:

shell

npx mcp-remote https://tinytools.pro/api/mcp \
  --header "Authorization: Bearer <YOUR_KEY>"

Field names differ between apps, but the command, args, and the Authorization header are always the same.

Wiring it by hand

If your client speaks MCP directly, these are the only facts you need:

Endpoint: https://tinytools.pro/api/mcp
Transport: Streamable HTTP (no SSE)
Auth: Authorization: Bearer <YOUR_KEY> on every request
On failure: 401 if the key is missing, invalid, or the Pro pass has lapsed

Prefer raw HTTP?

Every tool is also a plain JSON endpoint at POST /api/v1/<operation> with the same Authorization: Bearer key. See the operation index and the OpenAPI spec. Full API docs are coming soon.