Marque Docs

Connect an agent

Marque exposes a remote MCP server over Streamable HTTP:

https://marque.at/mcp

Use an MCP client that supports OAuth for remote HTTP servers. You do not need to create an API key or copy a bearer token.

Before you connect

You need:

  • a Marque account signed in through AT Protocol;
  • an OAuth-capable MCP client;
  • access to any domains you want the agent to manage.

An OAuth scope does not create domain access. A team member can only use capabilities already delegated by the domain owner.

Add Marque

  1. Open your MCP client’s server settings.
  2. Add a remote or Streamable HTTP server.
  3. Enter https://marque.at/mcp as the server URL.
  4. Start the connection.
  5. Complete the Marque sign-in and consent flow in your browser.
  6. Return to the client and confirm that Marque’s tools are listed.

The client first contacts the endpoint without credentials. Marque responds with OAuth discovery information, and the client opens the browser flow. This initial unauthorized response is expected.

For exact setup steps, choose a client guide: Zed, Cherry Studio, Claude, Cursor, and VS Code are covered.

Choose scopes deliberately

The consent screen lists the access requested by the client. Grant only what the agent needs for its task. Read the OAuth scope reference for the complete list.

You can disconnect a client later from Settings → Connected agents in Marque. Revocation invalidates that client’s active credentials and pending checkout requests without affecting other clients.

Verify the connection

Ask the client to list Marque tools, then start with a read-only call such as search_domains or list_domains. A client should not ask you to paste Marque, PDS, card, or wallet credentials into its configuration.

If setup fails, use the troubleshooting guide.

On this page