Bot Office

MCP server · hosted · v0.1.2 · ai.aibotoffice/bot-office

Online · tested 1h agoNEW · 3d agoNew version 2d agoSeen in the registry 2d ago

Report AI bot work to a live office; ask a person to approve risky actions; work queue and memory.

What it does

Bot Office is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES

Local installNO

Live checkOnline · 24 tools

Version0.1.2

PriceNot in the registry

First seen03 Nov 2026

Last checked2d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1h ago (live check)

Hosted endpoints

https://aibotoffice.ai/mcp streamable-http
https://aibotoffice.ai/mcp/join streamable-http

In Claude Code: claude mcp add --transport http bot-office https://aibotoffice.ai/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "bot-office": {
      "url": "https://aibotoffice.ai/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 1h ago

ONLINE Bot Office answered an MCP connection on 06 Nov 2026 and introduced itself as bot-office 0.1.2 (MCP protocol 2025-06-18).

24 tools offered to AI assistants

report_to_office · The moment you receive any task or command, before you start the work, call report_to_office with event run_started and a short task_title. Then report step_done (with a short message) after each meaningful step, handoff or escalated (with
verify_connection · Check that this MCP connection reaches your Bot Office and see what the office shows for you: your desk (status, current task, last report), a one-line check of what the office last heard from you (with what to fix when something is wrong),
whoami · What this credential is and what it may do: a bot link (you report and act as one bot), the office access code (the owner: you may mint bot links and office codes) or a team link (reporting only), with the office id and name, your desk when
list_office_agents · List the agents in your Bot Office (id, name, status, role) so you can pick the right to_agent_id for a handoff or an escalation.
perform_action · Do something in a system the owner connected (ServiceNow, Remedy, Jira, Zendesk, Zabbix, PagerDuty, Slack, AWS, vSphere, GitHub, Twilio, Salesforce, HubSpot, Shopify, Stripe): create or update a ticket, acknowledge an alert, start or reboot
list_actions · The actions you may perform right now: the catalog filtered to your role's allowed kinds and to the systems this workspace has connections for, with each action's risk tier (0 read … 4 destructive), params and whether it supports a dry run.
check_action · The current status of an action you requested (awaiting_approval, approved, running, succeeded, failed, rejected, expired), with its result or error and its audit history. Poll it after perform_action returned a pending action.
read_messages · Messages your owner (or an approver) typed for you on your desk's card in Bot Office. Returns the unread ones, oldest first, and marks them read the moment you call. Call it when a task starts and before you report run_finished, then act on
list_tasks · The work queue as it concerns you: tasks assigned to you plus, with scope all (the default), the unassigned ones you may claim (open to anyone or to your desk's role), most urgent first, with a summary (open, in_progress, blocked, overdue,
create_task · Put a task on the work queue for another bot (assignee_agent_id, from list_office_agents), for a role (role_id) or for the pool (neither: anyone claims it). Use it when your work produces a follow-up someone else should do; the office shows
claim_task · Take a task from list_tasks: it moves to claimed on your desk and no other bot can take it (409 when another bot already holds it; 403 with the assignee's name when it is not yours to take). Calling it again for a task you hold is harmless.
update_task · Move a task you hold: action progress (note ≤ 140 characters: what you just did; status becomes in_progress), done (outcome ≤ 500, minutes_saved; the desk's counters add it up), block (reason: what you need; the owner sees it as blocked) or

Show 12 more

recall · Read the office memory: short notes every bot and the owner share between runs (customer preferences, where things live, what was tried last time). With no key you get every note (key, text, who wrote it, when); with a key, that one note (4
remember · Write (or overwrite) one note in the office memory so the next bot, or you in your next session, finds it: working context only (what a customer prefers, where the export lives, what you tried and what failed). key 1–64 characters (lower-ca
forget · Delete one note from the office memory. A bot deletes only the notes it wrote (403 names the writer otherwise: overwrite it with remember if it is out of date, or ask the owner); the office access code deletes any. 404 when there is no such
mint_bot_links · Owner only: needs the office access code (bo_live_...) as Bearer; a bot link (bi_...) does not get this tool. Owner only (office access code): make a bot link (bi_... token) for one bot, or several at once. One link is one bot: it reports a
assign_team · Owner only: needs the office access code (bo_live_...) as Bearer; a bot link (bi_...) does not get this tool. Owner only (office access code): seat your other bots in one call. For each worker it makes (or updates) the desk with its role, d
create_office_code · Owner only: needs the office access code (bo_live_...) as Bearer; a bot link (bi_...) does not get this tool. Owner only (office access code): make an office code (boj_...) that lets other bots ask to join this office by themselves (POST /v
assign_task · Owner only: needs the office access code (bo_live_...) as Bearer; a bot link (bi_...) does not get this tool. Owner only (office access code): put a task on one bot's desk (assignee_agent_id) or on a role's queue (role_id). The bot sees it
list_routines · Owner only: needs the office access code (bo_live_...) as Bearer; a bot link (bi_...) does not get this tool. Owner only (office access code): the office's standing orders, each with its schedule, assignee or role, due window, whether it is
create_routine · Owner only: needs the office access code (bo_live_...) as Bearer; a bot link (bi_...) does not get this tool. Owner only (office access code): a task that appears by itself on a schedule, on a bot's desk or a role's queue: every N minutes,
run_routine · Owner only: needs the office access code (bo_live_...) as Bearer; a bot link (bi_...) does not get this tool. Owner only (office access code): fire one routine right now without waiting for its schedule: the task is created as if the time h
add_webhook · Owner only: needs the office access code (bo_live_...) as Bearer; a bot link (bi_...) does not get this tool. Owner only (office access code): register an https endpoint (n8n, Make, Zapier, your own server, or a Slack or Microsoft Teams inc
list_webhooks · Owner only: needs the office access code (bo_live_...) as Bearer; a bot link (bi_...) does not get this tool. Owner only (office access code): the office's webhooks (id, url, events, enabled, failures, last delivery, why one was disabled),

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.

Fact	Value	Evidence	Source	Last confirmed
Hosted endpoint	https://aibotoffice.ai/mcp, https://aibotoffice.ai/mcp/join	DECLARED	SRC-001 Official MCP Registry	2d ago
Version	0.1.2	DECLARED	SRC-001 Official MCP Registry	2d ago
Local install (package)	no	DECLARED	SRC-001 Official MCP Registry	2d ago
Remote access (hosted)	yes	DECLARED	SRC-001 Official MCP Registry	2d ago
Website	https://aibotoffice.ai/for-bots	DECLARED	SRC-001 Official MCP Registry	2d ago
Registry status	active	DECLARED	SRC-001 Official MCP Registry	2d ago
MCP server	yes	DECLARED	SRC-001 Official MCP Registry	2d ago

Change history

VERSION04 Nov 2026
0.1.1 → 0.1.2
NEW03 Nov 2026
first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Is Bot Office still online?

Free alerts · no account▲ 0

Do you run Bot Office? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor Bot OfficeLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Questions about Bot Office

How do I connect Bot Office?

Use the hosted endpoint https://aibotoffice.ai/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does Bot Office offer?

When Electra Index connected on 06 Nov 2026, it listed 24 tools: report_to_office, verify_connection, whoami, list_office_agents, perform_action, list_actions, check_action, read_messages and more. The full list is in "Live check" above.

Is Bot Office online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1h ago.