Beck
bot.beckPublished by beck.botv1.6.1Updated Oct 24, 2026
Project management for coding agents: record the approved plan, work the tasks, ask, hand off.
Overview
Beck is a local MCP server that gives coding agents a project-management workspace to record an approved plan, work through tasks, ask questions and hand off.
- What you can do
- Connect an assistant to a Beck workspace for project management aimed at coding agents, as described in the registry entry: record the approved plan, work the tasks, ask, and hand off. The manifest lists no individual tools, so the exact operations are not documented here. It runs as a local process over stdio and talks to a Beck instance, defaulting to the hosted service unless another URL is configured.
- When to use it
- Useful when you want a coding agent to keep a plan and task list in a shared Beck workspace rather than only in the conversation, including asking questions and handing work off to others.
- Requirements
- A local runtime able to run the npm package @becklabs/beck-mcp-server over stdio, on a desktop machine. A workspace token supplied in the BECK_API_TOKEN environment variable, created in Beck settings and named after the agent. Optionally BECK_API_URL to point at a self-hosted instance; it defaults to the hosted Beck service. Network access to that instance.
Installation
In SourceWeft
- Open Beck in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Tools
0Version history
1- v1.6.1LatestSep 28, 2026
Score
15% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.
