Feature
Developer API and MCP
Integrate Pamphlet through REST API v1, scoped API keys, webhooks, the TypeScript SDK, and an MCP server for agent tooling.
REST API v1
Each Pam Pod exposes a versioned REST API with OpenAPI documentation. Integrations can read and write CRM, campaign, and conversation data with scoped credentials.
MCP server for agents
The Pamphlet MCP server connects external agent frameworks to Pam Pod data and actions. Configure it with an API key and Pam Pod ID for local or hosted agent runtimes.
SDKs, keys, and webhooks
The TypeScript SDK wraps common API patterns. API keys are created in security settings with bearer authentication. Webhooks and connectors extend event-driven workflows.
Related
FAQ
Where is the OpenAPI spec?
OpenAPI documentation is available at /api/v1/openapi. Developer settings inside each Pam Pod show the base URL and authentication format.
How do I run the MCP server?
Install @pamphlet/mcp-server, set PAMPHLET_API_KEY and PAMPHLET_POD_ID, and connect your MCP-compatible client. Developer settings include the exact command for your Pam Pod.
Are API keys scoped per Pam Pod?
Yes. API keys authenticate against a specific Pam Pod so integrations respect workspace isolation and sending policy boundaries.
See this in your workspace
Book a demo to walk through this capability with your team.