The MCP surface
Add BitsWeave's MCP server to your agent and it gains one audited interface for organizations, projects, tasks, sessions, and your connected tools.
BitsWeave speaks MCP (the Model Context Protocol). When you add the BitsWeave MCP server to your agent, the agent gains a single, typed set of tools for reading and changing everything in your organization — and every call is authenticated and logged.
This page is a high-level tour, not a full reference. The exact tools your agent
sees depend on what you've connected and what your access allows. The advertised
list is a small keep-set (context_search, tools_search, tools_call) plus
domain seeds (accounts, organization, documents, records, sessions, brokers).
Broker seeds appear only for brokers with an active install on the org. The
broker catalog seed is not advertised. tools.search still lists installable
broker tools that are not installed: those rows set installed: false and
installUrl to /app/brokers/new/<definitionId> so the agent can send the
user to the install page. The accounts seed lists
accounts_me and accounts_setActiveOrg so a multi-org MCP client can pin
an org. Platform admin tools sit under one
platform seed and only appear for platform admins. Operator, onboarding,
conversation, actions, and workflow surfaces are not advertised over MCP.
MCP tools/call also rejects billing.* and actions.* — those are not
MCP-compatible. The web app (tRPC) still serves them. Each advertised tool
includes MCP annotations (title, readOnlyHint, destructiveHint,
openWorldHint) and an outputSchema for Claude and other directories.
context.summary is a streaming query, so its hint is read-only.
What your agent can reach
Once the MCP is added, your agent can work with the same things you do in the BitsWeave UI:
Organizations & members
Read your organization, its members, roles, and invitations — the people and permissions your work happens inside.
Projects & tasks
Create and update projects, tasks, and labels so plans and progress live where the whole team can see them.
Work sessions
Open, inspect, and close work sessions, and see who is touching the same repo or branch right now.
Notes & decisions
Capture durable notes and record decisions that outlive any single run.
Connected tools
Act through brokers — open and comment on GitHub pull requests, send email, query observability — without holding the underlying credentials.
Why a single surface
Instead of wiring your agent to GitHub here, an email provider there, and a database somewhere else — each with its own credentials and its own audit story — your agent talks to one surface.
- One credential. The agent authenticates to BitsWeave with a Personal Access Token; BitsWeave holds the credentials for the tools behind it. See Organizations & access.
- One audit trail. Every tool call is attributed and logged, so you can see exactly what an agent did and on whose behalf.
- One permission model. What a token can do is scoped by the organization and role behind it — the same rules whether a human or an agent makes the call.
Brokers, not raw keys
Connected tools are reached through brokers. Your agent asks BitsWeave to "comment on this pull request"; BitsWeave uses the stored integration to do it. The agent never sees the GitHub or email credential itself.
Where this fits
The MCP surface is how a connected agent acts; work sessions are how its activity (and yours) becomes visible. Both are scoped by your organization.
To add the MCP server to your own agent, follow Getting Started.
Work sessions & af-tap
af-tap mirrors each of your Claude Code sessions into BitsWeave one to one, so the work you do locally shows up as a live, shared work session.
Organizations & access
An organization is your tenancy and access boundary in BitsWeave. You and your agents authenticate to it with a Personal Access Token.