MCP server
The beem toolset inside any MCP agent client.
beem mcp serve is a stdio MCP server
that gives agent clients the whole beem workflow:
- Authoring quality — the
authoring_guidetool delivers the authoring knowledge base from the beem cloud to signed-in accounts with the local-agent capability. No prompt assets ship in any package; every client builds to the same baseline. - Local decks — create, check (a real build), preview and list decks.
Outside a beem project the tools work in a private workspace under
~/.beem/workspace, so "make me slides about X" works from anywhere. - Cloud — push, pull, publish, share and link-access tools, once you
have run
beem login. Signed out, the cloud tools answer with the exact sign-in instruction instead of erroring.
Register it with your clients
npx --package=@beem-slide/cli beem mcp installdetects the agent clients on your machine and writes the server into their configurations — idempotently, touching nothing but its own entry, and never putting a token in a client config:
| Client | Configuration it writes |
|---|---|
| Claude Code | ~/.claude.json (only the mcpServers key) |
| Claude Desktop | claude_desktop_config.json in the platform's config dir |
| Codex | its own [mcp_servers.beem-slide] section in ~/.codex/config.toml |
| Cursor | ~/.cursor/mcp.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| Gemini CLI | ~/.gemini/settings.json |
Restart the client afterwards. beem mcp status shows what is registered
where; beem mcp uninstall removes exactly what install wrote.
Any other client
Every MCP client accepts the same server definition. Print it with:
npx --package=@beem-slide/cli beem mcp config --jsonand paste it into the client's MCP settings (this is the path for Workbuddy, 千问办公, and anything else that speaks MCP).
The registered command is npx -y --package=@beem-slide/cli beem mcp serve.
Installs made by the install script point at their
managed ~/.beem/bin/beem shim instead — those machines have no system node
for a client to resolve npx with.