Skip to content
DocblockOpen workspace

Claude Code integration

Give a coding session the project context it needs.

Code explains how something works today. Docblock can hold the brief, decisions, and research behind it. Connect Claude Code over MCP so it can consult that context during your work.

01

Retrieve the project’s reasoning

Ask for the decision note or research behind a change before planning implementation. Keep the source in a note that people can also review.

02

Use browser sign-in or a token

Add Docblock as a remote HTTP MCP server, then authenticate through Claude Code. The guide also covers an authorization header with a scoped token.

03

Leave a useful handoff

Authorize an append, a proposed note update, or a daily entry after meaningful work. Keep the unresolved questions visible for the next session.

FROM IDEA TO USEFUL CONTEXT

Put it into practice.

  1. Add the remote server

    Follow the Claude Code HTTP MCP setup in the agent guide.

  2. Authenticate and scope it

    Choose the workspace, optional folder limit, and read or write boundary that fits the project.

  3. Verify context retrieval

    Ask Claude Code to read a known note and cite the decision relevant to the current task.

A FEW USEFUL DETAILS

Questions, answered.

Can I make the connection available across projects?

Yes. The Claude Code setup guide documents the user-scope option for making the server available across projects.

Do note edits alter repository files?

Docblock tools operate on workspace notes. Claude Code’s access to repository files is separate from the Docblock connection.

KEEP EXPLORING

Connect the next piece.

A PLACE TO BUILD ON

Give your next thought a home.

Start with a note. Add structure, connect an agent, and keep the useful context together.

Open Docblock