/v1 API as MCP tools. AI agents and LLM clients can use it to send messages, query conversations, manage numbers, templates, webhooks, groups, and voice calls — directly from the model context.
Hosted connector
The server speaks the streamable HTTP transport and runs as a hosted connector at:ps_* key in the x-api-key header:
Authentication
Use a number-scoped key for tools that operate on a specific number (messaging, conversations, groups); tenant-scoped keys are required for tenant tools such as
api_keys_list and numbers_list.
Self-hosted
The server is published as@pilot-status/mcp-server on npm and can be run locally:
ps_* API key via the x-api-key header (HTTP mode) or environment configuration, depending on your MCP client.
Available tools (65)
Notes:
templates_create/templates_updaterequire theexamplesobject (one real sample per variable; missing →400 TEMPLATE_EXAMPLES_REQUIRED) and accept media headers by URL only — base64 is REST-only.messages_sendsupports the three send modes:templateId,text, or direct media (media+mediaType; audio is delivered as a voice note).- Inbound media: on META numbers feed
media.idtomedia_get; on unofficial (Pilot Status web) numbers usemedia.urldirectly. - Token-based routes (remote-pairing public endpoints, embed session minting) are excluded from the tool list because they use a different auth flow.
Example tool call
Common errors
401— missing or invalid API key.403— tenant-scoped key on a number-scoped tool (or vice versa), or a tool outside a per-number grant.400— invalid tool arguments (validated against the underlying API schema).