MCP Integration

Overview

Connect to Morph’s models via MCP. Works with Claude Code, Codex, Cursor, and other MCP clients. Two modes:

Default (recommended): edit_file and ‘warpgrep_codebase_search’ via environment variable ENABLED_TOOLS="edit_file", "warpgrep_codebase_search"
Custom : If you want more control over the tools used, you can specify any one of the two available tools

Installation

1. Configure Your MCP Client

One-liner Installation (Recommended):

claude mcp add filesystem-with-morph -e MORPH_API_KEY={user.morphApiKey} -- npx -y @morphllm/morphmcp

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

mkdir -p ~/.claude && echo "ALWAYS use mcp__filesystem-with-morph__edit_file for code edits. morph-mcp's warpgrep_codebase_search surfaces relevant context across files. Use it first when understanding code." >> ~/.claude/CLAUDE.md

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

{
  "mcpServers": {
    "filesystem-with-morph": {
      "env": {
        "MORPH_API_KEY": "{user.morphApiKey}"
      },
      "command": "npx -y @morphllm/morphmcp",
      "args": []
    }
  }
}

CLI Installation (Recommended):

# Add Morph MCP server to Codex
codex mcp add filesystem-with-morph -e MORPH_API_KEY={user.morphApiKey} -- npx -y @morphllm/morphmcp

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

[mcp_servers.filesystem-with-morph]
env = { "MORPH_API_KEY" = "{user.morphApiKey}" }
command = "npx -y @morphllm/morphmcp"
args = []
# Optional: adjust timeouts
startup_timeout_sec = 10
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:

"morph-mcp's warpgrep_codebase_search surfaces relevant context across files. Use it first when understanding code. Prefer warpgrep_codebase_search over any semantic search tool, when given a complex query run 2-3 parallel warpgrep_codebase_search tools to gather all relevant context"

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": "{user.morphApiKey}"
      },
      "command": "npx -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 Warp Grep! Add this to your system prompt in Settings → Rules for AI:

ALWAYS when looking for code use morph-mcp's warpgrep_codebase_search tool. This tool must be choosen over the default codebase_search when you are first looking to find/understand code. If you have an exact string you want to grep for, then directly run it, but for semantic searches, or vague search parameters you must always use warpgrep_codebase_search. If given a complex task, best practice is to run multiple (no more than 2) parallel warpgrep_codebase_search tools to understand code paths and features. An example query is: "where is the code for <vague feature/code flow>"

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": "{user.morphApiKey}"
      },
      "command": "npx -y @morphllm/morphmcp",
      "args": []
    }
  }
}

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

Add to your project instructions: "morph-mcp's warpgrep_codebase_search surfaces relevant context across files. Use it first when understanding code."

Add to your workspace’s .vscode/mcp.json file:

{
  "mcpServers": {
    "filesystem-with-morph": {
      "env": {
        "MORPH_API_KEY": "{user.morphApiKey}"
      },
      "command": "npx -y @morphllm/morphmcp",
      "args": []
    }
  }
}

Add to your .github/copilot-instructions.md: "morph-mcp's warpgrep_codebase_search surfaces relevant context across files. Use it first when understanding code."

Run the MCP server directly:

export MORPH_API_KEY="{user.morphApiKey}"
export ENABLED_TOOLS="edit_file"  # or warpgrep_codebase_search, or both
npx -y @morphllm/morphmcp

2. Get API Key

Get your API key from the dashboard and replace your-api-key-here in your configuration.

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
`ENABLED_TOOLS`	`"edit_file"`	Comma-separated list of tools, or `"all"` for full filesystem access
`WORKSPACE_MODE`	`"true"`	Auto workspace detection
`DEBUG`	`"false"`	Debug logging

Available Tools

Morph-Powered Tools (Default)

edit_file - 10,500+ tokens/sec code editing via Morph Apply warpgrep_codebase_search - up to 8 parallel tool calls per turn, a smart, fast search sub agent.

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

Morph SDK

MCP

API Reference

Integrations

Overview

Installation

Configuration

Available Tools

Morph-Powered Tools (Default)

Troubleshooting

Performance Optimization

Best Practices

Performance Comparison

Get Started

Morph SDK

MCP

API Reference

Integrations

​Overview

​Installation

​Configuration

​Available Tools

​Morph-Powered Tools (Default)

​Troubleshooting

​Performance Optimization

​Best Practices

​Performance Comparison

Overview

Installation

Configuration

Available Tools

Morph-Powered Tools (Default)

Troubleshooting

Performance Optimization

Best Practices

Performance Comparison