MCP Integration

Coding agents waste tokens on full-file rewrites and unfocused searches. Morph MCP gives your agent codebase_search (WarpGrep exploration subagent), edit_file (10,500 tok/s partial edits), and Reflex read-back tools that pull labeled production traffic — zero code changes.

Tool	Default	Description
`codebase_search`	Enabled	WarpGrep exploration subagent for your local workspace. Takes a natural-language query (“How does auth work?”) and runs parallel grep + file reads over multiple turns to find relevant files and line ranges. Use first when exploring unfamiliar code.
`github_codebase_search`	Enabled	WarpGrep exploration for public GitHub repositories — no clone required. Takes `owner/repo` plus a natural-language query. Use when debugging third-party dependencies or investigating upstream bugs.
`edit_file`	Disabled	Morph Fast Apply: 10,500+ tok/s partial edits using `// ... existing code ...` placeholders. Off by default so it doesn’t collide with client-native editors — enable by setting `DISABLED_TOOLS=""` in the MCP env.
`list_reflexes`	Enabled	The Reflex classifiers on your account: the 11 built-ins (jailbreak, guardrail, stuck-in-a-loop, user-frustrated, …) plus any you trained.
`reflex_summary`	Enabled	Firing rates per traced model per Reflex, aggregated from recent production traffic. The fastest way to compare a canary model against your incumbent.
`get_reflex_traces`	Enabled	Individual traced turns with their Reflex labels and input/output snippets. Filter by conversation, model, Reflex, or label.

One command to install:

npx -y @morphllm/morph-setup --morph-api-key YOUR_API_KEY

Logged in? Your API key auto-fills above. Otherwise, get it from your dashboard.

Installation (All Clients)

1. Get Your API Key

Get your API key from the dashboard.

2. Configure Your MCP Client

One-liner Installation (Recommended):

claude mcp add filesystem-with-morph --scope user -e MORPH_API_KEY=YOUR_API_KEY -- npx --prefer-offline -y @morphllm/morphmcp

Configure Claude to prefer Morph: Add this to your global Claude config:

mkdir -p ~/.claude && echo "Fast Apply: IMPORTANT: Use \`edit_file\` over \`str_replace\` or full file writes. It works with partial code snippets—no need for full file content.
Warp Grep: warp-grep is a subagent that takes in a search string and tries to find relevant context. Best practice is to use it at the beginning of codebase explorations to fast track finding relevant files/lines. Do not use it to pin point keywords, but use it for broader semantic queries. \"Find the XYZ flow\", \"How does XYZ work\", \"Where is XYZ handled?\", \"Where is <error message> coming from?\"" >> ~/.claude/CLAUDE.md

Manual Config File Method:Create or edit .claude.json in your workspace:

{
  "mcpServers": {
    "filesystem-with-morph": {
      "env": {
        "MORPH_API_KEY": "YOUR_API_KEY"
      },
      "command": "npx --prefer-offline -y @morphllm/morphmcp",
      "args": []
    }
  }
}

CLI Installation (Recommended):

# Add Morph MCP server to Codex
codex mcp add morph-mcp --env MORPH_API_KEY=YOUR_API_KEY -- npx --prefer-offline -y @morphllm/morphmcp

Manual Config File:Add to ~/.codex/config.toml:

[mcp_servers.filesystem-with-morph]
env = { "MORPH_API_KEY" = "YOUR_API_KEY" }
command = "npx --prefer-offline -y @morphllm/morphmcp"
args = []
# Optional: adjust timeouts
startup_timeout_sec = 120
tool_timeout_sec = 60

CLI Management: Use codex mcp list to see configured servers and codex mcp remove filesystem-with-morph to remove.

Add to your AGENTS.md:

Fast Apply: IMPORTANT: Use `edit_file` over `str_replace` or full file writes. It works with partial code snippets—no need for full file content.
Warp Grep: warp-grep is a subagent that takes in a search string and tries to find relevant context. Best practice is to use it at the beginning of codebase explorations to fast track finding relevant files/lines. Do not use it to pin point keywords, but use it for broader semantic queries. "Find the XYZ flow", "How does XYZ work", "Where is XYZ handled?", "Where is <error message> coming from?"

Add to your Cursor MCP by clicking this button:

OR add to your Cursor MCP config file:Location: ~/.cursor/mcp.json

{
  "mcpServers": {
    "morph-mcp": {
      "env": {
        "MORPH_API_KEY": "YOUR_API_KEY"
      },
      "command": "npx --prefer-offline -y @morphllm/morphmcp",
      "args": []
    }
  }
}

Global Config: This configuration works across all your projects automatically. The MCP server detects workspace boundaries via .git, package.json, and other project indicators.

Make Cursor use Morph tools! Add this to your system prompt in Settings → Rules for AI:

Fast Apply: IMPORTANT: Use `edit_file` over `str_replace` or full file writes. It works with partial code snippets—no need for full file content.
Warp Grep: warp-grep is a subagent that takes in a search string and tries to find relevant context. Best practice is to use it at the beginning of codebase explorations to fast track finding relevant files/lines. Do not use it to pin point keywords, but use it for broader semantic queries. "Find the XYZ flow", "How does XYZ work", "Where is XYZ handled?", "Where is <error message> coming from?"

Add to your Claude Desktop config file:macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "filesystem-with-morph": {
      "env": {
        "MORPH_API_KEY": "YOUR_API_KEY"
      },
      "command": "npx --prefer-offline -y @morphllm/morphmcp",
      "args": []
    }
  }
}

Restart Required: Completely quit and restart Claude Desktop to load the new configuration.

Add to your project instructions:

