pancake-api-mcp
This server provides an MCP interface for AI assistants to access Pancake API documentation and, optionally, interact with the live API.
Search Documentation: Search across REST endpoints, webhook events, guide sections, and component schemas with ranked results.
Explore Endpoints: List all 31 REST endpoints, filter by tag or keyword, and get full contract details (parameters, request/response schemas, examples).
Inspect Webhooks: List all 5 webhook events and retrieve their payload schemas and sample JSON.
Read Guides: Browse 11 conceptual guide sections (authentication, rate limits, usage flow, etc.) and read full narrative text.
Check Configuration: Verify which access tokens are configured without exposing sensitive values.
Live API Calls (Optional): If tokens are configured, make HTTP requests to any endpoint with automatic token selection; set
PANCAKE_READ_ONLY=trueto restrict to read-only operations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@pancake-api-mcp How do I authenticate to the Pancake API?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
pancake-api-mcp
A Model Context Protocol (MCP) server that serves the Pancake API documentation to your AI assistant.
Point Claude Desktop, Cursor, or any MCP client at this server and your AI can read the Pancake docs on its own — search endpoints, pull a single endpoint's full contract (parameters, request body, response schema with every $ref expanded), inspect webhook payloads, and read the authentication / rate-limit / webhook-setup guides — without you copy-pasting anything.
The docs are bundled as a static snapshot of the official OpenAPI spec, so documentation lookups are self-contained and offline.
Optionally, configure your access tokens in the server's environment and the call_endpoint tool can also call the live Pancake API for you — the right token (access_token or page_access_token) is picked from each endpoint's OpenAPI security scheme and attached automatically. Without tokens the server stays fully offline and documentation-only.
What's inside
31 REST endpoints across Pages, Conversations, Messages, Statistics, Customers, Posts, Tags, Users, Call logs, Export Data, Page's Contents, and Chat Plugin.
5 webhook events:
messaging,conversation,post,subscription,connect_status— each with its full payload schema and an example.11 guides: authentication & tokens, rate limits, the recommended API usage flow, webhook setup, event types, suspension rules, and best practices.
Related MCP server: Dedalus MCP Documentation Server
Tools
Tool | Input | Returns |
|
| Ranked matches with type, id, and a snippet — start here to discover things |
|
| REST endpoints grouped by tag (id, method, path, summary) |
|
| Full endpoint contract as markdown |
| — | All webhook events with summaries |
|
| Webhook payload schema + example |
| — | Guide section ids + titles |
|
| Full guide section |
| — | Which tokens are configured (masked), plus the other env settings |
|
| Live call to the Pancake API — status + response body |
Every endpoint, webhook, and guide is also exposed as an MCP resource (pancake-api://endpoint/..., pancake-api://webhook/..., pancake-api://guide/...) for clients that browse resources.
Install
Requires Node.js 18+.
git clone https://github.com/<your-org>/pancake-api-mcp.git
cd pancake-api-mcp
npm install
npm run buildThis produces dist/index.js, the server entry point.
Configure your access tokens (optional)
Pancake uses two token types, both passed as a query parameter. Set them as environment variables of the MCP server and call_endpoint will attach the right one per endpoint — you never paste a token into a chat, and tokens are never accepted as tool input.
Variable | Query param | Needed for | How to get it |
|
| 2 account-level endpoints under | Pancake → Account → Personal settings → API Access Token. Valid up to 90 days. |
|
| 24 page-level endpoints under | Page → Settings → Tools, or |
Optional extras:
Variable | Default | Effect |
| — | Default value for |
|
| When |
|
| Timeout for live API calls |
Ask your assistant to run auth_status to verify the setup — it reports which variables are set without revealing their values.
Writes are enabled by default. With a page token configured,
call_endpointcan really send messages to customers, change tags, and delete data. SetPANCAKE_READ_ONLY=trueif you only want the assistant to read. Tokens are read from the environment only, redacted from every tool response and error message, and never written to logs.
Connect it to your AI client
Claude Desktop
Edit your claude_desktop_config.json:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"pancake-api": {
"command": "node",
"args": ["/absolute/path/to/pancake-api-mcp/dist/index.js"],
"env": {
"PANCAKE_USER_ACCESS_TOKEN": "your-user-access-token",
"PANCAKE_PAGE_ACCESS_TOKEN": "your-page-access-token",
"PANCAKE_PAGE_ID": "optional-default-page-id"
}
}
}
}Drop the env block entirely to run in offline documentation-only mode.
Restart Claude Desktop. You should see the pancake-api tools appear.
Cursor
In Settings → MCP → Add new global MCP server (or edit ~/.cursor/mcp.json):
{
"mcpServers": {
"pancake-api": {
"command": "node",
"args": ["/absolute/path/to/pancake-api-mcp/dist/index.js"],
"env": {
"PANCAKE_PAGE_ACCESS_TOKEN": "your-page-access-token"
}
}
}
}Replace /absolute/path/to/pancake-api-mcp with the real path where you cloned this repo.
Try it
Once connected, ask your AI things like:
"Using the Pancake docs, how do I authenticate?"
"What endpoint lists conversations for a page, and what parameters does it take?"
"Show me the payload of the
messagingwebhook.""Search the Pancake docs for anything about tags."
And, with tokens configured:
"Check my Pancake token setup." (
auth_status)"List the last 60 conversations of page 12345." (
call_endpoint)"Send 'thanks for your order' to conversation X." (a write — confirm before you say yes)
Development
npm run build # compile TypeScript to dist/
npm run dev # tsc --watch
npm run inspect # open the MCP Inspector against the built server
npm run sync-spec # (maintainer) refresh spec/ from ../pancake_api_doc/openapiUpdating the bundled docs
The OpenAPI snapshot lives in spec/openapi.yaml and spec/webhook.yaml. A maintainer refreshes them from the source docs project with:
npm run sync-spec # assumes ../pancake_api_doc alongside this repo
npm run sync-spec -- /path/to/pancake_api_doc # or pass the docs repo explicitly
npm run buildLicense
MIT — see LICENSE.
Available Tools
7 toolsget_endpointA
Get the full contract of a single Pancake REST API endpoint as markdown.
Includes the base URL(s), authentication, all parameters, the request body schema, and the response schema — with $ref schemas expanded into a readable field list — plus any examples. Pass an id from search_docs or list_endpoints.
Inputs: id (required).
get_guideA
Get the full text of a single Pancake API guide section.
Returns narrative documentation such as authentication (how to obtain and use access tokens), rate limits, the recommended integration flow, or webhook setup. Pass an id from list_guides or search_docs.
Inputs: id (required).
get_webhookA
Get the full payload schema and an example for a single Pancake webhook event.
Returns the event's description, the payload structure ($ref schemas expanded into a readable field list), and a sample JSON body. Pass an event name from list_webhooks or search_docs.
Inputs: event (required).
list_endpointsA
List all Pancake REST API endpoints, grouped by tag.
Returns each endpoint's id (e.g. "GET /pages/{page_id}/conversations"), method, path, and summary. Pass the id to get_endpoint for the full contract (parameters, request body, response schema, examples). Optionally filter by tag or keyword.
Inputs: tag, keyword.
list_guidesA
List the Pancake API guide sections (narrative documentation).
These cover concepts rather than a single endpoint: authentication and tokens, rate limits, the recommended API usage flow, webhook setup, event types, suspension rules, and best practices. Pass a guide id to get_guide for the full text.
Inputs: no named parameters.
list_webhooksA
List all Pancake webhook events.
Returns each event's name and summary. Pass an event name to get_webhook for the full payload schema and an example. Webhooks are HTTP POST notifications Pancake sends to your registered endpoint in real time.
Inputs: no named parameters.
search_docsA
Search the entire Pancake API documentation and return ranked matches.
This is the entry point for exploring the docs: search first, then fetch full detail with get_endpoint, get_webhook, or get_guide using the returned id.
Searches across REST endpoints, webhook events, guide sections (authentication, rate limits, setup...), and component schemas. Each result includes its type, the id to pass to the matching get_* tool, and a short snippet.
Inputs: query (required), area, limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: search_docs is the cross-cutting entry point, list_* tools provide overviews, and get_* tools retrieve specific details for endpoints, webhooks, and guides. There is no overlap or ambiguity between them.
All tool names follow the consistent verb_noun pattern: search_docs, list_endpoints, get_endpoint, list_webhooks, get_webhook, list_guides, get_guide. The verbs (search, list, get) and nouns are uniformly applied across the three resource types.
Seven tools is well-scoped for a documentation explorer. Each tool serves a necessary role in the search/list/detail workflow, and there are no redundant or missing operations.
The tool set fully covers the stated purpose of exploring Pancake API documentation: search across all content, list all endpoints/webhooks/guides, and retrieve full details for each. There are no obvious gaps or dead ends in the workflow.
Related MCP Connectors
Publish your API docs so AI assistants can look up endpoints and call your API correctly.
Read-only search and Markdown pages from the OpenPlanr docs, for coding agents.
Tailor Platform for AI assistants: search, list and read the platform documentation.
Versioned documentation registry and semantic search for AI tools and coding assistants.
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides AI assistants with access to Payman's documentation, helping developers build integrations more efficiently through enhanced contextual support.5ISC
- AlicenseAqualityDmaintenanceEnables AI-powered querying and management of documentation through markdown file serving, keyword search, and OpenAI-based Q\&A capabilities. Supports document indexing, analysis, and agent handoffs with rate limiting protection.5MIT
- AlicenseNot gradedqualityDmaintenanceEnables serving and querying documentation with AI-powered capabilities including markdown file serving, keyword search, and intelligent Q\&A using OpenAI integration.MIT
- AlicenseAqualityCmaintenanceServes the already-public developer documentation for the DivineAPI REST API, enabling search, endpoint lookup, and example responses without authentication.5MIT