Skip to main content
The connector is a remote MCP server at:
It uses the Streamable HTTP transport and OAuth 2.1 sign-in. No API key is involved — every client below opens a browser window where you sign in with your Montra account and pick a workspace. See Authentication for how that works.

​
Claude (claude.ai and desktop)

  1. Open Settings → Connectors and choose Add custom connector.
  2. Name it Montra and enter https://montra.com/api/mcp as the URL.
  3. Click Connect, sign in with your Montra account, and choose the workspace this connection should act in.
The Montra tools then appear in Claude’s tool menu for new chats.

​
Claude Code

Add the server, then authenticate from inside a session:
Start claude and run /mcp — select montra and follow the browser sign-in. After the consent screen the tools are available as mcp__montra__*.

​
Cursor

Add the server to ~/.cursor/mcp.json (or the project’s .cursor/mcp.json):
Cursor prompts you to authenticate the first time it connects.

​
Other MCP clients

Any client that supports remote MCP servers with the Streamable HTTP transport and OAuth 2.1 authorization can connect. Point it at https://montra.com/api/mcp; the server advertises its authorization server through the standard protected-resource metadata at:
Clients that implement the MCP authorization spec (PKCE + dynamic client registration) will discover everything else from there.

​
Verify the connection

Ask your agent to call get_workspace. It returns the name and id of the workspace the connection is bound to — a quick confirmation that sign-in and workspace binding both worked.
Requests without a valid token get a 401 with a WWW-Authenticate challenge pointing at the metadata URL above. That is the protocol working as intended — it is how clients discover where to send you for sign-in, not an outage.