MCP.so
Sign In

Beans MCP

@selfagency

About Beans MCP

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

Basic information

Category

Other

Transports

stdio

Publisher

selfagency

Submitted by

Daniel Sieradski

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"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

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

FAQ from Beans MCP

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