Everything the server exposes, grouped by the job it belongs to. 22 are read-only and 30 need a write key. Nothing here is aspirational — if it is on this page, the server answers it today.
| Tool | Needs | What it does |
|---|---|---|
list_bots | read | Every bot across every workspace you administer, with the workspace it belongs to. |
get_bot | read | One bot in full — instructions, model, settings. |
update_bot_instructions | write | Rewrite what the bot is told to do. Snapshotted, so you can roll back. |
update_bot_settings | write | Model, office hours, handoff, automations. |
test_bot | write | Ask the bot a question and read the answer, without touching a real conversation. |
get_overview | read | Conversation counts by stage, per bot, across every workspace. |
| Tool | Needs | What it does |
|---|---|---|
list_conversations | read | The shared inbox. Filter by bot, stage or channel. |
get_conversation | read | Every message in order, plus the lead details captured on the thread. |
send_reply | write | Reply as a human. Never metered and never counted against your plan. |
take_over | write | Stop the AI on a thread so a person can answer. |
hand_to_ai | write | Give the thread back; the AI resumes answering. |
set_conversation_status | write | Move a thread between open, pending and closed. |
list_signups | read | Captured leads — anyone who gave a name, email or phone to a bot. |
get_signup | read | One lead in full. |
update_signup | write | Edit a lead record or add a note. |
get_pipeline | read | Your sales board — who is at which stage, what the open pipeline is worth, and whether the bot or a person moved them. |
list_opportunities | read | Leads the AI let slip, found twice a day: why, what they said, what to do and a message ready to send. |
update_opportunity | write | Mark a missed opportunity done or not worth it once the team has replied, called or made an offer. |
scan_opportunities | write | Read the latest chats for missed opportunities right now instead of waiting for the next scheduled scan. |
move_contact | write | Move someone to another stage or set what their deal is worth. Unlike the bot, you can move people backwards and close them. |
list_tags | read | Your tags, how many people carry each, and which ones keep the AI quiet. |
tag_contact | write | Tag the person in a chat, e.g. Client, or take the tag off. A tag can keep the AI quiet for them: no replies, no follow-ups. |
| Tool | Needs | What it does |
|---|---|---|
list_knowledge | read | Everything a bot has been taught, by source. |
add_knowledge | write | Teach the bot a new fact, policy or document. |
delete_knowledge | write | Remove one chunk by id — the fix for an answer that went stale. |
list_knowledge_chunks | read | The retrievable pieces, so you can find the one that is wrong. |
add_website | write | Crawl a URL and turn its pages into citable knowledge. |
resync_website | write | Re-crawl after you have changed the site. |
list_help_articles | read | Published help centre articles. |
upsert_help_article | write | Write an article. It serves readers for SEO and teaches the bot at the same time. |
reorder_help_articles | write | Pull the articles that matter to the top. |
list_files | read | The PDFs and voice notes the AI can send, and how often each went out. |
add_file | write | Add a course PDF, price sheet or voice note from a link, and say when to send it. |
update_file | write | Change which course a file is for, when it goes out, or pause it. |
delete_file | write | Remove a file so the AI stops sending it. |
set_file_library | write | Let the AI send files by itself, or stop it. |
| Tool | Needs | What it does |
|---|---|---|
get_bot_costs | read | Spend per bot, with cost per reply and the model breakdown. |
get_credit_balance | read | Credits and AI replies left this month, per workspace. |
get_ad_results | read | Chats, leads, sales and spend per Click-to-WhatsApp ad, with the cost of each. |
get_meta_conversions | read | Whether sales from ads reach Meta, and which ad conversations were reported as a Purchase. |
set_meta_purchase_stage | write | Mark a pipeline stage as a sale, so ad leads who reach it are sent to Meta as a Purchase. |
set_meta_tracking | write | Connect a WhatsApp number to the Meta dataset, so ad leads and sales are reported to Meta. |
list_feedback | read | Bug reports your team has sent from inside the console — what broke, who hit it, and which are still open. |
| Tool | Needs | What it does |
|---|---|---|
list_channels | read | Which channels a bot answers on — widget, WhatsApp, Messenger, email. |
create_channel | write | Add a web chat widget to a bot and get the script tag to paste on the site. |
sync_catalog | write | Pull the live Shopify or WooCommerce catalogue so answers use real prices. |
update_widget | write | Colours, launcher, position, starter questions, and which domains may embed the widget. |
list_templates | read | WhatsApp templates and where each stands with Meta — only approved ones can be broadcast. |
submit_template | write | Send a WhatsApp template to Meta for approval, so you can message people outside the 24-hour window. |
send_order_update | write | Tell a customer their order was placed, paid, shipped or delivered — on WhatsApp, from any system that can call a tool. |
edit_template | write | Change the wording of a WhatsApp template, keeping its name, and send it back to Meta for review. |
get_whatsapp_health | read | Check a WhatsApp number with Meta — token, payment method, registration, quality and limits. Start here when sends fail. |
https://platform.tendabot.com/api/mcp/YOUR_KEYCreate a key under Settings → Claude & API access. A read-only key refuses every write tool by name, so you can hand one over without thinking about it. How the connection works.