BotMape
BotMape provides APIs for creating and managing AI agents, knowledge bases, conversations, messages, and usage analytics.
Verdict
Common use cases
- Prototype chatbot responses before launch
- Bulk-load FAQ content into agent knowledge
- Test visitor conversation flows in staging
- Pull weekly analytics for support chatbots
- Update agent prompts across multiple sites
Integration
- Vendor
- BotMape
- Category
- communication
- Auth
- API_KEY
- Tools
- 8
- Composio slug
botmape
Tools
- Add Knowledge
Add and automatically embed training content in one AI agent's knowledge base, optionally with source or categorization metadata.
- Create AI Agent (No API Delete)destructive
Permanently create a BotMape AI agent. BotMape provides no documented delete-agent API, so this toolkit cannot remove it afterward, and creation may permanently consume a plan-limited agent slot. Requires explicit confirmation that a lastin
- Delete Knowledge Entrydestructive
Permanently delete one knowledge-base entry from an AI agent using both the agent ID and knowledge entry ID.
- Get AI Agent
Return the detailed configuration, behavior prompt, appearance, and active state of one AI agent by ID.
- Get Platform Analytics
Return account-wide BotMape message and conversation totals, daily activity, averages, and per-agent statistics.
- List AI Agents
Return all AI agents owned by the connected BotMape account, including the IDs needed by single-agent, chat, and knowledge tools.
- List Knowledge Entries
Return all knowledge-base entries currently attached to one AI agent, including entry IDs needed for deletion.
- Send Message to AI Agent
Immediately send a visitor message to an AI agent, creating a conversation or continuing the supplied conversation, and return the generated reply. This permanently adds chat history.
Setup
Setup guide
- 11. Click 'Add Integration' in your Switchy workspace settings and select BotMape. 2. Log into your BotMape account at botmape.com and navigate to Settings → API Keys. 3. Generate a new API key and copy it to your clipboard. 4. Paste the key into Switchy's connection dialog and click 'Connect'. 5. Open any Project and type '@BotMape list agents' to confirm the connection works—you'll see your existing agents. 6. To test a tool, try '@BotMape create an agent named Support Bot with the prompt: Answer questions about our return policy.' 7. Remember that created agents are permanent; BotMape provides no delete endpoint, so plan your agent slots carefully.
What teammates see: by default, memories from BotMape 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
Create Support Agent
@BotMape create an AI agent named 'Support Assistant' with the behavior prompt: You help customers with shipping timelines, return policies, and order tracking.
Load Knowledge Base
@BotMape add knowledge to agent ID abc123: Our return window is 30 days. Customers must include the original receipt. Refunds process within 5 business days.
Test Conversation Flow
@BotMape send this message to agent ID abc123: 'I ordered last week and haven't received a tracking number yet. What should I do?'
Review Agent Config
@BotMape get the details for agent ID abc123 including its behavior prompt and active status.
Pull Usage Analytics
@BotMape get platform analytics showing total conversations, daily message volume, and per-agent breakdowns for the past month.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@BotMape list all AI agents in our account and show me which ones have been active in the last 7 days
Found 4 AI agents in your BotMape account: 1. **Support Bot** (ID: agt_8x9k2) – Active, last message 2 hours ago 2. **Sales Assistant** (ID: agt_3m7p1) – Active, last message yesterday 3. **Onboarding Guide** (ID: agt_5n2q8) – Inactive, last message 14 days ago 4. **FAQ Bot** (ID: agt_1k4r6) – Active, last message 3 days ago Three agents have handled conversations in the past week. The Onboarding Guide appears dormant and may need knowledge-base updates or reactivation.
This example uses the List AI Agents tool to audit your chatbot fleet. Requires a valid BotMape API key with read access. Useful for identifying underutilized agents or confirming deployment status before making configuration changes.
@BotMape add this product documentation to the Support Bot's knowledge base: [paste 500-word help article]. Tag it as 'product-docs' and cite the source as our internal wiki.
Successfully added 1 knowledge entry to Support Bot (agt_8x9k2): - **Content**: 487 words embedded and indexed - **Metadata**: category='product-docs', source='internal wiki' - **Entry ID**: kb_7t3w9 The agent will now reference this article when answering visitor questions about product features. BotMape's embedding process typically completes within 60 seconds; the bot may return generic answers until indexing finishes.
Demonstrates the Add Knowledge tool, which permanently writes to an agent's training corpus. The MCP cannot verify embedding completion—test the agent afterward to confirm retrieval quality. Large uploads may hit BotMape's per-request size limits; chunk long documents into multiple calls if needed.
@BotMape pull last 30 days of platform analytics and identify which agent has the highest average messages per conversation
**BotMape Account Analytics (Last 30 Days)** Total conversations: 1,847 | Total messages: 9,203 | Avg messages/conversation: 4.98 **Per-Agent Breakdown**: 1. Sales Assistant – 6.2 avg msgs/conv (longest interactions, likely complex inquiries) 2. Support Bot – 4.1 avg msgs/conv 3. FAQ Bot – 2.8 avg msgs/conv (quick resolutions) 4. Onboarding Guide – 3.5 avg msgs/conv Sales Assistant drives the deepest engagement, suggesting visitors need more back-and-forth to reach purchase decisions. Consider expanding its knowledge base or adjusting its prompt to surface pricing/demos earlier.
Uses the Get Platform Analytics tool to surface usage patterns across your agent fleet. This read-only call requires API key access but won't modify any configuration. Helpful for quarterly reviews or identifying which bots justify knowledge-base investment. BotMape's analytics API returns account-wide totals; agent-level breakdowns depend on your plan tier.
Use-case deep-dives
When BotMape fits your tier-one support triage workflow
A 10-person SaaS team runs first-line support through a BotMape agent that answers billing and onboarding questions before escalating to Slack. The team uses Switchy to add knowledge entries when a new FAQ surfaces, test the agent's reply with Send Message, and pull analytics to see which questions still leak through. BotMape works here because the knowledge base stays under 200 entries, the team updates it weekly not hourly, and the agent creation limit (no delete API) isn't a problem when you only need two agents. If your support load exceeds 500 conversations a day or you prototype agents frequently, the missing delete endpoint becomes a planning tax. For stable, low-churn support bots at small scale, BotMape and Switchy close the loop between ticket patterns and agent training in one workspace.
BotMape handles lead capture when your CRM can't
A three-person agency uses a BotMape agent on their landing page to ask budget, timeline, and project-type questions before booking a call. The founder checks Get Platform Analytics in Switchy each Monday to see conversation volume and uses List Knowledge Entries to audit what the bot knows about their service tiers. This scenario works because the agent's job is narrow (qualify, not close), the knowledge base is static (six service packages), and the team doesn't need to spin up test agents every sprint. BotMape's API key auth and eight-tool scope mean setup takes one Switchy session. If your sales process changes monthly or you A/B test bot personalities, the no-delete constraint and manual knowledge management become friction. For agencies with a fixed offer and predictable inbound flow, BotMape gives you a working qualification layer without Intercom's price tag.
When BotMape becomes your async HR reference desk
A 15-person remote startup points employees to a BotMape agent that answers PTO, expense, and benefits questions pulled from their handbook. The ops lead uses Switchy to bulk-add knowledge entries when policies update and sends test messages to confirm the agent surfaces the right sections. BotMape fits because the knowledge base is append-only (policies don't vanish, they version), employees ask the same 20 questions, and the team doesn't need agent proliferation (one HR bot, one IT bot). The missing delete API doesn't hurt when you're not prototyping. If your handbook changes weekly or you need the bot to trigger Slack workflows, BotMape's toolset is too thin and you'll want a platform with webhooks. For stable internal reference at small-team scale, BotMape and Switchy let your ops person own the bot without engineering help.
Frequently asked
What does the BotMape MCP let me do in Switchy?
It lets your team create and manage BotMape AI chatbots directly from Switchy workflows. You can add training content to knowledge bases, send test messages to agents, pull analytics, and list all your bots. The MCP wraps BotMape's API so you don't need to leave Switchy to configure or query your customer-facing agents.
Do I need a specific BotMape plan to use this MCP?
You need a BotMape account with API access and an API key. The Create AI Agent tool warns that BotMape has no delete endpoint, so new agents may permanently consume a slot on your plan. Check your BotMape tier's agent limit before creating bots through Switchy to avoid hitting quota.
Can the MCP delete AI agents I create by mistake?
No. BotMape's API does not expose an agent-deletion endpoint, so the MCP cannot remove agents once created. You'll need to log into BotMape's dashboard to delete unwanted bots manually. The MCP can delete individual knowledge entries, but not entire agents.
How is this different from just using BotMape's dashboard?
The MCP lets you script agent updates and knowledge uploads inside Switchy workflows, which is faster than clicking through BotMape's UI for repetitive tasks. You can also pull analytics and send test messages without switching tabs. For one-off agent setup, the dashboard is simpler.
Who on my team should connect the BotMape API key?
Whoever owns your BotMape account or has the API key. The key grants full read-write access to all agents and knowledge bases, so treat it like an admin credential. Once connected in Switchy, any teammate with workspace access can invoke the tools.