agent add mcp

AI Community

Skill notes

Step 1: Determine Scope

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: Global (user-scoped): ~/.warp/.mcp.json Project-scoped: {repo_root}/.warp/.mcp.json

Step 2: Gather Server Details

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

Step 3: Check and Prepare the Config File

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

Command-based server (stdio transport)

By default, Warp spawns stdio servers from the directory the config was discovered in: Project-scoped configs ({repo_root}/.warp/.mcp.json) run from the repo root. Global configs (~/.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:

URL-based server (HTTP/SSE streaming transport)

For environment variables containing secrets, use ${VAR_NAME} syntax — Warp will substitute the value from the user's environment at runtime.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@warpdotdev · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Required · Vendor-specific
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Determine Scope

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: Global (user-scoped): `~/.warp/.mcp.json` Project-scoped: `{repo_root}/.warp/.mcp.json`

02
Step 2: Gather Server Details

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

03
Step 3: Check and Prepare the Config File

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: 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_servers`

04
Step 4: Write the Server Configuration

Step 4: Write the Server Configuration

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.