Connect your existing agent
Wire your existing agent into BitsWeave in three steps — add the MCP server over OAuth, install af-tap with the af-tap-install skill, then verify by creating an artifact and watching a live session.
This is the fastest path into BitsWeave: keep using the agent you already run, and connect it so BitsWeave can see your sessions and your agent can call BitsWeave's tools. No new agent to install, no token to copy, no JSON to hand-edit — the MCP server signs in over OAuth and af-tap installs itself through a skill.
By the end you'll have:
- The af-api MCP server added to your agent over OAuth — so it can call BitsWeave tools (read your org, projects, sessions, and more) from a prompt.
af-taprunning locally, mirroring each agent session into BitsWeave as a work session — so your activity shows up live.
Prerequisite
You need to be in an org and have it pinned active. If you're not yet, start with Join or create an organization.
The three steps
Add the MCP server (OAuth)
The af-api MCP server is an HTTP endpoint at /api/mcp. Add it once; your agent
signs in through an OAuth handshake in the browser, so there's no token to
paste.
For Claude Code:
claude mcp add --transport http bitsweave https://bitsweave.com/api/mcpThe first tool call opens an OAuth consent flow. Approve it and your agent is bound to your account and active org. Other agents (Cursor, Codex, Windsurf, …) take the same URL — see Connect your agents for the equivalent one-liners.
Install af-tap (one step)
af-tap is the other half — a local daemon that mirrors your agent sessions into
BitsWeave so you can watch them live. You don't install it by hand: tell your
connected agent to run the af-tap-install skill and it does everything —
installs the daemon, mints its token over MCP, and starts it.
Run the af-tap-install skill to install and start af-tap for me.The skill lives at products/agent-flow/af-tap/skills/af-tap-install/ and uses
the MCP server you added above to provision af-tap's credential. No PAT to copy.
Verify
Two observable success signals — one for each half of the connection.
1. MCP → an artifact in your graph. Ask your agent to create something over MCP:
Use the bitsweave MCP server to create a project called "Onboarding test"
and a document in it.Open your graph and confirm the artifact is there:
The new project and document show up as nodes. That round-trip proves the MCP server is wired, your OAuth credential is valid, and your active org resolved.
2. af-tap → a live session. With af-tap running, do a little work in an agent session, then watch it appear on your home feed:
A new work session shows up as a card on /app (with a detail view at
/app/sessions/<id>) and tracks what you're touching (repo, branch, files) in
real time. MCP alone gives you graph artifacts; + af-tap gives you the live
session on top.
You're connected
Your existing agent now reports its sessions into BitsWeave (via af-tap) and
can act on BitsWeave through its tools (via the MCP server). From here, head
to Concepts to learn how routing, agents, and sessions
work together.
Troubleshooting
- MCP tools return "authentication required" — the OAuth handshake didn't complete or expired. Re-run the tool call to re-trigger the browser consent flow, and make sure you approved it for the right org.
accounts_meresolves to no org — your account belongs to more than one org and none is pinned active. Call theaccountsseed, thenaccounts_setActiveOrgwith anorganizationIdfromaccounts_me. Or pin one from the org picker.- No live session on your
/apphome feed — af-tap isn't running, or there's been no activity since it started. Re-run the af-tap-install skill, or ask your agent to checkaf-tap status.