Kapso
Kapso provides APIs for WhatsApp messaging, customer and contact management, broadcasts, workflows, and serverless functions.
Verdict
Common use cases
- Triage unassigned WhatsApp conversations at shift start
- Audit customer records before outreach campaigns
- Check workflow health after deployment
- Review message threads for compliance audits
- Verify function runtime config before rollback
Integration
- Vendor
- Kapso
- Category
- communication
- Auth
- API_KEY
- Tools
- 10
- Composio slug
kapso
Tools
- Get Function
Retrieve one Kapso serverless function's code, runtime configuration, deployment status, and computed URLs without invoking or changing it.
- Get Phone Number
Retrieve one Kapso WhatsApp phone-number configuration by its Meta phone number ID.
- Get Phone Number Health
Run Kapso's live checks for one WhatsApp phone-number configuration and return its body-level health status and individual check results.
- Get Workflow
Retrieve one workflow's metadata, full graph definition, or available variables without executing or changing it.
- List Conversations
List one page of WhatsApp conversations by recent activity, with filters for phone number, status, assignment, and activity time range.
- List Customers
List Kapso project customers and filter them by name, external customer ID, or creation time. Returns one page and a continuation cursor.
- List Functions
List serverless functions configured in the Kapso project, including runtime and deployment state, without returning function source code or invoking any function.
- List Messages
List one page of WhatsApp message history project-wide through Kapso Platform or for one phone number through the Meta-compatible proxy. This tool only reads history and never sends messages.
- List Phone Numbers
List WhatsApp phone-number configurations in the Kapso project, with filters for account, customer, messaging state, and display name.
- List Workflows
List project workflows and filter them by lifecycle status, name, or creation time. This read-only action does not execute a workflow.
Setup
Setup guide
- 11. In Switchy, open Settings → Integrations and click Add MCP Server. 2. Select Kapso from the catalog. 3. Log in to your Kapso dashboard, navigate to API Keys, and generate a new key with read permissions for conversations, customers, functions, and workflows. 4. Paste the key into Switchy's API Key field and click Connect. 5. Switchy will validate the key and list available tools. 6. Open any Project, type '@Kapso list recent conversations' in the chat, and confirm you see conversation data. 7. If the response is empty, verify the key has the correct scopes in Kapso's dashboard.
What teammates see: by default, memories from Kapso are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Unassigned Conversation Summary
@Kapso list conversations with status unassigned from the last 24 hours. Summarize each by customer name and last message, then rank by urgency.
Customer Lookup by Name
@Kapso search customers with name containing 'Garcia'. For each match, show external ID, creation date, and recent conversation count.
Phone Number Health Check
@Kapso check health for phone number ID 123456789. List each diagnostic check and flag any failures with recommended fixes.
Function Deployment Audit
@Kapso list all functions. For each, show runtime, deployment status, and last updated timestamp. Flag any that aren't fully deployed.
Message History Export
@Kapso get message history for phone number 987654321, last 50 messages. Format as a timestamped log with sender, recipient, and message body.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Kapso list all active WhatsApp conversations assigned to me from the last 48 hours, grouped by customer
Kapso returned 14 active conversations from the past 48 hours. Seven are assigned to you: three from Acme Corp (order questions), two from Beta Industries (support escalations), one from Gamma LLC (onboarding), and one from Delta Partners (billing inquiry). The remaining seven are assigned to teammates. Each conversation includes the customer name, last message timestamp, and current status. This is an illustrative summary; actual results depend on your project's conversation volume and assignment rules.
This example shows Kapso's conversation-filtering and assignment capabilities. The MCP requires a valid API key with read access to conversations. Results are paginated; if you have hundreds of conversations, you'll receive a continuation cursor to fetch the next page. The grouping logic here is performed by the AI, not the MCP itself.
@Kapso check the health status of our main customer-support WhatsApp number and tell me if any checks are failing
Kapso's health check for phone number +1-555-0199 (Meta ID: 123456789) shows overall status: healthy. All six checks passed: webhook reachability (200 OK, 89ms), message template quota (47 of 250 used), rate limit headroom (12% of hourly cap), Meta API connectivity (verified), certificate validity (expires in 203 days), and function deployment status (all handlers live). This is an illustrative response; your actual check results will reflect your number's real-time state and Meta account limits.
This example demonstrates Kapso's proactive monitoring tool for WhatsApp infrastructure. The health check runs live against Meta's API and your webhook endpoints, so it may take 2–4 seconds to return. If any check fails, the output will include diagnostic details (error codes, latency spikes, quota thresholds). Requires API key with phone-number read scope.
@Kapso retrieve the 'order-confirmation' workflow definition and summarize what triggers it and what actions it takes
Kapso returned the full graph definition for workflow 'order-confirmation' (ID: wf_abc123). The AI summarizes: This workflow triggers when a customer sends a message containing 'order confirmed' or a payment webhook fires. It executes four steps: (1) fetch order details from your CRM via the 'get-order' function, (2) send a WhatsApp template message with order summary and tracking link, (3) log the interaction to your analytics function, (4) update the conversation status to 'fulfilled'. The workflow uses three variables: customer_id, order_id, and tracking_url. This is an illustrative breakdown; the actual graph JSON contains node IDs, edge conditions, and retry policies.
This example pairs Kapso's workflow-retrieval tool with the AI's reasoning to explain automation logic in plain language. The MCP returns the raw workflow graph (nodes, edges, variables); the AI interprets it. Useful for onboarding teammates or auditing complex workflows. Requires API key with workflow read access. The MCP does not execute the workflow—it only fetches the definition.
Use-case deep-dives
When Kapso wins for support teams routing WhatsApp at scale
A 6-person support team fields 200+ WhatsApp conversations daily across three product lines. Kapso's List Conversations and List Messages tools let the team pull recent threads into Switchy, filter by assignment or status, and draft replies in shared context before pushing them back through the platform. The Get Phone Number Health check surfaces delivery issues before customers complain. This works when your volume justifies dedicated WhatsApp infrastructure and you already run Kapso workflows—if you're below 50 conversations a week or using a different messaging backend, the 10-tool surface is overkill. For teams that live in WhatsApp support queues and need shared AI visibility into thread history and routing state, Kapso in Switchy closes the loop between triage and response.
When this MCP helps dev teams troubleshoot Kapso deployments
A 3-engineer team deploys customer-facing automations as Kapso serverless functions and hits a deployment failure during a product launch. The Get Function and List Functions tools pull runtime config, deployment status, and computed URLs into Switchy so the team can compare the broken function against working ones without switching tabs. Because Kapso functions tie directly to WhatsApp workflows, the Get Workflow tool shows the full graph that triggered the failure. This scenario assumes you're already building on Kapso's serverless layer—if your functions live in AWS Lambda or Vercel, this MCP adds no value. For small teams running Kapso as their automation backbone, having function state and workflow definitions in the shared AI workspace cuts mean-time-to-fix in half.
When Kapso's customer tools speed up live prospect research
A 4-person sales team takes inbound calls from prospects who've already messaged the company's WhatsApp line. The List Customers tool filters by external ID or name and surfaces the full conversation history through List Messages, so the rep can reference prior questions without asking the prospect to repeat themselves. Get Conversation pulls thread metadata and assignment state if the prospect was already routed to support. This only makes sense if your sales motion starts in WhatsApp and you store customer records in Kapso—if leads come through HubSpot or Salesforce, you need a different MCP. For teams where WhatsApp is the first touchpoint and Kapso holds the customer graph, pulling that context into Switchy during live calls turns cold outreach into warm follow-up.
Frequently asked
What does the Kapso MCP let me do in Switchy?
It reads WhatsApp conversation history, customer records, and serverless function configs from your Kapso project. You can list messages, check phone-number health, retrieve workflow definitions, and inspect function deployment status. It does not send messages or trigger workflows—it's read-only visibility into your Kapso setup.
Do I need admin access to connect Kapso MCP?
You need a Kapso API key with read permissions for conversations, customers, functions, and workflows. Kapso doesn't publish granular scope documentation, so confirm your key can call their Platform API endpoints. If your key is scoped to only send messages, the MCP won't work.
Can the Kapso MCP send WhatsApp messages or run workflows?
No. It only reads data—message history, conversation threads, customer lists, function code, workflow graphs. To send messages or execute workflows, use Kapso's web dashboard or their direct API. The MCP is for pulling context into Switchy, not for triggering outbound actions.
Why use this instead of logging into Kapso's dashboard?
The MCP surfaces conversation context and customer data inside Switchy's AI workspace, so your team can reference WhatsApp threads or function configs without tab-switching. If you only need to send messages or deploy functions, the dashboard is faster. Use the MCP when you want conversation history in your AI prompts.
Who on my team should connect the Kapso MCP?
Whoever manages your Kapso project and holds an API key. That's usually a developer or ops lead. Once connected in Switchy, any workspace member can query the data through AI—they don't need their own Kapso login. The MCP doesn't count against Kapso's message or function quotas.