Beans MCP Server

@selfagency

Basic information

About Beans MCP Server

MCP (Model Context Protocol) server for Beans issue tracker. Provides programmatic and CLI interfaces for AI-powered interactions with Beans workspaces.

#beans#issue-tracker#issues #markdown #memory

Beans MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "beans": {
      "command": "npx",
      "args": [
        "-y",
        "@selfagency/beans-mcp@latest",
        "/path/to/your/repo"
      ]
    }
  }
}

Beans MCP Server tools

Initialize Beans in the current workspace, equivalent to the extension init command.

Archive completed or scrapped beans, equivalent to the beans CLI archive command.

Fetch full bean details by ID.

Create a new bean.

Update bean metadata fields (status/type/priority/parent/blocking).

Reopen a completed or scrapped bean into a non-closed status.

Update bean metadata fields (status/type/priority/parent/blocking). Consolidated replacement for per-field update tools.

Delete a bean (intended for draft/scrapped beans).

Create multiple beans in one call. Optionally assign all of them (or a subset) to a shared parent.

Update multiple beans in one call. Optionally assign all of them (or a subset) to a shared parent.

Mark all markdown checklist tasks within a bean as completed.

Unified query tool for refresh, filter, search, and sort operations.

Read, create, edit, or delete files under .beans (operation param).

Read extension output log or show guidance (operation param).

Overview

What is Beans MCP?

Beans MCP is a Model Context Protocol server for the Beans issue tracker. It provides programmatic and CLI interfaces for AI-powered interactions with Beans workspaces, enabling AI assistants to read, create, update, and manage issue beans.

How to use Beans MCP?

Run npx @selfagency/beans-mcp /path/to/workspace from the command line. Optional parameters include --workspace-root, --cli-path, --port, and --log-dir. The server exposes 13 public MCP tools for interacting with beans.

Key features of Beans MCP

Initializes, lists, views, and archives bean workspaces
Creates and bulk-creates beans with parent support
Updates bean metadata and body with concurrency control
Supports bulk updates and batch delete operations
Queries beans with filters, sort, and GraphQL passthrough
Marks markdown checklist tasks complete automatically

Use cases of Beans MCP

AI agents managing issue tracking workflows programmatically
Batch creation or updating of related beans under a shared parent
Automating closure or reopening of beans with cascading status on descendants
Integrating Beans with VS Code via the companion extension
Performing complex queries and generating Copilot instructions from workspace data

Frequently asked questions

What version of Beans CLI is supported?

The server checks against Beans CLI version 0.4.2 at startup. If versions differ, a warning is printed to stderr but startup continues.

How does Beans MCP handle path validation?

All file and log operations validate paths to stay within the workspace or VS Code log directory. The `.beans/` prefix is automatically stripped from input paths.

Are bulk operations atomic?

No. `beans_bulk_create` and `beans_bulk_update` are best-effort: each item is processed sequentially and failures are reported per-item in the result array.

Does closing a parent bean affect its children?

Yes. Closing a parent bean via `beans_update` with status `completed` or `scrapped` cascades the same status to all descendants.

Does Beans MCP cache query results?

Unfiltered list results are cached with a short burst TTL and a timestamp-probe refresh strategy. Mutation tools immediately invalidate the cache.

Comments

More Other MCP servers

Klarix Intelligence Engine

Klarix

B2B competitive intelligence, live sales battlecards, 5-axis ICP prospect fit scoring, and tech stack teardowns over MCP and REST with cited public-web evidence.

Volley.sh

Volley

A good sequence diagram can solve almost any communication problem in engineering. Volley lets your agent write them as plain text, with the real request and response payloads on every arrow. It checks its own syntax wi