Connect an AI client with MCP

Before you connect

• Use an active Agency workspace.
• Choose a trusted client that supports remote Streamable HTTP MCP.
• Be ready to choose one workspace or all eligible workspaces and approve access.

Choose your AI client

Select the client you use and follow its native setup. These are the same instructions shown in Settings > Integrations, including the exact server URL or commands to copy.

Connect this AI client to Tartol using its native MCP and OAuth flow. Configure a Streamable HTTP server named Tartol.

MCP server URL: https://tartol.com/api/mcp

Use OAuth discovery automatically; do not ask for or add an API key, bearer token, resource override, or custom authorization header. Start the client's OAuth action and open the authorization screen so I can sign in, select my workspace, review permissions, and approve. If the request expires, restart OAuth and reopen it. After approval, confirm that the Tartol server is connected, call whoami and list_capabilities, then list the available Tartol tools. Do not modify or deploy Tartol code.

Authorize Tartol

1. 1Sign in to TartolUse the OAuth browser window opened by your client. If the browser session needs to be refreshed or you need to sign in, Tartol returns to the same connection request automatically; you should not need to select Authenticate a second time. Never paste an API key, password, manual resource, or authorization header.
2. 2Review the requestChoose All workspaces or one workspace, review View and Edit access, and select Authorize connection.
3. 3Verify the connectionConfirm the server is connected, then call whoami and list_capabilities.

Verify the right workspaces

The whoami tool returns every authorized workspace, its role, and the OAuth scopes bound to the connection. Tools accept workspace_id when the client needs to target a specific workspace. Stop and reconnect if any of those are wrong.

Stay connected across restarts

A client restart should not require another Tartol sign-in. Tartol issues a revocable 30-day access session and, when the client registers refresh support, a rotating refresh token valid for up to one year. If a client unexpectedly shows Authenticate again, complete OAuth once, verify the Tartol server is connected, and update or report the client if the problem repeats. Revoking the connection in Tartol immediately prevents the credential from being used again.

Disconnect later

Open Settings > Integrations > OAuth connections and revoke the client. Connections are shown five at a time; use the numbered pagination controls to move between pages. Revocation stops that connection without changing your Tartol password.