Developers · Pamphlet Editorial · Updated 2026-08-04
MCP and API for custom agent workflows
REST API v1 and the Pamphlet MCP server let developers connect external agents to Pam Pod data and actions.
Outbound teams increasingly build custom agent runtimes. Those runtimes need the same CRM, campaign, and inbox context operators see in the UI.
Pamphlet exposes REST API v1 with OpenAPI documentation and scoped bearer keys per Pam Pod. The TypeScript SDK covers common integration patterns for internal tools.
The MCP server connects MCP-compatible clients to Pam Pod tools with PAMPHLET_API_KEY and PAMPHLET_POD_ID. Developers run it locally or in their agent host alongside Pam Agent inside the workspace. Both paths keep automation auditable instead of siloed in a script on someone's laptop.