Skip to main content

​
OAuth sign-in

The connector authenticates with OAuth 2.1: PKCE, dynamic client registration, and standard discovery. When an MCP client connects for the first time it is redirected to Montra, where you sign in with your normal Montra account. There are no API keys to create or store — the client ends up holding a short-lived access token for your user, refreshed automatically. Discovery works the standard way: the server publishes protected-resource metadata at https://montra.com/.well-known/oauth-protected-resource, which names the authorization server; unauthenticated requests to /api/mcp return a 401 whose WWW-Authenticate header points at that metadata. Compliant clients handle the whole flow without configuration.

​
Workspace binding

During sign-in, Montra shows a consent screen where you choose exactly one workspace. That choice is recorded per connection — keyed by your user and the OAuth client — so:
  • Your Claude connection and your Cursor connection can be bound to different workspaces.
  • Everyone on a team binds their own connections; nothing is shared implicitly.
Every tool except get_document_by_share_url operates strictly inside the bound workspace. Documents you can technically reach as a user — for example, ones shared with you from another workspace — read as not found through the connector, because the connection was consented to one workspace only. Share links are the deliberate exception: a pasted link names one specific resource, so the share tool resolves it regardless of the binding. The binding is checked on every request. If your membership in the bound workspace is revoked, or the workspace is deleted, tool calls start failing with a message asking you to reconnect.

​
Switching workspaces

Reconnect the connector (remove and re-add it in your client, or use the client’s re-authenticate action) and pick a different workspace on the consent screen. The new choice replaces the old binding for that connection.
If your account belongs to exactly one workspace, a connection that predates the consent screen still resolves to it automatically. With more than one workspace, an unbound connection returns an error asking you to reconnect and choose.

​
Revoking access

Disconnecting the connector in your MCP client stops it from making further requests. Because access rides on your Montra sign-in, anything that ends your Montra session — or removal from the workspace — also cuts the connection off.

​
What the connector can do as you

The connector acts as your user, through the same row-level security rules as the Montra apps. It can never see more than you can. Writes are real, though: update_ticket, update_document, and delete_ticket overwrite or remove content the same way editing in the app does, so agents should treat them with the care the tool descriptions ask for.