Model Context Protocol (MCP)

Configure MCP servers in the Warp desktop app to extend local agents with custom tools and data sources through a standardized interface.

MCP servers extend Warp’s local agents in a modular, flexible way by exposing custom tools or data sources through a standardized interface — essentially acting as plugins for Warp. Warp supports a variety of connection protocols, including Streamable HTTPS and SSE, along with custom headers and environment variables.

MCP is an open source protocol. Check out the official MCP documentation for more detailed information on how this protocol is engineered.

How to access MCP Server settings

You can navigate to the MCP servers page in any of the following ways:

From the Settings Page: Settings > Agents > MCP servers
From Warp Drive: under Personal > MCP Servers
From the Command Palette: search for Open MCP Servers
From the Warp app: Settings > Agents > Warp Agent > Manage MCP servers

This will show a list of all configured MCP servers, including which are currently running. If you close Warp with an MCP server running, it will run again on next start of Warp. MCP servers that are stopped will remain so on next launch of Warp.

MCP servers page

Adding an MCP Server

To add a new MCP server, you can click the + Add button. Configurations from most MCP Clients can be directly copied and pasted.

MCP server types you can add:

CLI Server (Command)
Streamable HTTP or SSE Server (URL)

Provide a startup command. Warp will launch this command when starting up and shut it down on exit.

Adding a CLI MCP Server (Command)

CLI Server (Command) MCP Configuration Properties

Property	Type	Required	Description
`command`	string	Yes	The executable to launch (e.g., `npx`).
`args`	string[]	Yes	Array of command-line arguments passed to `command` (e.g., module name, paths).
`env`	object	No	Key-value object of environment variables (e.g., API Tokens).
`working_directory`	string	No	Working directory path where the command is run, used for resolving relative paths.

Provide a URL where Warp can reach an already-running MCP server that supports Server-Sent Events.

Adding an SSE MCP Server (URL)

Streamable HTTP or SSE Server (URL) MCP Configuration Properties

Property	Type	Required	Description
`url`	string	Yes	The HTTP endpoint URL to connect to via Server-Sent Events (SSE).
`headers`	object	No	Key-value object of header variables (e.g., Authorization).

Adding multiple MCP servers

Warp supports configuring multiple MCP servers using a JSON snippet. Each entry under mcpServers is keyed by a unique name (filesystem, github, notes, etc). All servers defined in the example are added automatically — no manual setup required.

To add a multiple MCP servers, you can click the + Add button then paste in a JSON snippet like the example below:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/allowed/files"]
    },
    "notes": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-notes", "--notes-dir", "/Users/you/Documents/notes"]
    },
    "externalDocs": {
      "url": "http://localhost:4000/mcp/stream",
      "headers": {
            "my-header": "my-header-value"
      }
    }
  }
}

File-based MCP servers

Warp detects MCP server configurations managed by supported third-party agents and can automatically spawn them alongside your manually configured servers.

To enable, go to Settings > Agents > MCP servers and toggle File-based MCP Servers on.

File-based MCP Servers toggle

When enabled:

Global/user-scoped servers - spawned on Warp startup and available in any session.
Project-scoped servers - spawned when you enter a repo containing a supported config file, and available within that project only.

Supported providers:

Claude Code - reads user-scoped config (~/.claude.json) and project-scoped config (.mcp.json at project root). See user scope and project scope in the Claude Code docs.
Codex - reads global config (~/.codex/config.toml) and project-scoped config (.codex/config.toml at project root). See Codex MCP docs.

Managing MCP servers

After MCP servers are registered in Warp, you can Start or Stop them from the MCP servers page. Each running server will have a list of available tools and resources.

You can rename and edit a server’s name, as well as delete the server. If you are a part of a Team, you can also share a MCP with your teammates.

MCP servers can be shared with your teammates by clicking the share icon. When sharing, sensitive values in the env configuration will be automatically scrubbed and replaced with variables.

Your teammates can find shared MCP servers under the Shared section of their MCP settings. When your teammates install your server configuration, they will be prompted to enter any scrubbed env values.

Warp also provides out-of-the-box MCP servers that can be installed by anyone. These can be found under the Shared section of your MCP settings.

Authentication in MCP servers

Most MCP servers require authentication to connect to external services. Warp supports the following methods:

Environment variables: pass an API key or access token via the server’s environment variables.
OAuth login (one-click installation): simplifies configuration by handling authentication through your browser. Warp stores credentials securely on your device and reuses them for future sessions. Re-authentication is required when opening Warp on a new machine.
- Starting a server without existing credentials automatically opens a browser-based authentication flow.
- Credentials can be revoked at any time from the MCP Servers pane in Warp.
Custom Headers: pass an Authentication Bearer token via the headers variable.

