README: document MCP server and both agent-integration paths#15
Merged
Conversation
The README was written in PR #13 (cleanup), before PR #14 added packages/mcp-server. As a result, the MCP integration path was invisible to anyone landing on the repo, even though the server ships in the container build context. Changes: - Add packages/mcp-server to the Components list. - Rewrite the Agent integration section to cover both paths: - Option A: MCP server (Claude Code, Cursor, MCP-Inspector, any MCP-capable client). Single mcpServers JSON entry. - Option B: agentskills.io skill (Hermes, OpenClaw, Claude Code). Symlink the skill into the agent's skill directory. Both target the same BRAIN_DIR and expose the same four tools.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The README was written in PR #13 (Logseq cleanup), before PR #14 added
packages/mcp-server. As a result, the MCP integration path was invisible to anyone landing on the repo — even though the server ships and works.What changed
packages/mcp-server.mcpServersJSON entry in the agent's config.Both target the same
BRAIN_DIRand expose the same four tools. Picking the right one depends on what the agent supports.Why this matters
For external discovery (ClawHub listing, casual visitors, future alpha testers), the README is the front door. Missing the MCP path made it look like BizerBrain only worked with three named agents, when in fact it works with anything that speaks MCP.
Test plan
$BRAIN_DIRGenerated by Claude Code