Skip to main content
MCP Tools

MCP tools

The Bureau tool catalogue served over MCP, grouped by family.

bureau serve exposes one MCP catalogue over Streamable HTTP at POST http://localhost:8830/mcp. Every tool is served by the same daemon; the GET /health response reports the live tool count. Tools are grouped into families below.

FamilyTools
Browser controlbrowser_navigate, browser_click, browser_fill, browser_evaluate, browser_screenshot, browser_get_dom, browser_cdp_send, browser_list_requests, browser_get_request_body, browser_act
Scrape & researchscrape, browser_export, research_run, research_status
Socialsocial_capture, social_search, social_action, social_conversation, social_media, social_network, social_feed, social_capture_start, social_capture_poll, social_capture_contract
Screenscreen_capture, screen_displays, screen_windows, screen_move, screen_click, screen_type, screen_key
Sessions & credentialsbureau_sessions, bureau_tabs, list_profile_accounts, session_sync_from_chrome, session_reauth, record_credential, list_credentials
Workflowsbureau_workflow_list, bureau_workflow_run

Conventions

  • Sessions. Read/act tools take an optional (or, for browser_act, required) session — a saved identity id from Sessions. Omit it for an anonymous control tab.
  • Gated writes. Outbound social verbs (social_action, social_network invite) are dry-run by default: call without confirmToken to preview, then echo the returned token back to execute. Screen actuation is rate-limited and gated.
  • Rate limiting. Every tool call passes a per-tool rate limiter; a throttled call returns a readable { throttled: true, retryAfterMs, limit } result rather than a transport error.

On this page