Model Context Protocol (MCP)

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 HTTP 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.

Note

This page covers MCP servers for local agents in the Warp app. For help choosing between local, cloud, and shared MCP workflows, see Connect developer tools to agents with MCP workflows. If you’re using cloud agents, see MCP Servers for cloud agents.

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)

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

Adding a CLI MCP Server (Command).

Note

Always set working_directory explicitly when your MCP server command or args include relative paths. This ensures consistent and predictable behavior across machines and sessions.

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.

Streamable HTTP or SSE Server (URL)

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 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

Compared to manually adding a server in the Warp settings, file-based servers are defined in config files that Warp detects and can spawn automatically. They offer a few additional benefits:

• Configurable directly with an agent - Use the bundled skill /agent-add-mcp so the Warp Agent can add or update an MCP server without leaving the conversation.
• Inherited across providers and repos - Warp reads .warp/.mcp.json files and also picks up config from third-party agent providers (Claude Code, Codex, and others). The same server definition follows you across tools and repos.

Supported providers

Warp reads MCP server definitions from the following providers:

Provider	Global config	Project-scoped config	Auto-spawn
Warp	~/.warp/.mcp.json	.warp/.mcp.json at project root	On by default
Claude Code	~/.claude.json	.mcp.json at project root	Requires toggle
Codex	~/.codex/config.toml	.codex/config.toml at project root	Requires toggle
Other agents	~/.agents/.mcp.json	.agents/.mcp.json at project root	Requires toggle

Global Warp servers auto-spawn by default. Global servers from all other providers auto-spawn only when Auto-spawn servers from third-party agents is enabled. Project-scoped servers from any provider require explicit approval.

For provider-specific setup, see the Claude Code MCP docs and Codex MCP docs.

Auto-spawn behavior

Global Warp servers auto-spawn by default. Third-party agent servers require you to enable auto-spawn first.

To auto-spawn global servers from third-party agents:

1. In the Warp app, go to Settings > Agents > MCP servers.
2. Toggle Auto-spawn servers from third-party agents on.

File-based MCP server settings.

Project-scoped servers from any provider must be toggled on individually from the MCP servers page. These are session-scoped — after restarting Warp, toggle them on again if you still trust the repo.

Using /agent-add-mcp

The built-in /agent-add-mcp skill lets the Warp Agent create or update file-based MCP server definitions. Choose whether to save globally or in the current project — the skill writes the server definition to the matching file:

• Global: ~/.warp/.mcp.json
• Project-scoped: {repo_root}/.warp/.mcp.json

The demo shows how to use /agent-add-mcp to add an MCP server, choose where Warp saves the file-based configuration, and review the generated .warp/.mcp.json file before using the server.

Security mitigations

MCP config files can start local commands and send data to external tools. Warp adds approval gates around file-based MCP servers to reduce the risk of untrusted config changes:

• Config edits require approval - Warp prevents edits to MCP config files unless you explicitly approve the change. This keeps an agent or automation from silently adding a server that can run commands or access data.
• Project-scoped servers never auto-spawn - Warp detects project-scoped MCP config files in cloned repos, but requires you to start each server manually. This prevents a cloned repo from automatically starting an MCP server that runs arbitrary local commands.

Note

File-based servers that require OAuth show an authentication modal on their first spawn. Credentials are saved for future spawns, the same as manually configured MCP servers.

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 an MCP server with your teammates.

Sharing MCP servers

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.

Sharing an MCP Server.

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.

Caution

If you choose to share your MCP server logs with anybody, make sure to remove any sensitive information before sharing, as they may contain API keys.

Many SSE based MCP servers will state that your URL should be treated like a password, and can be used with no additional authentication.

Note

Tip: We’ve noticed that some models often work better with MCP servers than others. If you’re having trouble calling or using an MCP server, try using a different model.

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

Caution

Note this will delete all your MCP auth tokens stored locally so you will need to login and re-authenticate.

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 the Sentry tab under MCP server configuration examples.

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:

macOS

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

Windows

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

Linux

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

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

Sentry MCP Docs

Sentry CLI Server (Command)

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

Sentry Streamable HTTP Server (URL)

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

Grafana

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

Linear MCP Docs

Linear CLI Server (Command)

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

Linear Streamable HTTP Server (URL)

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

Chroma

Chroma Package Search CLI Server (Command)

1. Visit Chroma’s Package Search page.
2. Click “Get API Key” to create or log into your Chroma account and issue an API key for Package Search.
3. After issuing your API key, click the “Other” tab and copy your API key.
4. 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

Figma Remote MCP Server (Recommended)

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

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

Note

Note: A Figma account with Dev Mode enabled is required.

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

Figma Local MCP Server

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

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

Slack

Slack MCP Docs

Slack CLI Server (Command)

Enter the following configuration into Warp > Warp Drive > MCP Servers > + Add.

{
  "Slack": {
    "command": "npx",
    "args": ["-y", "@modelcontextprotocol/server-slack"],
    "env": {
      "SLACK_BOT_TOKEN": "xoxb-<your-bot-token>",
      "SLACK_APP_TOKEN": "xapp-<your-app-token>",
      "SLACK_TEAM_ID": "T<your_workspace_id>",
      "SLACK_CHANNEL_IDS": "<your_channel_id-1>, <your_channel_id-2>",
      "MCP_MODE": "stdio"
    }
  }
}

Slack SSE Server (URL)

Enter the following configuration into Warp > Warp Drive > MCP Servers > + Add.

{
  "Slack": {
    "url": "https://your-mcp-host.com/api/mcp/slack/sse"
  }
}

Atlassian

Atlassian MCP Docs

Atlassian CLI Server (Command)

Enter the following configuration into Warp > Warp Drive > MCP Servers > + Add.

{
  "Atlassian": {
    "command": "npx",
    "args": ["-y", "mcp-remote", "https://mcp.atlassian.com/v1/sse"]
  }
}

Notion

Notion MCP Docs

Notion CLI Server (Command)

Enter the following configuration into Warp > Warp Drive > MCP Servers > + Add.

{
  "Notion": {
    "command": "npx",
    "args": ["-y", "mcp-remote", "https://mcp.notion.com/mcp"]
  }
}

Notion SSE Server (URL)

Enter the following configuration into Warp > Warp Drive > MCP Servers > + Add.

{
  "Notion": {
    "url": "https://mcp.notion.com/sse"
  }
}

MCP server demos

Warp Guides hosts a collection of demos and walkthroughs showing how MCP servers can extend your workflows. Each example highlights practical use cases you can try today:

• GitHub — access repositories, issues, and pull requests through MCP.
• Sentry — surface error monitoring and alerts as agent-usable data.
• Linear — integrate project management tasks and tickets.
• Puppeteer — run automated browser workflows via MCP.
• Context7 — experiment with external data integrations.