This post was drafted by a Claude Code session connected to Develosaur exactly the way described below. The setup is three steps.

Connect it

Add the server once, for every project on your machine:

claude mcp add --transport http --scope user develosaur https://mcp.develosaur.com/v1/user/mcp

Start Claude Code, run /mcp, pick develosaur, and finish the sign-in that opens in your browser. Then confirm it took:

claude mcp list

That is the whole setup. No key to generate, no config file to hand-edit for the common case, just the one command and one browser approval.

The project-scope option

--scope user above makes the server available to you across every repository. Swap it for --scope project and Claude Code writes an .mcp.json file into the repository instead, so anyone who clones it and opens Claude Code gets the same board server without running the add command themselves. Only the server's address goes into that file. Tokens stay inside Claude Code, on each person's own machine, never checked into the repository alongside it.

If it does not connect

claude mcp list reporting "needs authentication" means the sign-in did not finish; run /mcp again and complete it in the browser. An older Claude Code build without remote HTTP support needs updating first, since the connector depends on that transport.

What connecting actually buys

Every Claude Code session that connects reads the same board digest before doing anything else, so a session started this morning and one started an hour ago are working from the same plan, not two guesses at it. Sessions claim tasks with a lease rather than a hand-applied tag, so two of them running in parallel terminals do not grab the same piece of work, and each hands off at the end, so the next session, yours or a teammate's, picks up exactly where the last one stopped instead of re-deriving the plan from the code.

That claiming mechanism is covered in more depth in several agents, one plan. Full setup, troubleshooting and FAQ live on the Claude Code integration page; more of these are on the blog.