Skip to main content
Seam MCP The Seam MCP server gives your assistant current documentation, API schemas, and implementation and troubleshooting skill packs. Connect with OAuth to also read or manage workspace resources within the permissions you approve. Use the authenticated endpoint by default with an OAuth-capable MCP client: No Seam API key is needed in your MCP configuration. Sign-in identifies you; workspace permission consent determines which API requests your assistant can execute. Choose Viewer (product.read) for read-only access.
Already using Seam MCP? Replace the existing connection instead of adding a duplicate. See Update an Existing Installation for Claude and Codex commands and client restart instructions.

​
Connect From Claude Code

Run this command from your terminal:
Open /mcp inside Claude Code, select seam, and complete browser sign-in. Reconnect or start a new session after signing in. Alternatively, merge this entry into your Claude Code MCP configuration, then authenticate through /mcp:

​
Connect From Codex

Run these commands, then complete browser sign-in:
Restart your Codex session and use /mcp to check the available tools. See Seam for Codex for configuration alternatives.

​
Connect From Claude.ai or Claude Desktop

  1. Open Customize → Connectors in Claude.
  2. Select + Add → Add custom connector.
  3. Name the connector Seam and enter https://mcp.seam.co/mcp/authenticated.
  4. Add the connector and complete the OAuth browser sign-in.
  5. Enable Seam in a new conversation.
Your organization may require an owner to add the connector. See Claude’s current connector instructions. For Cursor, VS Code, Windsurf, and ChatGPT, see the client setup examples.

​
Verify Workspace Access

After signing in, check that api_request appears alongside the discovery tools. Ask your assistant to list your accessible workspaces using a read-only request. If Seam returns a permission-consent link, open it, choose the intended scope and Viewer permissions, approve, and retry. Tell your assistant which workspace to use. Device changes require the corresponding write permissions. Signing in alone does not grant unrestricted access. See Authorize Workspace Access.

​
Optional: Documentation Without Sign-In

Use https://mcp.seam.co/mcp instead if you only want public documentation, API references, and skill packs. Skip OAuth login. This endpoint needs no account or Seam API key, does not automatically prompt for sign-in, and does not expose api_request or access private workspace resources.

​
What You Can Ask

  • “Find the current API parameters for unlocking a Schlage Encode and explain how to check the action result.”
  • “What’s the difference between an access code and an Access Grant?”
  • “Load the implementation guide that fits my application’s framework.”
  • “List my accessible workspaces without changing anything.”
  • “Use the troubleshooting skill to investigate why device <device_id> in workspace <workspace_id> is offline.”
The last two examples require authenticated workspace access.

​
Available Tools

The default authenticated connection exposes the seven discovery tools plus api_request. Agent-specific connections can expose fewer tools; inspect your client’s current tool listing. Your assistant uses search_api → get_apis → api_request to inspect or manage resources. api_request supports reads and writes; a Viewer grant enforces read-only access. The other seven tools read public information and are also available anonymously. See the complete tool inventory for arguments and usage.

​
Investigate an Incident

The public MCP includes a read-only troubleshooting skill pack for device and connected-account health, access grants, access codes, and API or MCP authentication failures. Ask your assistant to troubleshoot a concrete incident with the workspace ID and affected resource ID, or explicitly request search_prompts with match: {"task": "troubleshooting", "output": "direct"}. The instructions are public; inspecting live workspace resources requires authenticated access. Choose Viewer to enforce read-only API access. The skill recommends fixes and prepares a support handoff when evidence is insufficient, without changing resources or submitting a ticket. See Troubleshoot with a Skill Pack for example prompts, supported playbooks, explicit loading instructions, and structured JSON output.

​
Troubleshooting

  • Only documentation tools appear — Confirm the URL ends in /mcp/authenticated, complete OAuth sign-in, reconnect, and start a new conversation. Replace any old anonymous entry.
  • API access is denied after sign-in — Complete the permission-consent link returned by Seam and retry with the intended workspace. See MCP troubleshooting for other connection errors.
  • Empty search results — If search_docs returns nothing, broaden your query. Use Seam API resource names (for example, access_codes) rather than SDK-specific method names, and use generic capability terms (for example, “mobile keys”) when searching for devices.
  • Connection refused — Confirm that your network allows outbound HTTPS to mcp.seam.co. Some corporate firewalls block custom MCP endpoints.

​
Support

For questions or issues with the Seam MCP server, contact support@seam.co.