Configure MCP servers in Warp terminal for AI command-line workflows.
Warp is a modern terminal with built-in AI features. Warp supports Model Context Protocol (MCP) so AI blocks and agents can call external tools — the same official reference servers used by Claude Desktop, Cursor, and Cline.
PREREQUISITES
From https://github.com/modelcontextprotocol/servers :
- Node.js 18+ for npx servers
- uv / uvx for Python servers
Quick verification:
npx -y @modelcontextprotocol/server-everything
uvx mcp-server-time
CONFIGURATION
Warp documents MCP setup in its settings and developer documentation. Look for MCP or "Model Context Protocol" under Warp Settings > AI or Features (exact path may change between Warp releases).
Warp typically stores MCP definitions in a JSON configuration using command and args fields compatible with the official README examples:
{
"mcpServers": {
"memory": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-memory"]
}
}
}
Consult Warp's current docs for whether config lives in a global file, per-workflow file, or cloud-synced settings — this differs from Claude Desktop's claude_desktop_config.json path.
WINDOWS
For npx on Windows, the official MCP servers README specifies:
{
"mcpServers": {
"memory": {
"command": "cmd",
"args": ["/c", "npx", "-y", "@modelcontextprotocol/server-memory"]
}
}
}
uvx entries remain:
{
"mcpServers": {
"fetch": {
"command": "uvx",
"args": ["mcp-server-fetch"]
}
}
}
EXAMPLE: FILESYSTEM + MEMORY FOR LOCAL DEV
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/Users/you/dev"
]
},
"memory": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-memory"]
}
}
}
Terminal-centric workflows benefit from Git MCP scoped to the repo you opened in Warp:
uvx mcp-server-git --repository path/to/git/repo
USING MCP IN WARP
After configuration, Warp AI features can discover tools exposed by running MCP servers — listing directories, reading files within allowed roots, storing memory graph entities, converting fetched HTML to text, etc. Restart Warp or reload MCP if servers do not appear immediately.
TROUBLESHOOTING
- Ensure Node and uvx binaries are on the PATH Warp inherits (GUI apps on macOS may need login shell PATH fixes).
- Run the server command manually in Warp to capture startup errors.
- Invalid JSON prevents loading — validate before save.
SECURITY
Warp may execute shell commands alongside MCP tools. Combine least-privilege directory scoping with careful review of agent-suggested commands. Official reference servers are examples; not all deployments belong in production terminals with sensitive keys.
REFERENCES
- Official MCP servers README: https://github.com/modelcontextprotocol/servers
- Warp MCP documentation: see docs.warp.dev for the latest configuration UI (may vary).