The MCP (Model Context Protocol) server for Beans provides programmatic and CLI interfaces for AI-powered interactions with Beans workspaces.
From the registry: Interact with the Beans CLI issue tracker agentically
Please install the `beans-mcp` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install the Beans CLI** — The Beans issue tracker CLI must be installed and its workspace initialised before running beans-mcp. (https://github.com/hmans/beans)
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["@selfagency/beans-mcp","<your-beans-workspace-path>"]
Note: Server is started with a workspace root path as an argument. Optional --cli-path, --port, --log-dir flags exist.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Persistent codebase knowledge graph. Survives session restarts and context compaction.
Validate oh-my-posh configurations and segment snippets against the official schema.