Authentication & permissions

Marq MCP uses OAuth 2.0 with the authorization-code flow and PKCE. If you have integrated with the Marq REST API, the model will be familiar; this page covers what is specific to MCP.

The assistant acts as the user

Every connection belongs to one person, and every tool call runs with that person's permissions.

• It reaches what they reach. The templates, images, datasets and documents that user can already open in Marq — nothing else, and nothing belonging to colleagues who have not connected.
• Permissions are live. They are checked on each call, not captured at connection time. Remove someone's access to a folder in Marq and their assistant loses it immediately.
• Limits are theirs. Rate limits apply per connected session. See Usage policy & limits.

For an administrator, the decision being made is "our people may let an assistant act as them in Marq." There is no way to grant an assistant more than the person already has.

No plan requirement

MCP access is not gated by plan or add-on. Any Marq account can connect.

Client registration

The server supports Dynamic Client Registration, so an MCP client can register itself the first time a user connects. Nothing needs to be provisioned in advance.

Clients that do not implement DCR can register once manually — see Connect an AI assistant.

Tokens

Server metadata is published at https://mcp.marq.com/.well-known/oauth-authorization-server, and the protected resource at https://mcp.marq.com/.well-known/oauth-protected-resource/mcp. Spec-compliant clients read both automatically.

Disconnecting

Revoking the token at the revocation endpoint ends the connection immediately; the next tool call fails until the user reauthorizes.

Because the assistant holds no standing access of its own, removing a person's Marq access — or deactivating their account — also ends anything their assistant could do.