How do I connect Brain Os MCP Server to Claude?

The listing records `npx brain-os init` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Code, Cursor, Windsurf as compatible clients.

Is Brain Os MCP Server free?

The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.

What can Brain Os MCP Server do?

Brain Os MCP Server documents 22 tools to the agent, including action_guard, audit_log, context_resolve. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.

Brain Os

Unclaimed

by brainOS-HQ

Local-first MCP memory server for operational project state: decisions, blockers, plans, patterns, and next moves.

Install

$npx brain-os init

Set up this server

Compare servers My Stack

This server needs project-specific setup. Follow the project instructions; no reusable public launch command is available yet.

Project instructions

agent-memoryai-agentsclaude-codecursordeveloper-toolslocal-firstmcpmodel-context-protocoloperational-memoryproject-state

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

22 of 22 tools

Documented tools (22)

From project documentation. A server handshake does not verify each tool’s description or behavior.

action_guard

Apply built-in guard templates to common high-risk actions before proceeding

audit_log

Read the full mutation history — what changed, when, by whom

context_resolve

Resolve which entity the current work belongs to, from explicit mention / alias / files / lexical signals. Deterministic and confidence-scored — routes known context, never guesses intent.

decision_check

Check a proposed action against active decisions — returns clear/caution/conflict

decision_log

Log a strategic decision with reasoning and alternatives

decision_refresh

Refresh an existing decision: bump reviewdate, append evidence, change status. Metadata only — does not mutate decision content.

decision_review

Review-debt inbox: buckets overdue decisions (still-true / changed / archive / needs-evidence) and recommends an action for each. Read-only — proposes, you confirm. Auto-detects duplicate-stub decisions.

entity_read

Read operational state of one or all tracked entities

entity_update

Update entity state — status, momentum, blockers, next moves

focus_get

Get prioritized recommendations on what to work on

memory_check

Audit memory quality — flags stale data, contradictions, noise

memory_commit

End-of-session commit — save all state changes

pattern_detect

Analyze patterns across all entities

plan_add

Add steps to an existing plan

plan_advance

Complete or skip a step (requires evidence/reason) — auto-promotes next

plan_read

View plan progress and current step

plan_set

Set an ordered plan for an entity — step 1 becomes active nextmove

project_evidence_scan

Read-only scan of a repo's native operating state (STATE.md, FLAGS, HANDOFF, ROADMAP/PLAN/TODO, git activity, dirty files) for human gates, next moves, and do-not-touch — grounds focus in repo reality.

risk_assess

Classify risky actions before execution, including public-release and destructive-operation risks

semantic_recall

Search memory by meaning using natural language

wrap_auto

Non-interactive safety-net wrap: applies low-risk fields and stages high-risk changes for review

wrap_check

Detect whether meaningful state changes have accumulated since the last wrap

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about Brain Os MCP Server

How do I connect Brain Os MCP Server to Claude?: The listing records `npx brain-os init` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Code, Cursor, Windsurf as compatible clients.
Is Brain Os MCP Server free?: The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can Brain Os MCP Server do?: Brain Os MCP Server documents 22 tools to the agent, including action_guard, audit_log, context_resolve. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.