BitsWeave

Connect the AI agents you already run to 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.

Connecting an existing AI agent is three steps: give it BitsWeave's tools over MCP, let it mirror your sessions with af-tap, then verify both. There's no token to copy and no JSON to hand-edit — the MCP server authenticates over OAuth, and af-tap installs itself through a skill.

Prerequisite

You need to be in an org and have it pinned active. If you haven't done that yet, start with Join or create an organization.

Step 1 — Add the MCP server (OAuth)

The af-api MCP server is an HTTP endpoint at /api/mcp that gives your agent BitsWeave's tools — read and write orgs, projects, tasks, sessions, and more — right from a prompt. 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/mcp

The first tool call opens an OAuth consent flow in your browser. Approve it and your agent is bound to your account and active org.

Other agents take the same endpoint through their MCP settings. Most clients (Cursor, Windsurf, and other JSON-config clients) accept an entry like:

{
  "mcpServers": {
    "bitsweave": {
      "url": "https://bitsweave.com/api/mcp"
    }
  }
}

Any MCP client that speaks Streamable HTTP and OAuth works — point it at https://bitsweave.com/api/mcp and complete the sign-in.

Create an org

Open the context explorer

Step 2 — Install af-tap (one step)

MCP gives your agent tools; af-tap is the other half — a local daemon that mirrors your agent sessions into BitsWeave as work sessions 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 (no PAT to copy), 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/. It uses the MCP server you added in Step 1 to provision af-tap's credential, so the only thing you do is ask.

Step 3 — Verify the install

Two checks, one for each half of the connection.

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.

Then open your graph and confirm the artifact is there:

Open your graph

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.

af-tap → a live session

With af-tap running (Step 2), do a little work in an agent session, then watch it appear live on your home feed:

Watch live sessions

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.

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_me resolves to no org — your account belongs to more than one org and none is pinned active. Call the accounts seed, then accounts_setActiveOrg with an organizationId from accounts_me. Or pin one from the org picker.
No live session on your /app home 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 check af-tap status.

Now that your agent is connected and building activity, head to Explore context to see the graph and summary your work produces.

Connect your agents