Prerequisite: You’ll need an account on Morph to get an API key.

​
What is Fast Apply?

Fast Apply is Morph’s intelligent code model that helps you seamlessly integrate code changes into existing files. It understands both the original code and your intended updates, producing clean, consistent results.

Morph Apply API

Programmatically apply code updates with precision

ModelSpeedAccuracy
morph-v3-fast4500+ tok/sec96%
morph-v3-large2500+ tok/sec98%
auto2500-4500 tok/sec~98%

​
Why Use Morph Fast Apply?

The best coding agents use Fast Apply models to integrate code changes into existing files.

This lets frontier models like GPT-4o, Claude, and Gemini focus on the hard reasoning tasks, while a dumber model like Morph Fast Apply handles the integration.

  • Patch/Diff edits are currently unreliable and often break existing code
  • Fast and Cheaper: Morph Fast Apply is fast

You should use Morph Fast Apply in an edit_file tool call. See the edit_file tool call for more details.

​
Example Usage

import { OpenAI } from 'openai';

const client = new OpenAI({
  apiKey: 'your-api-key',
  baseURL: 'https://api.morphllm.com/v1'
});

async function applyCodeUpdate(originalCode: string, updateSnippet: string) {
  const response = await client.chat.completions.create({
    model: "morph-v3-large",
    messages: [
      {
        role: "user",
        content: `<code>${originalCode}</code>\n<update>${updateSnippet}</update>`
      }
    ],
    stream: true
  });
  
  return response.choices[0].message.content;
}

​
MCP Server Usage

For applications using the MCP (Model Context Protocol) server, you can authenticate once and use the tools without providing the API key on each request:

# Authenticate and get session ID
curl "https://your-app.com/api/mcp?api_key=your-api-key"

# Response includes sessionId for subsequent requests
{
  "message": "Morph MCP Server - API Key Registered",
  "sessionId": "abc123...",
  "tools": [...],
  "usage": {
    "authenticate": "Add ?api_key=YOUR_API_KEY to this URL to authenticate",
    "subsequentRequests": "Include X-Session-ID header or session_id query parameter in subsequent requests"
  }
}

The MCP server stores your API key in memory for the session, so you only need to provide it once during the initial connection. The session ID is returned in the response headers and can be used for subsequent requests.