keap-mcp

Keap (formerly Infusionsoft) MCP Service — a stateless HTTP MCP server wrapping the Keap CRM REST API v1, covering Contacts, Tags, Opportunities, Notes, Tasks, Campaigns, and Users.

Tech stack: Python 3.12 + uv + FastMCP (Starlette/Uvicorn)

Scope

Out of Keap's full REST API v1, this service implements 15 tools aligned to the resource categories MSPbots has historically synced (Contact, Tag Contact, Tags, Opportunities, Notes, Task, Campaigns, User).

Related MCP server: mcp-mautic

Authentication

Keap's REST API v1 is oauth2 on paper (authorization_code grant is the only flow in its official OpenAPI spec's securitySchemes), but Keap also offers a documented, self-service alternative that needs no redirect: Personal Access Tokens (PAT) and Service Account Keys (SAK) — see developer.infusionsoft.com/pat-and-sak. Either is generated inside the Keap app itself (Settings → API Settings, no developer-app registration or client secret needed) and used as a plain bearer token:

Authorization: Bearer <PAT or SAK>

This service uses that path — a single static token, no login/token-exchange step, no redirect. A Service Account Key (admin-level) is recommended over a Personal Access Token (single-user-scoped) for server-to-server use.

Quick Start

cd D:\claude\project\keap-mcp
uv sync

$env:KEAP_ACCESS_TOKEN="your_pat_or_sak"
uv run keap-mcp

Configuration

Copy .env.example to .env and fill in your values:

HEADER 授权参数说明

Claude Desktop Setup

{
  "mcpServers": {
    "keap": {
      "command": "uv",
      "args": ["run", "--directory", "D:/claude/project/keap-mcp", "keap-mcp"],
      "env": { "KEAP_ACCESS_TOKEN": "your_pat_or_sak" }
    }
  }
}

Transport Modes

stdio

$env:KEAP_ACCESS_TOKEN="your_pat_or_sak"
uv run keap-mcp

HTTP — single-tenant

$env:KEAP_ACCESS_TOKEN="your_pat_or_sak"
$env:MCP_TRANSPORT="http"
$env:AUTH_MODE="env"
uv run keap-mcp

HTTP — gateway / multi-tenant

$env:MCP_TRANSPORT="http"
$env:AUTH_MODE="gateway"
uv run keap-mcp
# Each request must include: X-Keap-Access-Token header

Available Tools (15)

Known Gaps

• ⚠️ Not yet tested against a live Keap account. All 15 tools have been checked structurally only (MCP handshake, tools-list, schema validity, /health, gateway 401 credential-gating) — no real PAT/SAK was available at build time. A free-trial Keap account application has been submitted separately; once approved, generate a Service Account Key and test end-to-end.

• Endpoint paths/params were verified directly against Keap's official OpenAPI v1 spec (https://crm.infusionsoft.com/app/v3/api-docs/V1, linked from the "Download OpenAPI specification" button on the docs site) — not guessed.

• PUT /contacts (upsert) documents a duplicate_option field in prose but it does not appear in the actual request schema — a documentation/schema mismatch on Keap's side, not implemented here since it's unconfirmed. Not built as a tool in this 15-tool scope anyway (only POST/GET contact operations were included).

• Scope is limited to the 15 operations above (Contacts/Tags/Opportunities/Notes/Tasks/Campaigns/Users read+core-write), not Keap's full REST API v1 surface (which also includes Companies, Products, Orders/Subscriptions, Affiliates, Files, Email sending, custom fields management, and webhooks).

API Reference

• Keap REST API v1 Documentation

• Personal Access Tokens & Service Account Keys