MCP (Model Context Protocol) on Via Kondado lets you connect Claude — in any of its products — directly to your data integrated in Kondado. Once connected, you can ask Claude to list tables, describe fields, and run queries in natural language without leaving the chat.

This article covers how to set up the connection in Claude Web, Claude Desktop, and Claude Code. For the general MCP concept on Via Kondado and the alternative token-based path, see the MCP section of the main Via Kondado article.

Claude Web

Validated on claude.ai in November 2026. The flow uses OAuth — you do not need to copy any token manually. Claude Desktop has exactly the same screens (see the Claude Desktop section).

Step 1 — Open "Add custom connector"

In Claude's sidebar, click Customize → Connectors tab → + Add button → Add custom connector.

Shortcut (Claude Web): this link opens the add window directly: https://claude.ai/new?modal=add-custom-connector#settings/customize-connectors

Step 2 — Fill in the name and URL

In the "Add custom connector" window:

• Name: Kondado (any clear label — it is cosmetic only).
• Remote MCP server URL: https://mcp.kondado.io/mcp (full URL, including /mcp at the end).

Click Continue.

Step 3 — Authentication screen: choose "Sign in now"

The window now shows an Authentication screen with 3 options. Select "Sign in now":

• Sign in now (recommended) — you sign in to your Kondado account through the OAuth flow before using the connector.
• Sign in when needed — also works: Claude connects without credentials and asks you to sign in when it runs the first query.
• No sign in — do not select it. Claude often marks it as "Detected" by default, but Via Kondado requires sign-in to run queries; with "No sign in" no query works. This does not expose your data — Via Kondado only reads your account's destination, and every query requires your account's authentication.

Step 4 — OAuth client: keep the default

When you select "Sign in now", an OAuth client section appears below. Keep the default option "Use Claude's published identity (Recommended)" — do not change it and do not add headers.

Step 5 — Add

Click Add.

Step 6 — Connect

Claude shows a message saying you started connecting to Kondado but did not finish, with a button to connect. Click it.

Step 7 — Continue connecting

A dialog asks you to confirm finishing the connector's connection. Confirm to continue connecting. If you are not yet signed in to Kondado in that browser, the Kondado sign-in screen (app.kondado.com.br) opens first — sign in with your email and password (or social login).

Step 8 — Authorize access and choose your Via Kondado

Kondado's authorization screen opens:

1. Confirm the app is Claude and the scope is read access to your Via Kondado data.
2. Check that the signed-in email is your Kondado account.
3. In the dropdown, choose which Via Kondado destination Claude should query (if you have more than one Via Kondado, pick the one you want to run queries on).
4. Click the button to authorize.

Step 9 — Done

The connector shows up in your connectors list as Kondado. From there, open a chat and ask something like "List my Kondado tables" or "How much did I spend on Google Ads last month?".

On the first query, Claude asks permission to use the tool ("Claude wants to use … from Kondado"). Click Always allow if you don't want to see that prompt on every call.

Claude Desktop

Claude Desktop (the computer app) uses the same flow and the same screens as Claude Web. Open the app and follow:

1. Sidebar: Customize → Connectors tab → + Add → Add custom connector.
2. Name: Kondado; Remote MCP server URL: https://mcp.kondado.io/mcp. Click Continue.
3. On the Authentication screen, select "Sign in now". "Sign in when needed" also works; do not select "No sign in", even if Claude marks it as "Detected" — with it no query works (and it does not expose your data). Details of the 3 options in Step 3 of Claude Web.
4. Under OAuth client, keep "Use Claude's published identity (Recommended)" and do not add headers.
5. Click Add.
6. When Claude says you started connecting to Kondado but did not finish, click the button to connect.
7. Confirm you want to finish connecting the connector (sign in to Kondado in the browser if asked).
8. On Kondado's authorization screen, choose your Via Kondado destination and authorize (see Step 8 of Claude Web).
9. Done: the connector shows up in your connectors list as "Kondado". Claude Desktop stores the authorization — you do not need to sign in again.

Claude Code (CLI)

Claude Code is Anthropic's terminal CLI. It accepts MCP servers via a direct command or a config file.

Option A — direct command

claude mcp add kondado --transport http --url https://mcp.kondado.io/mcp

Option B — config file

Add this to your Claude Code settings.json:

{
  "mcpServers": {
    "kondado": {
      "type": "http",
      "url": "https://mcp.kondado.io/mcp"
    }
  }
}

On the first tool call that uses Kondado, Claude Code opens the browser in the same OAuth flow described in steps 7 and 8 of Claude Web. After approving, the token is stored locally and refreshed automatically.

Other Claude clients

As Anthropic adds MCP support to new products in the Claude family, the pattern is always the same:

• Register the MCP server with the URL https://mcp.kondado.io/mcp.
• On the first call, the client opens the Kondado consent screen at app.kondado.com.br.
• You pick the Via Kondado destination and approve.

See also: to connect OpenAI products (ChatGPT Web/Desktop and the Codex CLI), see the ChatGPT article.

For third-party MCP clients (non-Claude) or server-to-server integrations that do not support OAuth, you can use the legacy Via Kondado token — see the MCP section of the Via Kondado article.

Tips and troubleshooting

• Switch Via Kondado: open Customize → Connectors, remove the connector, and add it again. Going through consent again lets you pick a different destination in the dropdown.
• Token expired: Claude refreshes the token automatically via the refresh token. If you still see an authentication error, redo the connection (remove + add).
• I don't see all my tables: the connector only sees tables in the destination you picked on the consent screen. Make sure you selected the right destination in Step 8 of Claude Web.
• Claude asks for permission on every call: click Always allow the first time to stop seeing the pop-up for that specific tool.
• v1 limitations: MCP is read-only (queries only) and uses KSQL. You cannot write, update, or delete data in Via Kondado through MCP.

Next steps

• Via Kondado — destination overview
• MCP section in the Via Kondado article — differences between OAuth and the legacy token
• ChatGPT — how to connect ChatGPT (Web/Desktop) and Codex (OpenAI's CLI) to Via Kondado