---
title: Sommet MCP server
description: Connect Claude, ChatGPT, Cursor, VS Code, Claude Code or Codex to your Sommet data, and let them edit your questions and actions.
sidebar:
  label: Overview
---

The Model Context Protocol (MCP) lets an AI assistant call tools on other services. The Sommet MCP server gives your assistant access to your workspaces: AI visibility, answers, cited sources, competitors, AI bot visits, tracked questions and recommended actions. With your approval, it can also edit your questions, update the status of actions.

Use it to:

- ask "Why did my mention rate drop this week?" in Claude or ChatGPT;
- let Cursor or Claude Code read your actions, change the right page in your repository, then mark the action done;
- rewrite your tracked questions from your sales notes;
- prepare your [weekly review](/docs/improve/weekly-routine) in one prompt.

## Server details

|                |                                                                      |
| -------------- | -------------------------------------------------------------------- |
| URL            | `https://api.sommet.dev/mcp`                                         |
| Transport      | Streamable HTTP, stateless (`POST` only)                             |
| Authentication | OAuth 2.1 with your Sommet account                                   |
| Scopes         | `sommet:read` for the read tools, `sommet:write` for the write tools |
| Quota          | Calls use no plan quota. Calls are rate-limited per user.            |

## Connect

1. **Add the server to your assistant**

    Follow the steps for your assistant in [Connect your assistant](/docs/mcp/clients). You can also open
    **Settings → AI assistants** in Sommet: it shows the URL, one-click install links and the
    commands to copy.

2. **Sign in and approve**

    The first time, the assistant opens Sommet in your browser. Sign in, check the name of the app
    and where it sends you back, then select **Allow**.

3. **Ask a question**

    Start with "List my Sommet workspaces". Then try a prompt from the [prompt
    library](/docs/prompts/analyze-with-mcp).

## What the assistant can do

The assistant sees what you see in Sommet, for every workspace you are a member of. It cannot see your Search Console or Bing credentials, your Cloudflare token or your drain URLs.

The consent screen lists the access you give:

- read the AI visibility, answers, sources, competitors, AI bot traffic and recommended actions of your workspaces;
- add, reword and remove tracked questions, update the status of recommended actions;
- confirm your identity and see your name and email;
- stay connected without signing in again.

It cannot change your plan, members, settings or connected services, and it cannot start a collection. See the [tools reference](/docs/mcp/tools) for each tool.

:::tip
Most assistants ask you to confirm before they call a tool that changes data. Read the confirmation: it names the tool and its inputs. Ask the assistant to show the change it plans first, for example "List the questions you will remove, and wait for my go."
:::

### Read-only connections

A connection approved before write access existed, or by a client that asked only for `sommet:read`, sees the read tools only. To get the write tools, disconnect the assistant in **Settings → AI assistants**, then connect it again and approve.

## Disconnect

Open **Settings → AI assistants**. The **Connected apps** list shows each assistant and the date you connected it. Select **Disconnect** to revoke its access at once.

:::warning
Only approve a connection you started yourself. If a consent screen appears when you did not add Sommet to an assistant, select **Deny**.
:::

## For client developers

The server publishes the standard discovery documents, so any MCP client with OAuth support can connect without manual setup:

- Protected resource metadata (RFC 9728): `https://api.sommet.dev/.well-known/oauth-protected-resource/mcp`
- Authorization server metadata (RFC 8414): `https://api.sommet.dev/.well-known/oauth-authorization-server/api/auth`

Clients register dynamically. Tokens are sent as `Authorization: Bearer` headers.