Menú
Use this skill when helping users add MCP servers to their Warp configuration.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Fetch and display GitHub PR review comments for the current branch.
**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context — e.g. create/edit/delete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when the computer_use tool is available to the agent. Covers launching Warp and verifying UI behavior.
Repo-specific review guidance for warp. Only the categories declared overridable by the core review-pr skill may be specialized here.
Control and inspect the currently running local Warp application with the warpctrl CLI. Use this skill whenever the user asks the agent to manipulate Warp's own windows, tabs, panes, sessions, input buffer, themes, or UI surfaces; open a file in Warp; inspect local Warp state; or explain how to invoke Warp Control manually.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
| name | agent-add-mcp |
| description | Use this skill when helping users add MCP servers to their Warp configuration. |
Warp supports MCP servers via native config files. Follow these steps when helping a user add an MCP server.
If the user hasn't specified, ask whether they want to configure the server globally (for all projects) or project-scoped (for a specific repository only).
Config file paths:
~/.warp/.mcp.json{repo_root}/.warp/.mcp.jsonIf the user hasn't provided the server's connection details, use WebSearch to find the correct configuration for the named server.
If it's unclear whether the server should be run as a local CLI process (stdio transport) or connected to via URL (HTTP/SSE streaming transport), ask the user which they prefer.
Check whether the target config file exists.
If it does not exist, create it with mkdir -p for the directory and initialize it with an empty mcpServers wrapper key:
{
"mcpServers": {}
}
If it exists, read it to determine which top-level wrapper key is already in use. Recognized wrapper keys (in order of preference):
mcpServers (preferred)mcp_serversserversmcp.servers (nested under a mcp key)Preserve the existing wrapper key when writing. If the existing key is unrecognized or incompatible, switch to mcpServers.
Never remove existing server entries — only add or update the new server.
{
"mcpServers": {
"server-name": {
"command": "npx",
"args": ["-y", "@scope/package-name"],
"env": {
"API_KEY": "${API_KEY}"
}
}
}
}
By default, Warp spawns stdio servers from the directory the config was discovered in:
{repo_root}/.warp/.mcp.json) run from the repo root.~/.warp/.mcp.json, ~/.claude.json, etc.) run from the home directory.If the server's command or args are relative paths (e.g. ./tooling/mcp/server.js) or the server expects a specific cwd, set working_directory to override the default:
{
"mcpServers": {
"server-name": {
"command": "node",
"args": ["./tooling/mcp/server.js"],
"working_directory": "/absolute/path/to/repo"
}
}
}
{
"mcpServers": {
"server-name": {
"url": "https://example.com/mcp",
"env": {
"API_KEY": "${API_KEY}"
}
}
}
}
For environment variables containing secrets, use ${VAR_NAME} syntax — Warp will substitute the value from the user's environment at runtime.
.mcp.json files on save — no restart required.