# LeadFoxConnect [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/LeadFox-Shay/leadfoxconnect  
**GitHub Stars:** 0  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/leadfoxconnect

## Description
Marketo MCP server for AI. 130 tools to operate Marketo from Claude, Cursor, or ChatGPT.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "leadfoxconnect": {
    "url": "https://app.leadfoxconnect.com/mcp"
  }
}
```

## Documentation

## What LeadFoxConnect MCP server does

LeadFoxConnect MCP server exposes Adobe Marketo Engage operations through the Model Context Protocol. Its 130 purpose-built tools cover leads, smart campaigns, emails, forms, landing pages, programs, analytics, and bulk exports. An AI client can use natural-language requests to inspect Marketo data, analyze campaign activity, and perform supported changes.

Typical tasks include finding leads based on recent form activity, reviewing lead-scoring distributions, locating inactive smart campaigns, checking email performance, and creating an email in a specified folder from a named template. The material also describes multi-instance support for agencies and consultants managing multiple client Marketo accounts.

## How it works

The MCP server is hosted rather than installed from this repository. Clients connect to the streamable HTTP endpoint at `https://app.leadfoxconnect.com/mcp`. Claude.ai and ChatGPT custom connectors use a sign-in flow with per-user OAuth. Claude Desktop, Cursor, Windsurf, and other MCP clients can connect through the same endpoint with a per-tenant API key.

Marketo data passes through between the connected AI client and the customer’s Marketo instance. The service states that it does not persist Marketo records. Credentials are kept in a managed secrets vault and encrypted with customer-managed keys. Tool calls are audited, and the service describes role permissions, parameter rules, and confirmation flows for high-risk operations.

## Setup and configuration

Access requires LeadFoxConnect beta enrollment. The README directs users to request access through the LeadFoxConnect website; detailed setup instructions for MCP clients are provided in the onboarding email after activation.

For Claude.ai or ChatGPT, add a custom connector, enter the hosted MCP URL, and sign in when prompted. For desktop or developer clients, configure streamable HTTP and authenticate with the tenant API key supplied through onboarding. No local package or server process is identified in the provided material.

## Tools and capabilities

The documented tool areas include:

- Querying and operating on Marketo leads
- Inspecting and managing campaigns
- Working with emails and templates
- Managing forms and landing pages
- Accessing programs and analytics
- Running bulk exports
- Supporting multiple Marketo instances

LeadFoxConnect MCP server is intended for Marketo practitioners, marketing operations professionals, and teams that want an AI client to carry out recurring Marketo work.

## Limitations and notes

The service is in closed beta, launched on April 14, 2026. It is free during the beta period; the README says future paid plans will be priced per connected Marketo instance and will include a free tier. Availability therefore depends on beta access rather than public self-hosting.

The repository contains installation documentation and MCP Registry metadata, while the MCP server itself is hosted. The stated infrastructure is hosted in the European Union. The project is licensed under MIT. LeadFoxConnect MCP server is an independent product and is not described as Adobe’s Marketo MCP implementation.

_Full upstream README: https://allmcps.com/mcp/leadfoxconnect/readme_