Botsify API (MCP)

Use the Botsify APIs MCP (botsify-api-mcp), not raw HTTP, unless the user asked for curl.

Do not invent JWT/API keys. Auth is POST /v1/login (tool login-account). The server stores the Bearer token. After login, last_selected_bot is the default apikey / bot_key. Switch with select-bot.

Default base URL: https://botsify.com/api. Config: email, password, optional baseUrl. Env: BOTSIFY_EMAIL, BOTSIFY_PASSWORD, BOTSIFY_API_BASE_URL.

OpenAPI for these tools: openapi.json in the MCP package. Public Postman: https://documenter.getpostman.com/view/9852076/2sBY4WoH2X

Session order

1. login-account (omit email/password if Smithery/env already set them).
2. list-workspace-agents (or list-owned-bots).
3. select-bot with apikey from the list (or skip if last_selected_bot is already correct).
4. Call domain tools. Confirm bot_id vs bot API key — they are different.

Identifier	What it is	Typical tools
apikey / bot_key	Bot API key string	select-bot, activate-agent-version.bot_id, converse
numeric bot_id	Database id	rename-agent, delete-agent, clone-agent, save-agent-version, inbox

agent_type on create: chatbot | agent | voice.

Workflows

Create then configure

1. create-agent (bot_name, agent_type, optional marketplace template) — new bot_api_key is stored.
2. get-bot-details
3. save-agent-version with the full agent text and chat_flow JSON (not a fragment).
4. activate-agent-version or deploy-agent-version

Patch one instruction column

patch-instruction-section with field: agent | memory | soul | identity | user_info.

Builder

start-builder-chat → stream-builder (messages as {role, content} objects, optional stream_id) → store-builder-response with the stream response_id → next turn. Cancel: stop-builder-stream. Reset: clear-builder-conversation.

Talk to an end user

• Website/API user: send-converse-message or stream-user-message (fbId max 16 chars). Stop: stop-user-message-stream. History: get-converse-history.
• Inbox: send-inbox-message (numeric bot_id + fbId).
• Outbound channel: send-user-message (to = fbId or phone; optional type whatsapp | sms).
• Agentic query: query-mcp-agent.
• Legacy stories: get-query-response.

WhatsApp

create-whatsapp-template → list-whatsapp-templates → send-whatsapp-broadcast → get-whatsapp-broadcast-report.

Destructive

Confirm before delete-agent, delete-agent-versions (active versions cannot be deleted), clear-builder-conversation.

Tool map

Auth: login-account, create-oauth-token (client_id/client_secret from login).

Agents: create-agent, list-workspace-agents, get-bot-details, select-bot, rename-agent, delete-agent, clone-agent, list-owned-bots.

Versions: list-agent-versions, save-agent-version, patch-instruction-section, activate-agent-version, delete-agent-versions, deploy-agent-version.

Builder: stream-builder, store-builder-response, stop-builder-stream, start-builder-chat, clear-builder-conversation.

Messaging: send-user-message, stream-user-message, stop-user-message-stream, list-conversations, get-user-chat, send-inbox-message, send-converse-message, get-query-response, query-mcp-agent, get-converse-history, set-user-attribute, list-messenger-users, list-bot-messenger-users, change-user-activation.

Analytics: get-bot-dashboard-stats.

WhatsApp: send-whatsapp-broadcast, create-whatsapp-template, list-whatsapp-templates, get-whatsapp-broadcast-report.

Whitelabel: list-whitelabel-clients, create-whitelabel-client, create-whitelabel-package, list-whitelabel-packages.

If a tool is missing, read src/server.ts registerTool names — do not guess old Postman names (authorize, get_bots, use_bot).

Run the MCP

cd botsify-api-mcp
npm install && npm run build && npm start

Smithery: email + password required; baseUrl optional. HTTP: npm run start:http.