Pick your tools in the chat.
Choose MCPs in a compact list beside your AI and Context pickers. Expand MAX to browse Connections, Tools and Access. Each conversation keeps its own selection.
AN alphaOS / bb PLUGIN
Your tools.
Every agent.
One home.
The work should move with you when you switch AI. Connect your MCP servers once, then give your agents the tools to read, write and finish the job.
Version 0.2.2 · Local installation · Read & write supported
YOUR INTELLIGENCE, CONNECTED
CClaude
OCodex
GGemini
HHermes
↗
THE CONNECTION LAYERMCP Management
DiscoverReadWrite ↗Verify
NDocuments
↗CRM
∞Workflows
One registry. The connections you choose. Access you control.
BUILT FOR WORK THAT GETS DONE
Shared connections · Real writes · Project permissions · Call receipts
THE CONNECTION LAYERYou chose your AI.
You chose your AI.
Your tools should
come with it.
You have a tool for your documents, a tool for your CRM, and a tool for your workflows. Then you have another copy of those connections for each AI.
Switch agents and you’re back to configuring servers, finding keys, and wondering which account can reach which tool.
MCP Management gives those connections a home inside alphaOS. Your agent finds the right capability through the hub, gets its exact input schema, and executes the operation using the access you granted.
Meet alphaOS ↗LESS SETUP. MORE FOLLOW-THROUGH.Give your AI the tools
Give your AI the tools
to complete the task.
Let your AI take action.
Create records. Update documents. Run workflows. Read & write access gives your agents the tools to finish the job, with optional confirmation for individual operations.
Choose who gets access.
Set access by project and agent. Keep a client’s tools in that client’s workspace. Disable a connection and its next call is blocked, even in an existing conversation.
See what actually happened.
Review a receipt for every execution attempt: the tool, project, outcome and duration. Credentials and argument bodies stay out of the activity log.
INTERACTIVE PREVIEW
Try the connection layer.
Switch agents, create a sample task, and see its receipt. This preview runs in your browser with illustrative data.
MCP Management
Your tools, ready for work.
3Connections
Read & writeTask connection access
0Operations in this preview
N
DocumentsProject workspace
Connected✓
TasksRead & write enabled
Connected∞
WorkflowsAgency workspace
ConnectedA simulated write. Your real accounts are never contacted.
LATEST CALL RECEIPT
Ready when you are.
- Tool
- create_task
- Agent
- Claude
- Project
- My workspace
- Result
- Waiting for a task
MAKE IT YOURSOne plugin.
One plugin.
Your whole toolset.
Install MCP Management, import or add your servers, and choose which projects and agents get access.
Download v0.2.2Source package · MIT license · alphaOS / bb 0.42+ · Node 22
Read the installation guide ↗● ● ●INSTALL MCP MANAGEMENT
tar -xzf bb-plugin-mcp-management-0.2.2.tgz
cd package
npm install --omit=optional
bb plugin build
bb plugin install . --yes- 01Open MCP Management
Manage servers in the sidebar. Choose active MCPs beside the AI and Context pickers in chat.
- 02Add or import a server
Select an account, project and read or write access. Each conversation can keep its own active connections.
- 03Test. Enable. Get to work.
Inspect the tools, grant access, then start a new agent session.
A FEW PRACTICAL QUESTIONSBefore you
Before you
connect.
Version 0.2 is built for a local hub. Your computer hosts the connections and needs to be available when agents use them.
Can I remove an MCP I do not use?
Yes. Select it in the dashboard and choose Remove connection. Confirm to clear its saved credentials, tool rules and chat/default selections. Activity receipts are kept. Use Disable connection to pause access while keeping its setup.
Does the picker control my existing native MCPs?
The chat picker controls connections routed through MCP Management. Separately configured tools native to Claude, Codex or another provider remain available until those connections are migrated or removed.
Does it support writes?
Yes. Read & write is the default access mode. After testing a connection and enabling its tools, agents can execute writes supported by that server. You can require confirmation for every call or selected tools.
Which MCP servers can I connect?
Local servers launched with a command, and remote servers using Streamable HTTP or legacy SSE. API keys and static headers are supported. OAuth is available through the MCP SDK’s sign-in flow; individual providers may require registered clients or additional setup.
Does it replace my existing MCP configuration?
Import reads user-level Claude and Codex definitions. Your existing configurations stay available. Each imported connection is tested and its tools are enabled in the dashboard before the shared gateway can execute them.
Can Hermes use it?
Hermes sessions inside alphaOS can use the plugin tool bridge when their provider supports it. Independent Hermes gateways can use a separately configured HTTP client and private tunnel. Installing the plugin does not change your Telegram gateway setup.
Where are my credentials stored?
In the host’s local secret settings, separate from connection metadata and activity receipts. This is local storage protected by owner permissions. It does not isolate credentials from every process running as the same operating-system user.
What does this release include?
A compact picker with a three-column MAX view, configurable Notion-first defaults, connection removal, redesigned connection settings, tool explorer and execution console, project and agent permissions, read and write operations, optional confirmations, activity receipts, a CLI, and individually revocable external client credentials. It proxies MCP tools; resources, prompts and embedded MCP app interfaces are outside this release.
BUILT BY BRIAN DECODEDKeep the connections.
Keep the connections.
Choose the intelligence.
A practical piece of the operating system I’m building for working with AI.