Connect an MCP client

Point your editor or chat at a Sync project and start reading and writing knowledge over MCP.

Sync exposes a single Streamable HTTP MCP endpoint:

https://sync.buzz/mcp

Any client that supports the Model Context Protocol (spec revision 2025-03-26 or newer) can talk to it directly over HTTPS — no local bridge process, no mcp-remote wrapper. Your Personal Access Token goes in the Authorization header; the scope you picked decides which companies and projects the token can reach.

Get a personal access token

Tokens in Sync are issued per user, not per project. One token can reach whichever companies and projects you pick — handy when one editor window needs to work across a whole team's codebase.

Sign in at sync.buzz.
Go to Account → Tokens.
Click New token, give it a name, pick the companies and projects it should reach, and copy the token. You won't see it again.

The token starts with sync_pat_. Treat it like a password — anyone with it can reach the scope you picked, acting as you.

How role is decided

The token doesn't carry a role. Every MCP call is checked against your current membership in the target project:

Your membership role	What the token can do
viewer	read-only
member / admin / owner	read + write

If you're removed from a project or demoted, the token loses that access immediately — no rotation needed.

Scoping tips

Default scope is every project you're a member of. Good for a single editor that should "just work" across your teams.
Whole-company scope (checkbox at the company level) auto-includes future projects. Right for your main day-to-day editor.
Project-specific scope is tighter. Use it for tokens you want to paste into shared configs or CI, where leak blast-radius matters.

You can change a token's scope later without rotating the secret.

Pick your client

Claude Desktop

Point Claude Desktop at sync.buzz/mcp and use Sync tools right inside the chat.

Cursor

Add Sync as an MCP server to Cursor and let the agent read your project's knowledge.

VS Code

Wire Sync into the VS Code MCP integration — works the same way as Cursor.

Zed

Configure the Zed agent panel to use Sync as a remote MCP server.

Revoking a token

If a token leaks or you replace a laptop, go to Account → Tokens and click the × next to the token. It becomes invalid immediately — the next MCP call from that client will fail with 401 revoked_token. Issue a new one and update the client config.

What about OAuth?

Sync also implements OAuth 2.1 (RFC 8414 discovery, RFC 7591 dynamic client registration, PKCE S256) at https://sync.buzz/.well-known/oauth-authorization-server. Clients that support browser-based OAuth for MCP can register and authenticate without a pre-issued token. Support in desktop MCP clients is still uneven, so personal access tokens remain the recommended path for now. OAuth will become the default once client coverage stabilizes.