# @becklabs/beck-mcp-server

MCP server for Beck — record your agent's plan as epics and tasks, resume work, documents, and the task lifecycle

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.6.1
- **Author:** Unknown
- **License:** MIT
- **npm:** @becklabs/beck-mcp-server
- **Source:** https://github.com/beckhq/beck-plugin
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-06T23:49:08.126Z
- **Version scanned:** 1.6.1
- **CVEs:** none found by OSV at scan time

## Tools

40 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `whoami` — Return the identity behind this API token (token name/kind, mint permission, owner). Use to know how comments and progress will be attributed.
- `list_workspaces` — List Beck workspaces this token can see. Tokens are org-scoped — this is not a default workspace. If the human named one, use only that id. If more than one and
- `create_workspace` — Create a workspace in the current org or personal account. Default: only when the human asked for a new workspace. If they named an existing one, bind to that i
- `bind_workspace` — Bind a Beck workspace to this git repo (the directory the agent runs in) so later calls can omit workspaceId. Do this once per repo after the human picks the wo
- `list_api_tokens` — List API tokens for this account in the current org (names, prefixes, kind, mint permission). Never returns secrets. Use when staffing multi-bot channels.
- `create_api_token` — Mint a new API token named for a bot (e.g. Coder, Reviewer). Requires a mint-capable coordinator token (Settings → Tokens). Returns the raw secret once — hand i
- `revoke_api_token` — Revoke an API token by id. Owner only via API path.
- `list_tasks` — List tasks in a workspace. Can filter by status, epic, or show icebox items.
- `get_task` — Get full details of a task including description, acceptance criteria, and comments.
- `start_task` — Start working on a task. This assigns the task to you and changes status to 'started'. Use this before beginning implementation work.
- `finish_task` — Submit a task for review. Changes status to 'ready_for_review'. Pass progress to log what you did and finish in one call. Next step is accept_task / reject_task
- `accept_task` — Accept a ready_for_review task (marks completed). Follow autonomy mode: human_review → only if they asked; peer_review → reviewer/PM bot; full → allowed when th
- `reject_task` — Reject a ready_for_review task back to started. reason is required. Follow the same autonomy mode rules as accept_task.
- `list_comments` — List all comments on a task.
- `add_comment` — Add a comment to a task. Use this to document progress, ask questions, or provide updates.
- `update_task` — Update task details (title, type, points, tags, epic, description, blocked status, acceptance criteria, relevant files). Status cannot be set here — use start_t
- `set_relevant_files` — Set the relevant files for a task. Use this to record which files are important for the task, so future work sessions know where to look. Paths must be relative
- `get_task_context` — Get rich context for a task including epic spec, related tasks, comments, and activity. Use this when starting work on a task to understand the full context.
- `log_progress` — Log a structured progress update for a task. Use this to document what you attempted, what succeeded, what failed, and any blockers or questions.
- `list_progress` — List structured progress updates for a task.
- `recommend_task` — Get recommendations for what task to work on next. Returns tasks prioritized by: 1) Your in-progress work, 2) Tasks assigned to you, 3) High-priority unassigned
- `list_documents` — List planning documents in a workspace. Documents are the living PRD/notes corpus.
- `read_document` — Read a workspace document by path (e.g. prd or research/notes).
- `create_document` — Create a markdown document in a workspace.
- `write_document` — Update a document. etag is required (If-Match from a prior read_document). Writes without an etag are rejected so concurrent edits cannot silently overwrite.
- `delete_document` — Delete a document. etag is required (If-Match from a prior read_document) so concurrent deletes cannot race a newer edit.
- `list_document_versions` — List saved versions of a document (id, time, actor, etag). Use restore_document to roll back.
- `restore_document` — Restore a document to a previous version. etag is the current document etag (If-Match), not the version's etag.
- `list_epics` — List epics in a workspace (title, status, task counts, last plan, GitHub).
- `get_epic` — Get an epic: working spec, last-plan provenance, imported tasks, GitHub link, and latest suggested breakdown. Use after plan_it or when you need the spec withou
- `resume` — Brief for picking work back up in this repo's workspace: tasks in progress, waiting for review, next up, open epics and plan documents. Call at session start an
- `ask_decision` — Record a choice the human may want a say in, with the default you are going with, then keep working on that default. Returns right away; the answer comes back o
- `list_decisions` — List decisions in the workspace: open ones waiting on the human (costly first), then answered ones, newest first.
- `answer_decision` — Answer an open decision: give an answer or keep the default. For peer-review bots, only when the autonomy mode allows it; otherwise the human answers in Beck.
- `record_plan` — Record an approved plan in one call: saves the plan markdown as a document under plans/, then creates each epic and its tasks in order. Use right after the huma
- `create_epic` — Create an epic in a workspace. Use create_tasks to add its work.
- `create_tasks` — Add tasks to an epic, in order, at the bottom of the backlog (or icebox). Use when scope grows mid-run or to finish a partial record_plan.
- `plan_it` — For people planning without an agent: snapshot selected documents into one or more epics, optionally with Beck's AI task breakdown. If you planned the work your
- `import_suggested_tasks` — Import pending Plan-it / breakdown suggestions from an epic into the backlog or icebox. Use when asked or when autonomy mode allows. Prefer get_epic first to se
- `link_epic_github` — Link a GitHub branch or PR to an epic. Use this after creating a branch or opening a PR for an epic's work.

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"beck-mcp-server\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@becklabs/beck-mcp-server\"\n      ],\n      \"env\": {\n        \"BECK_API_TOKEN\": \"<YOUR_BECK_API_TOKEN>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `BECK_API_TOKEN` — Beck API Token (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Extensive blast radius — deletes data; holds an api key.
- Floor 53, ceiling 53 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40becklabs%2Fbeck-mcp-server
- Install plan: https://forgeregistry.com/api/v1/packages/%40becklabs%2Fbeck-mcp-server/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40becklabs%2Fbeck-mcp-server
- HTML page: https://forgeregistry.com/registry/%40becklabs%2Fbeck-mcp-server
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.