Marketo Engage MCP Server

Claude Desktop claude-desktop

To connect to Claude Desktop, download marketo-mcp-bridge.zip and unpack it. Put marketo-mcp-bridge.mjs into a known location and use its absolute path in the configuration below.

You also need a supported LTS version of Node.js installed on your computer. The bridge does not require additional npm packages.

1. Open Claude Desktop.
2. Open claude_desktop_config.json. On macOS, the file is in ~/Library/Application Support/Claude/. On Windows, it is in %APPDATA%\Claude\. In versions with the developer settings menu, select Settings > Developer > Edit Config to open it.
3. Add the following entry under mcpServers, preserving any existing settings. Replace the path and credential placeholders with your values:

{
  "mcpServers": {
    "marketo-mcp": {
      "command": "node",
      "args": ["/path/to/marketo-bridge/marketo-mcp-bridge.mjs"],
      "env": {
        "MARKETO_MCP_PROD_CLIENT_ID": "<your-client-id>",
        "MARKETO_MCP_PROD_CLIENT_SECRET": "<your-client-secret>",
        "MARKETO_MCP_PROD_MUNCHKIN_ID": "<your-munchkin-id>"
      }
    }
  }
}

1. Restart Claude Desktop.

If Claude Desktop cannot find Node.js, replace node in command with the absolute path to your Node.js executable. For more information, see Connect to local MCP servers.

Cursor cursor

Add the marketo entry under mcpServers in ~/.cursor/mcp.json for your user account or .cursor/mcp.json in your project directory. Preserve any existing servers and replace the credential placeholders with your values:

{
  "mcpServers": {
    "marketo": {
      "url": "https://marketo-mcp.adobe.io/mcp",
      "headers": {
        "X-Marketo-Client-Id": "YOUR-CLIENT-ID",
        "X-Marketo-Client-Secret": "YOUR-CLIENT-SECRET",
        "X-Marketo-Munchkin-Id": "YOUR-MUNCHKIN-ID"
      }
    }
  }
}

Open Customize in Cursor and confirm that the server is turned on. For more information, see Cursor MCP configuration.

Claude Code (CLI) claude-code

Run the following command in your terminal, substituting your credentials:

claude mcp add --transport http marketo \
  https://marketo-mcp.adobe.io/mcp \
  --header "X-Marketo-Client-Id: YOUR-CLIENT-ID" \
  --header "X-Marketo-Client-Secret: YOUR-CLIENT-SECRET" \
  --header "X-Marketo-Munchkin-Id: YOUR-MUNCHKIN-ID"

The command adds the server for the current project and your user account. To make it available across projects, add --scope user. In Claude Code, run /mcp to check the connection. For more information, see Claude Code MCP configuration.

OpenAI Codex codex

Add the following to ~/.codex/config.toml, preserving any existing configuration:

[mcp_servers.marketo]
url = "https://marketo-mcp.adobe.io/mcp"

[mcp_servers.marketo.env_http_headers]
X-Marketo-Client-Id = "MARKETO_CLIENT_ID"
X-Marketo-Client-Secret = "MARKETO_CLIENT_SECRET"
X-Marketo-Munchkin-Id = "MARKETO_MUNCHKIN_ID"

Set MARKETO_CLIENT_ID, MARKETO_CLIENT_SECRET, and MARKETO_MUNCHKIN_ID in the environment of the process that runs Codex. The values in env_http_headers are environment variable names, not credentials.

Start a new Codex session and run /mcp to check the connection. For more information, see Codex MCP configuration.

Gemini CLI

To add the Marketo Engage MCP server to Gemini CLI, add the following mcpServers entry to .gemini/settings.json in your project directory or ~/.gemini/settings.json for your user account. Preserve any existing settings and replace the credential placeholders with your values.

{
  "mcpServers": {
    "marketo": {
      "httpUrl": "https://marketo-mcp.adobe.io/mcp",
      "headers": {
        "X-Marketo-Client-Id": "YOUR-CLIENT-ID",
        "X-Marketo-Client-Secret": "YOUR-CLIENT-SECRET",
        "X-Marketo-Munchkin-Id": "YOUR-MUNCHKIN-ID"
      }
    }
  }
}

Alternatively, set MARKETO_CLIENT_ID, MARKETO_CLIENT_SECRET, and MARKETO_MUNCHKIN_ID in your shell environment and run the following command. The shell expands the variables before the CLI stores the header values in your user configuration:

gemini mcp add --transport http -s user marketo https://marketo-mcp.adobe.io/mcp \
  -H "X-Marketo-Client-Id: $MARKETO_CLIENT_ID" \
  -H "X-Marketo-Client-Secret: $MARKETO_CLIENT_SECRET" \
  -H "X-Marketo-Munchkin-Id: $MARKETO_MUNCHKIN_ID"

Restart the session and run /mcp to check the connection. For more information, see Gemini CLI MCP configuration.

VS Code with GitHub Copilot vscode

Use the portable Copilot configuration for the latest versions of VS Code. Add the following entry under mcpServers in ~/.copilot/mcp-config.json, or $COPILOT_HOME/mcp-config.json if you set COPILOT_HOME. Preserve any existing servers:

{
  "mcpServers": {
    "marketo": {
      "type": "http",
      "url": "https://marketo-mcp.adobe.io/mcp",
      "headers": {
        "X-Marketo-Client-Id": "${MARKETO_CLIENT_ID}",
        "X-Marketo-Client-Secret": "${MARKETO_CLIENT_SECRET}",
        "X-Marketo-Munchkin-Id": "${MARKETO_MUNCHKIN_ID}"
      }
    }
  }
}

Set the three environment variables in the environment that runs VS Code or the remote host that connects to the server. Start a new Copilot session and review any server trust prompts.

To use the guided setup instead, run MCP: Add Server, select HTTP (HTTP or Server-Sent Events), enter the server URL, and choose Global > Copilot Global. Then add the headers to the saved configuration.

Older versions also support MCP: Open User Configuration or .vscode/mcp.json. These files use servers instead of mcpServers and ${env:MARKETO_CLIENT_ID} syntax for environment variables. Do not mix the two formats. For more information, see VS Code MCP configuration.

Copilot Studio

Turn on generative orchestration for your agent before adding MCP tools. Use a custom connector to define all three required Marketo headers.

On your agent’s Tools page, select Add a tool > New tool > Custom connector. In Power Apps, create a custom connector and use the Swagger editor to enter the following definition:

swagger: '2.0'
info:
  title: Marketo MCP Server
  description: Connect to the Marketo MCP server.
  version: 1.0.0
host: marketo-mcp.adobe.io
basePath: /
schemes:
  - https
paths:
  /mcp:
    post:
      summary: Marketo MCP Server
      description: Invoke the Marketo MCP server.
      operationId: InvokeServer
      x-ms-agentic-protocol: mcp-streamable-1.0
      parameters:
        - name: X-Marketo-Client-Id
          in: header
          description: Client ID.
          type: string
          required: true
        - name: X-Marketo-Client-Secret
          in: header
          description: Client secret.
          type: string
          required: true
        - name: X-Marketo-Munchkin-Id
          in: header
          description: Munchkin ID.
          type: string
          required: true
      responses:
        '200':
          description: Immediate Response
securityDefinitions: {}
security: []

Save or update the connector, return to Copilot Studio, and add it to your agent. Create a connection and supply the three header values when prompted. Keep credentials out of the OpenAPI definition and agent instructions. For more information, see Connect an agent to an existing MCP server.

Glean glean

To connect Glean to the Marketo Engage MCP server, follow Glean’s remote MCP setup instructions to add https://marketo-mcp.adobe.io/mcp. Check the Connectors catalog first. For a custom or unlisted server, use Admin console > Platform > Tools > Import tools from MCP server.

The Glean support team must configure the custom headers below. Include the server name, URL, and required header names in your support request, and coordinate secure handling of the credential values. A standard API key connection alone does not supply all three headers.

After Glean confirms that the headers are active, test the connection with a read-only request before making the tools available to other users.

Other tools other-tools

Adobe hosts the Marketo MCP server and exposes it at a public URL. Any MCP client that supports remote servers over streamable HTTP transport may connect to it.
Clients that support direct remote HTTP connections do not need a bridge or locally installed server software. If your tool is not listed above, use the connection details below to configure it manually.

Connection details:

Authentication headers:

Send all three headers with each request. Where you enter the server URL and headers depends on your tool, so consult its MCP documentation.

If your tool accepts a JSON configuration, start with the Cursor or VS Code examples, and adjust the keys and environment variable syntax to match your tool’s schema.