Debugging MCP

If you’re having trouble with an MCP server, you can check the logs for any errors or messages to help you diagnose the problem by clicking the View Logs button on a server from the MCP servers page.

Debugging MCP Authentication issues

In some cases you may need to reset the auth token for some MCP servers. To do this delete the local MCP auth files by running the following: rm -rf ~/.mcp-auth

If the above doesn’t help and you need to reset or change authentication, you may need to switch to a CLI-based MCP server configuration and provide the token via environment variables. See Sentry CLI MCP Example.

Where MCP logs are stored

Warp saves the MCP logs locally on your computer. You can open the files directly and inspect the full contents in the following location:

cd "$HOME/Library/Group Containers/2BBY89MBSN.dev.warp/Library/Application Support/dev.warp.Warp-Stable/mcp"

Set-Location $env:LOCALAPPDATA\warp\Warp\data\logs\mcp

cd "${XDG_STATE_HOME:-$HOME/.local/state}/warp-terminal/mcp"

MCP server configuration examples

Below are examples for popular Model Context Protocol (MCP) servers.

CLI Server (Command) — local npx or docker command based MCP servers.
Streamable HTTP or SSE Server (URL) — remote or locally hosted MCP endpoints.

Engineering & Ops

GitHub MCP Docs

GitHub CLI Server (Command)

{
  "GitHub": {
    "command": "docker",
    "args": ["run","-i","--rm","-e","GITHUB_PERSONAL_ACCESS_TOKEN","ghcr.io/github/github-mcp-server"],
    "env": {
      "GITHUB_PERSONAL_ACCESS_TOKEN": "<your_github_token>"
    }
  }
}

GitHub SSE Server (URL)

{
  "GitHub": {
    "url": "https://api.githubcopilot.com/mcp/"
  }
}

Sentry MCP Docs

Sentry CLI Server (Command)

{
  "Sentry": {
    "command": "npx",
    "args": ["-y","mcp-remote@latest","https://mcp.sentry.dev/mcp"]
  }
}

Sentry SSE Server (URL)

{
  "Sentry": {
    "url": "https://mcp.sentry.dev/sse"
  }
}

Grafana MCP Docs

Grafana CLI Server (Command)

{
  "Grafana": {
    "command": "docker",
    "args": ["run","--rm","-i","-e","GRAFANA_URL","-e","GRAFANA_API_KEY","mcp/grafana","-t","stdio","-debug"],
    "env": {
      "GRAFANA_URL": "http://localhost:3000",
      "GRAFANA_API_KEY": "<your_grafana_key>"
    }
  }
}

Grafana SSE Server (URL)

{
  "Grafana": {
    "url": "https://your-mcp-host.com/api/mcp/grafana/sse"
  }
}

Linear MCP Docs

Linear CLI Server (Command)

{
  "Linear": {
    "command": "npx",
    "args": ["-y","mcp-remote","https://mcp.linear.app/sse"]
  }
}

Linear SSE Server (URL)

{
  "Linear": {
    "url": "https://mcp.linear.app/sse"
  }
}

Chroma Package Search CLI Server (Command)

Visit Chroma’s Package Search page.
Click “Get API Key” to create or log into your Chroma account and issue an API key for Package Search.
After issuing your API key, click the “Other” tab and copy your API key.
Add the following to your Warp MCP config. Make sure to click “Start” on the server after adding.

More info in Chroma’s Package Search MCP Docs

{
    "package-search": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.trychroma.com/package-search/v1", "--header", "x-chroma-token: ${X_CHROMA_TOKEN}"],
      "env": {
        "X_CHROMA_TOKEN": "<YOUR_CHROMA_API_KEY>"
      }
    }
}

Design & Collaboration

Figma Remote MCP Server (Recommended)

The official Figma remote MCP server supports OAuth for simple, one-click setup.

In Warp, go to Warp Drive > MCP Servers > + Add and paste the configuration below.
Warp will open a browser window to authenticate with Figma.
After approving access, credentials are stored securely on your device.

{
  "Figma": {
    "url": "https://mcp.figma.com/mcp"
  }
}

Figma Local MCP Server

Enable the Official Figma MCP Server. Figma MCP Docs
Open the Figma desktop app and make sure you’ve updated to the latest version.
Create or open a Figma Design file.
In the upper-left corner, open the Figma menu.
Under Preferences, select Enable local MCP Server.
Enter the following configuration into Warp > Warp Drive > MCP Servers > + Add.

{
  "Figma (Local)": {
    "url": "http://127.0.0.1:3845/mcp"
  }
}

Slack MCP Docs

Slack CLI Server (Command)