Banjo MCP Server

Banjo is an MCP integration. Self-hosted AI assistant that places real phone calls for you: bookings, reservations, errands.

Packages and local setup

The published oci package is ghcr.io/shatch/banjo:0.1.8. Its declared MCP transport is streamable-http.

The package declares DATABASE_URL (required): Postgres connection URL. Migrations run on boot.; MCP_API_KEY (required): Bearer token MCP clients must send (at least 32 characters, e.g. openssl rand -hex 32).; ASSISTANT_PRINCIPAL_NAME (required): The name of the person Banjo calls on behalf of.; PUBLIC_HOSTNAME (required): Public hostname Twilio reaches this server on (no scheme), e.g. a tunnel or reverse proxy.; VOICE_AI_PROVIDER (required): Voice AI vendor. openai is the one carrying live traffic.; OPENAI_API_KEY: OpenAI API key, for VOICE_AI_PROVIDER=openai or openai-live.; TWILIO_ACCOUNT_SID (required): Twilio account SID.; TWILIO_AUTH_TOKEN (required): Twilio auth token.; TWILIO_PHONE_NUMBER (required): The Twilio number Banjo calls from, in E.164 (+15551234567).; NOTIFICATION_CHANNEL: How Banjo tells you a call's outcome. twilio_sms also needs NOTIFY_TO_PHONE_NUMBER and NOTIFY_FROM_PHONE_NUMBER; pushover needs PUSHOVER_APP_TOKEN and PUSHOVER_USER_KEY..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.8 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related communication MCP servers for tools that cover the same kind of work.