-
Notifications
You must be signed in to change notification settings - Fork 504
Add Warp (Warp.dev) configuration support #351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
b41cf55
2e8aec7
f7fdab9
2c77de8
b68095c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,5 +10,6 @@ public enum McpTypes | |
| VSCode, | ||
| Windsurf, | ||
| Trae, | ||
| Warp | ||
| } | ||
| } | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -206,6 +206,31 @@ public class McpClients | |
| mcpType = McpTypes.Codex, | ||
| configStatus = "Not Configured", | ||
| }, | ||
| // Warp | ||
| new() | ||
| { | ||
| name = "Warp", | ||
| windowsConfigPath = Path.Combine( | ||
| Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData), | ||
| "Warp", | ||
| "mcp.json" | ||
| ), | ||
| macConfigPath = Path.Combine( | ||
| Environment.GetFolderPath(Environment.SpecialFolder.UserProfile), | ||
| "Library", | ||
| "Application Support", | ||
| "Warp", | ||
| "mcp.json" | ||
| ), | ||
| linuxConfigPath = Path.Combine( | ||
| Environment.GetFolderPath(Environment.SpecialFolder.UserProfile), | ||
| ".config", | ||
| "Warp", | ||
| "mcp.json" | ||
| ), | ||
| mcpType = McpTypes.Warp, | ||
| configStatus = "Not Configured", | ||
| }, | ||
|
Comment on lines
+209
to
+233
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🧩 Analysis chainVerify Warp configuration paths with official documentation. The configuration paths follow the established pattern used by other clients (e.g., Trae), but it's important to confirm these are the actual paths used by Warp.dev for MCP configuration. 🌐 Web query: 💡 Result: Official MCP file locations (per Warp docs):
Source: Warp documentation (Model Context Protocol / MCP). [1] Update Warp MCP configuration paths to match official Warp documentation. The paths in the code do not match the official Warp MCP locations:
Per Warp's official Model Context Protocol documentation, the correct paths are macOS: $HOME/Library/Application Support/dev.warp.Warp-Stable/mcp; Windows: 🤖 Prompt for AI Agents
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @tanthcstt is this true? Can you show reference the docs for the paths you've added for Window, Mac and Linux? Not in the code, just reply to this comment
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
| }; | ||
|
|
||
| // Initialize status enums after construction | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,5 +10,6 @@ public enum McpTypes | |
| VSCode, | ||
| Windsurf, | ||
| Trae, | ||
| Warp, | ||
| } | ||
| } | ||
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
Verify Warp configuration paths with official documentation.
The configuration paths follow the established pattern used by other clients (e.g., Trae), but it's important to confirm these are the actual paths used by Warp.dev for MCP configuration.
🌐 Web query:
💡 Result:
Short answer: Warp does not publish an official on-disk MCP configuration path. The MCP servers UI in Warp stores MCP settings in Warp Drive / the app settings (managed from Settings → AI → Manage MCP servers) and the product docs show how to add MCPs as JSON via the UI, but they do not document a stable file path you can edit on disk. [1][2]
Supporting links:
If you need a writable file you can edit: many other MCP clients use a JSON file named mcp_config.json (examples: Windsurf / Codeium at ~/.codeium/windsurf/mcp_config.json, Windsurf docs) — but that is not Warp’s documented on-disk location. [3][4]
References
Remove or reconcile Warp configuration paths—Warp does not document on-disk MCP configuration files.
Warp does not publish an official on-disk MCP configuration path. MCP settings are stored in Warp Drive and managed through the app UI (Settings → AI → Manage MCP servers), with no stable file path documented for editing on disk. A public GitHub issue requesting local on-disk MCP config support exists, but Warp maintainers do not document such a location.
The hardcoded paths in lines 211-235 assume Warp stores MCP configuration at specific filesystem locations, but this is not officially supported. Remove these paths or verify with Warp maintainers that these are actual implementation details (not documented as stable).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this true? If it is, then this won't work, and we'll need a different approach to configure Warp
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
💡 Result:
Short answer: Warp stores MCP server configs in your Warp application data and you can edit/add servers via the Warp UI (or CLI) using a JSON snippet.
Steps and locations:
Example minimal MCP JSON structure:
{
"mcpServers": {
"myServer": {
"command": "npx",
"args": ["-y","@modelcontextprotocol/server-filesystem","/path/to/allowed/files"],
"env": {},
"working_directory": null,
"start_on_launch": true
}
}
}
(Use Warp’s Add UI to paste and save this.) [1]
If you want, tell me your OS and whether you prefer UI or CLI and I’ll give exact commands/paths for your setup.
Sources: Warp docs (MCP pages) [1], Warp CLI docs (mcp help) [2].
🌐 Web query:
💡 Result:
Locations for the Warp MCP directory (Stable build):
Sources: Warp docs (macOS path shown). [1] Additional path examples / log-location references showing Windows/Linux equivalents. [2]
References:
[1] docs.warp.dev — Model Context Protocol (MCP) / examples.
[2] Glama / warp-sql-server-mcp debug docs (MCP log/location examples for macOS, Windows, Linux).
🌐 Web query:
💡 Result:
Short answer: Warp's MCP (Model Context Protocol) configuration is JSON. It uses a top-level object (commonly "mcpServers") whose keys are server names and whose values are server entries with fields like url (for SSE servers) or command/args/env/working_directory (for CLI servers), plus optional flags such as start_on_launch. Example and docs below.
Example JSON:
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/allowed/files"],
"working_directory": "/path/to",
"env": { "TOKEN": "…" },
"start_on_launch": true
},
"externalDocs": {
"url": "http://localhost:4000/mcp"
}
}
}
Key fields:
Where it's used / managed:
Sources:
[1] Warp MCP docs (Model Context Protocol) — examples and property descriptions. (docs.warp.dev)
[2] Warp CLI docs — warp mcp commands and usage. (docs.warp.dev)
[3] Warp University / MCP examples (GitHub/Figma examples). (warp.dev)
[4] Warp GitHub issue about local MCP config storage. (github.com)
Would you like the exact JSON schema extracted into a schema file (JSON Schema or TypeScript types) or help locating the local config file on your OS?
Citations:
@msanatan Yes, CodeRabbit's warning is accurate. The paths in this PR are incorrect, and more importantly, Warp's MCP configuration approach is fundamentally different from the other clients in your codebase.
Key Issues
1. Incorrect Paths
The PR uses:
~/Library/Application Support/Warp/mcp.json%APPDATA%\Warp\mcp.json~/.config/Warp/mcp.jsonThe actual Warp MCP locations are:
~/Library/Application Support/dev.warp.Warp-Stable/mcp(directory, not file)%APPDATA%\dev.warp.Warp-Stable\mcp(directory, not file)~/.local/share/dev.warp.Warp-Stable/mcp(directory, not file)2. Different Configuration Model
Unlike other clients in your codebase (Cursor, Claude Desktop, Windsurf, etc.) that use directly editable JSON files, Warp:
warp mcpcommands)Recommendation
You'll need a different integration approach for Warp. The current pattern of directly writing to a config file won't work. Consider:
warp mcpcommands) if it supports programmatic configurationWould you like me to help research Warp's CLI capabilities for programmatic MCP configuration?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tanthcstt please look at this comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@msanatan I see. It says there’s no evidence, but coderabbitai mentioned:
This is based on [Warp issue #6602](https://github.com/warpdotdev/Warp/issues/6602?utm_source=chatgpt.com) and it is the directory of logs file not mcp configuration file.
However, I found the path
%APPDATA%\Warp\mcp.jsonwith default setup on my local Windows machine, and the server configuration works with it. I’ll look for more evidence to confirm this.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do the docs say?
Your confirmation that it works is more important than CodeRabbit's comments
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@msanatan

There’s no official documentation that specifies this directory exactly.
I was only able to test it on my own machine.