Model Context Protocol
Extend Warp’s agents with custom tools and data sources using MCP servers — modular plugins powered by a standardized interface.
Model Context Protocol (MCP)
MCP servers extend Warp’s agents in a modular, flexible way by exposing custom tools or data sources through a standardized interface — essentially acting as plugins for Warp.
MCP is an open source protocol. Check out the official MCP documentation for more detailed information on how this protocol is engineered.
In these docs, we'll focus on how to use MCP servers in Warp.
How to access MCP Server settings
You can navigate to the MCP servers page in any of the following ways:
From Warp Drive: under
Personal > MCP Servers
From the Command Palette: search for
Open MCP Servers
From the settings tab:
Settings > AI > Manage MCP servers
This will show a list of all configured MCP servers, including which are currently running

Adding an MCP Server
To add a new MCP server, you can click the + Add
button. MCP server types you can add:
Provide a startup command. Warp will launch this command when starting up and shut it down on exit.

CLI Server (Command) MCP Configuration Properties
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., tokens, API keys).
working_directory
string
No
Working directory path where the command is run, used for resolving relative paths. Default null
start_on_launch
boolean
No
Whether Warp auto-starts the MCP server on Warp launch. Default true
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"],
"start_on_launch": true
},
"github": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "your-github-token"
},
"start_on_launch": true
},
"notes": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-notes", "--notes-dir", "./notes"],
"working_directory": "/Users/Warp/Documents",
"start_on_launch": true
}
}
}
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. To prevent Warp from automatically starting a server when you open Warp, set the "start_on_launch"
value to false
in the server's JSON configuration.
Debugging
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.
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.
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/Application Support/dev.warp.Warp-Stable/mcp"
Last updated
Was this helpful?