Keap MCP Server
Keap operates a real, first-party REMOTE MCP server. It is undocumented — the string "MCP" does not appear anywhere on developer.keap.com / developer.infusionsoft.com — but it is unambiguously theirs and unambiguously live: POSTing a JSON-RPC tools/list request to https://api.keap.com/mcp returns a well-formed MCP error object ({"jsonrpc":"2.0","error":{"code":-32001, "message":"Authentication required. Missing or invalid Authorization header."}}) together with a `WWW-Authenticate: Bearer realm="MCP Server"` header, while an arbitrary unrouted path on the same host returns a bare 404 and the REST gateway returns a completely different Apigee OAuth fault. The server advertises RFC 9728 protected-resource metadata and RFC 8414 authorization-server metadata, including OAuth 2.1 dynamic client registration.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Descriptor
Candidate descriptor · transport
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.