Fast Apply: IMPORTANT: Use `edit_file` over `str_replace` or full file writes. It works with partial code snippets—no need for full file content.
Warp Grep: warp-grep is a subagent that takes in a search string and tries to find relevant context. Best practice is to use it at the beginning of codebase explorations to fast track finding relevant files/lines. Do not use it to pin point keywords, but use it for broader semantic queries. "Find the XYZ flow", "How does XYZ work", "Where is XYZ handled?", "Where is <error message> coming from?"

CLI Installation (Recommended):

code --add-mcp '{"name":"morph-mcp","command":"npx","args":["--prefer-offline","-y","@morphllm/morphmcp"],"envVars":{"MORPH_API_KEY":"YOUR_API_KEY"}}'

Or use the Command Palette: run MCP: Add Server, enter the server details, and select Global to save to your user profile.Manual Config File:Run MCP: Open User Configuration from the Command Palette, or add to your user-level mcp.json:

{
  "mcpServers": {
    "filesystem-with-morph": {
      "env": {
        "MORPH_API_KEY": "YOUR_API_KEY"
      },
      "command": "npx --prefer-offline -y @morphllm/morphmcp",
      "args": []
    }
  }
}

Add to your .github/copilot-instructions.md:

Fast Apply: IMPORTANT: Use `edit_file` over `str_replace` or full file writes. It works with partial code snippets—no need for full file content.
Warp Grep: warp-grep is a subagent that takes in a search string and tries to find relevant context. Best practice is to use it at the beginning of codebase explorations to fast track finding relevant files/lines. Do not use it to pin point keywords, but use it for broader semantic queries. "Find the XYZ flow", "How does XYZ work", "Where is XYZ handled?", "Where is <error message> coming from?"

Run the MCP server directly:

export MORPH_API_KEY="YOUR_API_KEY"
npx --prefer-offline -y @morphllm/morphmcp

3. Test Installation

Claude Code: Type /mcp and /tools to see Morph’s edit_file tool
Codex: Run codex mcp list to verify server is configured, then make edit requests
Cursor/VS Code: Make any code edit request - should use Morph automatically
Manual: Check server logs show “MCP Server started successfully”

Configuration

Variable	Default	Description
`MORPH_API_KEY`	Required	Your API key
`WORKSPACE_MODE`	`"true"`	Auto workspace detection
`DEBUG`	`"false"`	Debug logging

Advanced Configuration

Variable	Default	Description
`MORPH_API_URL`	`https://api.morphllm.com`	Override the Morph API base URL (for proxies)
`MORPH_WARP_GREP_TIMEOUT`	`30000`	Timeout for Warp Grep model calls in milliseconds

Custom API endpoint — For enterprise deployments or custom authentication flows:

{
  "mcpServers": {
    "morph-mcp": {
      "env": {
        "MORPH_API_KEY": "<user-jwt-token>",
        "MORPH_API_URL": "https://your-proxy.example.com"
      },
      "command": "npx --prefer-offline -y @morphllm/morphmcp",
      "args": []
    }
  }
}

Your proxy receives requests to /v1/chat/completions with the token in the Authorization: Bearer header. Forward these to https://api.morphllm.com/v1/chat/completions after handling auth/billing. Warp Grep timeout — Increase for large codebases or slow networks:

{
  "mcpServers": {
    "morph-mcp": {
      "env": {
        "MORPH_API_KEY": "sk-xxx",
        "MORPH_WARP_GREP_TIMEOUT": "60000"
      },
      "command": "npx --prefer-offline -y @morphllm/morphmcp",
      "args": []
    }
  }
}

Available Tools

codebase_search, github_codebase_search, and the three Reflex tools (list_reflexes, reflex_summary, get_reflex_traces) are enabled out of the box. edit_file ships disabled to avoid conflicting with client-native editors — opt in by setting DISABLED_TOOLS="" (or any value that doesn’t include edit_file) in the MCP server env. The Reflex tools read production results back: which classifiers run on your account, firing rates per traced model (canary vs. incumbent), and the individual conversations that fired. They need traced traffic to read — see the tracing guide.

{
  "mcpServers": {
    "morph-mcp": {
      "env": {
        "MORPH_API_KEY": "YOUR_API_KEY",
        "DISABLED_TOOLS": ""
      },
      "command": "npx --prefer-offline -y @morphllm/morphmcp",
      "args": []
    }
  }
}

Troubleshooting

Server won’t start: Check API key, Node.js 16+, run npm cache clean --force
Tools missing: Restart client, validate JSON config
Workspace issues: Add .git or package.json, or set WORKSPACE_MODE="false"
Slow performance: Use edit_file over write_file, check network to api.morphllm.com

Performance Optimization

Best Practices

Use edit_file for modifications: Much faster than reading + writing entire files
Minimize edit scope: Include only the sections that need changes
Batch related edits: Make multiple changes in a single edit_file call

Performance Comparison

Method	Speed	Use Case
`edit_file` (Morph)	~11 seconds	Code modifications, updates
Search & replace	~20 seconds	Simple text substitutions
Traditional read/write	~60 seconds	Full file rewrites

Get Started

Models

API Reference

Integrations

Installation (All Clients)

Configuration

Advanced Configuration

Available Tools

Troubleshooting

Performance Optimization

Best Practices

Performance Comparison

​Installation (All Clients)

​Configuration

​Advanced Configuration

​Available Tools

​Troubleshooting

​Performance Optimization

​Best Practices

​Performance Comparison

Installation (All Clients)

Configuration

Advanced Configuration

Available Tools

Troubleshooting

Performance Optimization

Best Practices

Performance Comparison