Seam MCP Server

What is Seam MCP Server?

Seam MCP Server is Seam's official, free documentation server for AI coding assistants: a public, read-only MCP endpoint that gives Claude, Cursor, VS Code and other clients the Seam docs, API reference and device catalog. No API key or sign-in is needed.

Seam is an API for connecting and controlling smart locks, thermostats, access control systems and other building devices from many manufacturers through one integration. Developers building on Seam need accurate details: which endpoints exist, which lock models a provider supports, how access codes or Connect Webviews work. The Seam MCP server puts that documentation inside the assistant, so the code it writes is based on current docs rather than memory. It does not control devices or touch your Seam workspace.

How to use Seam MCP Server?

There is nothing to install and no credentials to configure. The server URL is:

https://mcp.seam.co/mcp

It uses Streamable HTTP and needs no authentication. The /mcp path is required.

Claude Code

Seam's docs give this command:

claude mcp add --transport http seam https://mcp.seam.co/mcp

Claude Desktop and claude.ai

Open Settings > Connectors, click Add custom connector, give it a name such as "Seam" and enter https://mcp.seam.co/mcp. There is no sign-in step.

Cursor

Seam offers a one-click "Install in Cursor" button on its MCP page, or add this to .cursor/mcp.json in your project:

{
  "mcpServers": {
    "seam": {
      "url": "https://mcp.seam.co/mcp"
    }
  }
}

VS Code

Add this to .vscode/mcp.json in your project:

{
  "servers": {
    "seam": {
      "type": "http",
      "url": "https://mcp.seam.co/mcp"
    }
  }
}

Other clients

Seam also documents Windsurf (serverUrl in ~/.codeium/windsurf/mcp_config.json), Codex (codex mcp add seam --url https://mcp.seam.co/mcp) and ChatGPT Desktop with Developer Mode enabled.

Key features of Seam MCP Server

• Official server run by Seam; free and public.
• No API key, account or OAuth flow: add the URL and start asking.
• Read-only by design: it cannot unlock doors, create access codes or change anything in a Seam workspace.
• Semantic search across all Seam documentation, including guides for specific device brands.
• Direct lookups in the documented Seam API, returning compact spec entries for the endpoints you need.
• Covers the supported-device catalog (smart locks, thermostats, access systems) with manufacturer details.
• Ships prompts with supporting files that an agent can load and follow for multi-step tasks.

Seam MCP Server tools

Our probe of the live server returned seven tools in three groups:

• Documentation: search_docs runs a semantic search across all Seam docs, including supported device models and their manufacturers. get_docs fetches full pages by path glob: one exact path for a single page, or a wider pattern to read up to 20 pages.
• API reference: search_api searches the documented Seam API and returns lightweight entries with stable IDs (pass query="*" to list every entry). get_apis returns the detailed spec nodes for the IDs you pick.
• Prompts: search_prompts finds prompts by metadata, get_prompt loads one by name, and get_prompt_context loads that prompt's supporting files before the agent acts on it.

Use cases of Seam MCP Server

• First integration: "Show me how to unlock a door with the Seam API in Python."
• Account setup questions: "How do I create an API key in Seam?"
• Device coverage checks: "What access control systems does Seam support?" or "Does Seam support Aqara locks?"
• Endpoint details: ask the assistant to look up the parameters and response of a specific access code or thermostat endpoint before writing the call.
• Code review: have the assistant check existing Seam integration code against the current API spec.

Troubleshooting Seam MCP Server

• Tools are not showing up: restart your editor or reload the window after adding the configuration.
• Connection errors: make sure the URL is exactly https://mcp.seam.co/mcp; the /mcp path is required.
• Slow first answer: Seam notes the first query may take a few seconds while the server warms up; later queries are fast.
• You want to control devices: this server only reads documentation. Device actions go through the Seam API with your own API key.