Skip to content

MCP Tools and Profiles

Jump to bottom
Svwergio_mel edited this page Nov 11, 2026 · 2 revisions

MCP tools and profiles

Server endpoint: http://127.0.0.1:8765/mcp (Streamable HTTP). Auth: Authorization: Bearer cem_….

Tool surface

Browsers: browsers_list, browsers_bind, browsers_status

Platforms: platforms_list, platforms_capabilities

Chats: chats_list, chats_get, chats_export, chats_create, chats_send, chats_delete (delete needs confirm: true + gates)

Jobs (async lanes): jobs_enqueue, jobs_status, jobs_list, jobs_cancel — use for long ask/export/delete instead of blocking the UI thread.

Ask: chat_ask (provider-specific prompt in a bound browser tab).

Cache (SQLite, local): chat_cache_sync, chat_cache_read, chat_cache_append, chat_cache_update_block, chat_cache_delete — mirror long threads for agents without re-scraping the host on every turn.

Projects (where supported): projects_list, projects_create, projects_move_chat, projects_delete, etc. — gated by allowProjects on the browser.

Profiles: full vs small

When starting MCP you can limit exposed tools (dashboard/server config):

Profile Typical use
full Cursor / local agents: chats, jobs, cache, projects
small Read-mostly automation: list/get/export, browsers, platforms

Exact tool lists follow server registerTools — check platforms_capabilities and server README for the current set.

Cursor and mcpo

Cursor / VS Code: add HTTP MCP in .cursor/mcp.json (or user-level MCP settings):

{
  "mcpServers": {
    "chat-export": {
      "url": "http://127.0.0.1:8765/mcp",
      "headers": { "Authorization": "Bearer cem_YOUR_KEY_HERE" }
    }
  }
}

Create keys with chat-export-server key new (prefix cek_ or cem_). The server stores only hashes in ~/.chat-export/keys.json.

mcpo (Open WebUI and similar): if your stack exposes MCP through an OpenAPI proxy (e.g. mcpo on another localhost port), point that proxy at the same http://127.0.0.1:8765/mcp URL and forward the Authorization header. Cursor can use HTTP directly without mcpo.

Checklist: server running → MCP key in client → extension bridge on with ceb_ → logged-in provider tab → browsers_bind → tools.

chat_ask and request_id

  • Prefer chat_ask for a single Q&A in the live UI.
  • For multi-step or slow hosts, use jobs_enqueue { "kind": "ask", … } and poll jobs_status.
  • RPC and some MCP responses include request_id for correlating server logs and audit entries.

Cache workflow

  1. chat_cache_sync — pull latest messages for a chatId into the local DB.
  2. chat_cache_read — read blocks (outline or full text).
  3. chat_cache_append / chat_cache_update_block — agent writes without touching the provider until you send via chats_send.

Cache stays on disk under the server home directory; not sent to third parties.

Clone this wiki locally