Morph MCP

Supercharge your coding agent. One MCP with two specialized tools for faster edits and smarter retrieval.

Using OpenCode? Install the OpenCode plugin instead of this MCP server. It ships the same Fast Apply + WarpGrep tools plus automatic context compaction and tool routing that the MCP protocol cannot provide.

Which integration should I use?

| Harness | Use | Tools | |---------|-----|-------| | OpenCode | @morphllm/opencode-morph-plugin | Fast Apply + WarpGrep + GitHub search + compaction + tool routing | | Cursor, Claude Code, VS Code, Windsurf, Zed, any MCP host | this server (@morphllm/morphmcp) | Fast Apply + WarpGrep + GitHub search |

Conversation compaction is only available through the OpenCode plugin. The MCP protocol gives a server no access to the host's conversation history, so compaction can't be exposed as an MCP tool — use the plugin if you want it.

Tools

| Tool | What it does | |------|-------------| | edit_file | Apply code changes at 10,500+ tokens/sec with 98% accuracy | | codebase_search | Natural-language code exploration sub-agent backed by WarpGrep under the hood | | github_codebase_search | Search any public GitHub repo by URL or owner/repo shorthand |

All three tools are always exposed. Clients can manage tool visibility on their side.

Quick Start

Claude Code

claude mcp add morph-mcp -e MORPH_API_KEY=sk-xxx -- npx -y @morphllm/morphmcp

Cursor

Add to .cursor/mcp.json:

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

VS Code

Add to .vscode/mcp.json:

{
  "mcp": {
    "servers": {
      "morph-mcp": {
        "command": "npx",
        "args": ["-y", "@morphllm/morphmcp"],
        "env": {
          "MORPH_API_KEY": "sk-xxx"
        }
      }
    }
  }
}

How the Tools Work

edit_file

Applies code edits using Morph's Fast Apply model. The agent sends partial code with // ... existing code ... placeholders, and Fast Apply merges it into the full file.

Input:
  path: "src/api.ts"
  code_edit: |
    export async function fetchData(endpoint: string) {
      // ... existing code ...
      const response = await fetch(endpoint, { 
        headers,
        timeout: 5000  // added timeout
      });
      // ... existing code ...
    }
  instruction: "Add 5 second timeout to fetch call"

Output: Git-style unified diff showing exactly what changed

codebase_search

codebase_search is the MCP-facing wrapper around WarpGrep. Ask a natural-language question about what you want to understand and it will use WarpGrep under the hood to locate relevant files and line ranges. It does not accept regex or symbol-only queries.

Good: Where does auth get handled, what are the different oauth methods supported? Bad: auth()

Input:
  search_string: "Where does auth get handled, what are the different oauth methods supported?"
  repo_path: "/Users/me/project"
  search_type: "default"  # optional: "default" or "node_modules"

Output: List of files with specific line ranges + actual code content

Configuration

| Variable | Description | Default | |----------|-------------|---------| | MORPH_API_KEY | Your API key from morphllm.com | Required | | MORPH_API_URL | Override Morph API base URL for custom proxies | https://api.morphllm.com | | MORPH_WARP_GREP_TIMEOUT | Timeout for warp grep model calls in ms | 30000 |

Get an API Key

1. Sign up at morphllm.com
2. Go to dashboard → API Keys
3. Keys start with sk- or morph-

Troubleshooting

npm error code ETARGET ... No matching version found for ...

This happens when npx resolves against a stale local registry cache — most often with npx --prefer-offline, which intentionally avoids refreshing metadata. The examples above no longer use --prefer-offline for this reason. If you still hit it:

npm cache clean --force      # then retry: npx -y @morphllm/morphmcp
# or run it with bun, which fetches fresh metadata:
bunx @morphllm/morphmcp

Links

• Documentation
• MCP Quickstart
• OpenCode plugin

License

MIT