Connect an AI assistant

What you need

• A Marq account with a supported plan.
• An MCP client that supports remote servers and OAuth.

That is the whole list. There is no registration form and no approval step.

Step 1: Add the server

https://mcp.marq.com/mcp

Most clients take a config block like this:

{
  "mcpServers": {
    "marq": {
      "url": "https://mcp.marq.com/mcp"
    }
  }
}

Your client discovers everything else on its own. It reads /.well-known/oauth-protected-resource/mcp to find the authorization server, registers itself at the registration endpoint, and starts the sign-in flow. You do not need to create credentials in advance.

Step 2: Sign in

The first tool call opens the Marq sign-in page. The user signs in, approves the connection, and the client receives a token.

Access tokens last one hour and refresh automatically. Authorization uses the authorization-code flow with PKCE (S256), which is required — a client that does not send a code challenge is rejected.

📘

Each person signs in for themselves

There is no organization-wide connection. Every user authorizes individually and the assistant acts with exactly that person's Marq permissions. See Authentication & permissions.

Step 3: Confirm it works

Ask the assistant:

List my Marq brand templates.

That calls document_SearchTemplates and returns templates from the signed-in account. It is read-only, so a misconfigured connection cannot create anything.

An empty list means the connection works and the account has no templates. An error means the connection does not — see Troubleshooting.

Set the timeout to 60 seconds

Some tools do real work. Export renders a file; document-wide reads and edits touch every block on every page. A default timeout of a few seconds will cut those calls off while they are still succeeding.

If your client cannot register itself

Clients without automatic registration can register once by hand and reuse the credentials:

curl --request POST \
  --url https://mcp.marq.com/register \
  --header 'content-type: application/json' \
  --data '{
    "client_name": "Your product name",
    "redirect_uris": ["https://your-app.example.com/oauth/callback"]
  }'

Store the returned client_id and client_secret, then point your client at these endpoints:

Allow the right domains

If your platform filters outbound hosts, allow mcp.marq.com for the server itself and marq.com for the sign-in page the user is sent to. A client that allows one but not the other fails without a useful message.

Next

Verify your integration checks every tool group, not just the connection.