MCP connections and tools
Connect an agent with OAuth or a token and use the 11 available tools.
Connect an agent
- Copy the MCP URL from Dashboard → API & Agents.
- Add it as a remote server/connector in your MCP client.
- If the client uses OAuth, sign into MonCha, review the workspace and requested permissions, then approve.
- If using a token, configure the bearer header through the client’s secure credential mechanism.
- Refresh the client’s tools and request list_bots.
- Confirm the returned bots belong to the intended workspace before asking the agent to change anything.
https://api.dev-moncha.com/mcp
Available tools
Tools are filtered by the connection/token’s scopes. There is no create_bot MCP tool. Regional reports, chat summaries, team, billing and full dashboard configuration are not regular MCP tools.
| Tool | Required scope | Purpose |
|---|---|---|
| list_bots | bots:read | List accessible bots. |
| list_knowledge | kb:read | List knowledge, optionally for chatbotId. |
| add_knowledge | kb:write | Queue a URL or text with a title. |
| ask_bot | chat:invoke | Ask a question using the bot’s knowledge. |
| list_conversations | conversations:read | Find recent conversations with optional q/chatbotId. |
| get_conversation | conversations:read | Read one sessionId transcript. |
| list_leads | leads:read | Read intent-scored leads. |
| get_analytics | analytics:read | Read aggregate 30-day metrics. |
| list_bookings | bookings:read | Read appointment requests. |
| get_booking | bookings:read | Read one bookingId. |
| update_booking | bookings:write | Confirm, reject, reschedule or cancel a booking. |
Example tasks
- “List my bots, then show the recent questions for the support bot.”
- “Read the last 30 days of aggregate analytics for this bot and summarize recurring unanswered questions.”
- “Show pending bookings. Ask me before confirming, rejecting or changing one.”
- “Add this approved FAQ text to the selected bot and report the queued result.”
Disconnect or recover
OAuth connections appear under MCP connections in API & Agents. Disconnect the relevant connection there to revoke access. Remove it from the client too if it should no longer be configured. Token-based connections are revoked by revoking their API token.
- No tools: check scope, plan/live access and whether the client completed authentication.
- Wrong bots: inspect the authorized workspace and token allowlist.
- Expired/revoked credentials: reconnect or replace the token as appropriate.
- Payment suspension: restore service access before repeating login attempts.