Unable to connect claude desktop to Marketo engage | Community
Skip to main content
Level 1
April 29, 2026
Solved

Unable to connect claude desktop to Marketo engage

  • April 29, 2026
  • 5 replies
  • 128 views

Hi Team,

I am unable to connect Claude to Marketo MCP server.

This command didn’t work, the error I get is can’t connect to MCP server.

 

{
"mcpServers": {
"marketo": {
"type": "http",
"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"
}
}
}
}

 

Kindly help with the issue.

 

Thanks,

Deepthi.

Best answer by ManishRohilla

Hey Deepthi, I hit this same wall during the beta. Building on Sanford's point, there are really two separate things here:

  1. The access one already flagged: The MCP server's still closed beta, so until your instance is added you'll get that connection error no matter how clean the config looks. The support ticket is the right call.
  2. The other is Claude desktop specific: That "type": "http" block in the docs won't work with Claude desktop. Claude desktop's config is built for local servers, so for a remote one you have to bridge it with mcp-remote through npx, passing your Client ID, Secret and Munchkin ID as header arguments.

I wrote the whole thing up after I got it working, in case it saves you the headache: https://marketing-automation.ca/en-us/blog/connecting-ai-to-marketo-what-everyone-setting-this-up-should-know-first/. Feel free to give a shoutout if you’re in the beta and still facing issues, I’ll be happy to help!

5 replies

SanfordWhiteman
Level 10
April 29, 2026

You did create and fill in actual API credentials, right?

Level 2
April 29, 2026

Hi Sanford,

 

Yes created API user and got these values:

  • Client ID
  • Client Secret
  • Munchkin Account ID

Followed instructions as mentioned here: MCP Server | Adobe Marketo Engage

 

Thanks,

Deepthi.

SanfordWhiteman
Level 10
April 30, 2026

Don’t have anyone who both approved (internally) and got into the Beta!

Level 2
April 30, 2026

Hi Sanford,

 

Please guide me how should I proceed, should I raise a support ticket with Marketo to add to beta.

 

Thanks,

Deepthi.

SanfordWhiteman
Level 10
April 30, 2026

Yes.

Level 2
June 8, 2026

In case this is still open, another option is to reach out to your Marketo CSM. They can help confirm whether your instance has been enabled for the MCP beta and guide you through the onboarding process.

You can also submit the beta access request form here:

https://forms.cloud.microsoft/Pages/ResponsePage.aspx?id=Wht7-jR7h0OUrtLBeN7O4Y-uSf63sAxCmWyqMJg8eMFUMVZSVExSNDA3T0I4SEcwRDFSVTBGWU01Uy4u&origin=QRCode

If you're not yet enrolled in the beta, that could be the reason the MCP server connection is failing.

ManishRohilla
ManishRohillaAccepted solution
Level 2
June 9, 2026

Hey Deepthi, I hit this same wall during the beta. Building on Sanford's point, there are really two separate things here:

  1. The access one already flagged: The MCP server's still closed beta, so until your instance is added you'll get that connection error no matter how clean the config looks. The support ticket is the right call.
  2. The other is Claude desktop specific: That "type": "http" block in the docs won't work with Claude desktop. Claude desktop's config is built for local servers, so for a remote one you have to bridge it with mcp-remote through npx, passing your Client ID, Secret and Munchkin ID as header arguments.

I wrote the whole thing up after I got it working, in case it saves you the headache: https://marketing-automation.ca/en-us/blog/connecting-ai-to-marketo-what-everyone-setting-this-up-should-know-first/. Feel free to give a shoutout if you’re in the beta and still facing issues, I’ll be happy to help!