Studio MCP

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.

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

Adding to AI Tools

Claude.ai (Web)
Claude Desktop
ChatGPT
Claude Code
Cursor

Add the Studio MCP as a custom connector:

Go to Claude.ai → Customize → Connectors
Click Add → Add custom connector
Enter a name (“Evidence Studio”)
Enter the Remote MCP server URL: https://evidence.studio/api/mcp
Click Add
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.

Add the Studio MCP as a custom connector:

Open Settings → Connectors (macOS: Claude → Settings; Windows: menu ☰ → Settings)
Click Add custom connector
Enter a name (“Evidence Studio”)
Enter the Remote MCP server URL: https://evidence.studio/api/mcp
Click Add
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.

ChatGPT requires enabling Developer Mode to use MCP servers:

Go to Settings → ChatGPT Security
Scroll to find Developer Mode, and toggle it on.
Navigate to ChatGPT Plugins in the sidebar, then click the New Plugin button +

(Optional) Add an image (e.g., the Evidence logo)
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

Click “I accept and want to continue” then Create
You’ll be sent to Evidence to sign in and choose the organization to authorize
Back in a new chat, ask the assistant to achieve something “using Evidence”

The Evidence tools will now be available in your ChatGPT conversations.

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.

Add the following to your Cursor MCP configuration (.cursor/mcp.json):

{
  "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.

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.

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.

Get Started

Core Concepts

Features

MCP

CLI

Warehouses

Evidence Warehouse

Components

Adding to AI Tools

Available Tools

​Adding to AI Tools

​Available Tools

Adding to AI Tools

Available Tools