> ## Documentation Index
> Fetch the complete documentation index at: https://docs.evidence.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Studio MCP

> Connect AI assistants to your live Evidence workspace — query data and read published reports.

The **Studio MCP** lets AI assistants like Claude and ChatGPT connect to your live Evidence workspace. Once connected, the assistant can access your projects, published reports, and query your data.

The server is available at `https://evidence.studio/api/mcp` and uses Streamable HTTP.

<Note>
  Every request runs as the signed-in user — access policies and page controls are respected.
</Note>

## Adding to AI Tools

<Tabs>
  <Tab title="Claude.ai (Web)">
    Add the Studio MCP as a custom connector:

    1. Go to Claude.ai → Customize → [Connectors](https://claude.ai/new#settings/customize-connectors)
    2. Click Add → Add custom connector
    3. Enter a name ("Evidence Studio")
    4. Enter the Remote MCP server URL: `https://evidence.studio/api/mcp`
    5. Click **Add**
    6. If the connector does not authenticate automatically, click **Connect** — you'll be sent to Evidence to sign in and choose the organization to authorize

    The Evidence tools will now be available in your Claude.ai conversations.
  </Tab>

  <Tab title="Claude Desktop">
    Add the Studio MCP as a custom connector:

    1. Open **Settings → Connectors** (macOS: **Claude → Settings**; Windows: menu **☰ → Settings**)
    2. Click **Add custom connector**
    3. Enter a name ("Evidence Studio")
    4. Enter the Remote MCP server URL: `https://evidence.studio/api/mcp`
    5. Click **Add**
    6. If the connector does not authenticate automatically, click **Connect** — you'll be sent to Evidence to sign in and choose the organization to authorize

    The Evidence tools will now be available in your Claude Desktop conversations.
  </Tab>

  <Tab title="ChatGPT">
    ChatGPT requires enabling Developer Mode to use MCP servers:

    1. Go to Settings → [ChatGPT Security](https://chatgpt.com/plugins#settings/Security)
    2. Scroll to find Developer Mode, and toggle it on.
    3. Navigate to [ChatGPT Plugins](https://chatgpt.com/plugins) in the sidebar, then click the New Plugin button `+`

    * (Optional) Add an image (e.g., the [Evidence logo](https://github.com/evidence-dev/media-kit/blob/main/png/logo-square-white-on-black.png))
    * Enter a name ("Evidence Studio")
    * Enter a description ("Connect to Evidence to query your data and reports")
    * Enter the Remote MCP server URL: `https://evidence.studio/api/mcp`

    4. Click "I accept and want to continue" then `Create`
    5. You'll be sent to Evidence to sign in and choose the organization to authorize
    6. Back in a new chat, ask the assistant to achieve something "using Evidence"

    The Evidence tools will now be available in your ChatGPT conversations.
  </Tab>

  <Tab title="Claude Code">
    ```bash theme={null}
    claude mcp add evidence-studio --transport http https://evidence.studio/api/mcp
    ```

    Then run `/mcp` inside Claude Code and authenticate — you'll be sent to Evidence to sign in and choose the organization to authorize.
  </Tab>

  <Tab title="Cursor">
    Add the following to your Cursor MCP configuration (`.cursor/mcp.json`):

    ```json theme={null}
    {
      "mcpServers": {
        "evidence-studio": {
          "url": "https://evidence.studio/api/mcp"
        }
      }
    }
    ```

    Open Cursor → Settings → MCP and click **Login** on the evidence-studio server to sign in and choose the organization to authorize.
  </Tab>
</Tabs>

## Available Tools

The Studio MCP server provides the following tools for AI assistants:

| Tool                       | Description                                                                                                                                                                                                                                                                                                                                              |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `whoami`                   | Get the authenticated Evidence user and their active organization.                                                                                                                                                                                                                                                                                       |
| `list_organizations`       | List the Evidence organizations you belong to. The active organization is fixed to the one you authorized; to act in a different organization, reconnect and select it during sign-in.                                                                                                                                                                   |
| `list_projects`            | List the projects (workspaces) in this organization that you have access to.                                                                                                                                                                                                                                                                             |
| `get_context`              | Get the workspace context (the projects’ agent/context instructions and available skills) that Evidence maintains for AI assistants. Call with no arguments to get context for every project you can access, or pass a projectSlug to scope it to one project. Read this before answering questions about the workspace’s data, metrics, or conventions. |
| `list_project_pages`       | List the pages within a specific project that you have access to. Use after list\_projects.                                                                                                                                                                                                                                                              |
| `search_published_content` | Search published reports across the workspace by free text (titles + page body). Prefer this when the user asks about a topic, metric, or term.                                                                                                                                                                                                          |
| `get_page_summary`         | Get a structured summary of a published page (title, queries, components) so you can describe what it shows.                                                                                                                                                                                                                                             |
| `get_page_content`         | Get the raw Markdoc content of a published page. Prefer get\_page\_summary first.                                                                                                                                                                                                                                                                        |
| `list_tables`              | List the warehouse tables available in this workspace.                                                                                                                                                                                                                                                                                                   |
| `get_metadata`             | Get column names and types for the given tables so you can write correct SQL.                                                                                                                                                                                                                                                                            |
| `run_query`                | Execute a read-only SQL query against the workspace data you have access to. Before running your first query, call get\_context. Row-level security is applied based on who is asking. SELECT/WITH only; default LIMIT 100, max 1000. Do not add SETTINGS or FORMAT clauses, these are added by server.                                                  |

<Note>
  `run_query` is only available when your organization allows query execution. If it's disabled, the assistant can still explore tables, metadata, pages, and search results.
</Note>
