Skip to main content
mcpSource-backedReview first Safety Privacy

AccInt MCP Server for Claude

Local-first AccInt MCP server that gives Claude a scored Work Model through `acc_retrieve` and `acc_act`, so agent work can compound from real outcomes while the `acc.db` substrate stays on the user's machine.

HarnessClaude CodeCodexCursorClaude Desktop
Review first review before installing

Open the source and read safety notes before installing.

Safety notes

  • The MCP server launches the local `acc` binary; review the release binary, EULA, and installer before running it on sensitive machines.
  • `acc_act` can run bounded local work through runtimes such as `exec`, `browser`, and registered reusable actions, so host permissions and approvals matter.
  • External actions such as publishing, sending, deploying, deleting important data, or using credentials are designed to require owner authority before leaving the machine.
  • The installer probes hardware, downloads and verifies the matching release binary, and may download a large embedding model on first run.
  • The public repository contains Apache-2.0 installer, docs, plugins, and registry glue; the core engine binary is proprietary under the AccInt EULA.

Privacy notes

  • The Work Model substrate is a local SQLite file (`acc.db`) owned by the user; the MCPB bundle does not include that database.
  • Retrieval, scoring, prediction, and the local sandbox run on the user's machine rather than in a cloud memory service.
  • The public installer enables opt-out anonymous telemetry for event names and source refs only; it does not send prompts, files, memory, or Work Model data.
  • Use `ACC_NO_TELEMETRY=1` during install or `acc telemetry off` later if anonymous installer/runtime telemetry is not acceptable.
  • Receipts, commitments, and learned outcomes are written into the local substrate, so choose the database path and file permissions deliberately.

Prerequisites

  • Claude Code or another MCP client that can launch a local stdio server.
  • macOS, Linux, or Windows with permission to install the AccInt release binary.
  • Local disk space for `acc.db` plus the first-run embedding model download, which can be several GB.
  • Use the Official MCP Registry entry `io.github.maxbaluev/accint` when your client supports MCPB packages.

Schema details

Install type
cli
Troubleshooting
Yes
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
15 minutes
Difficulty
intermediate
Tool listing metadata
Disclosure
Source-backed public installer, host adapters, docs, plugins, and registry metadata are Apache-2.0. The AccInt engine source is private, and the prebuilt binary ships under the AccInt EULA.
Full copyable content
{
  "mcpServers": {
    "accint": {
      "command": "acc",
      "args": ["--db", "/absolute/path/to/acc.db", "mcp"]
    }
  }
}

About this resource

Content

AccInt is a local Work Model MCP server for Claude and other coding agents. It exposes two MCP tools: acc_retrieve, which reads the scored substrate by late-interaction retrieval, and acc_act, which records commitments, solves sub-goals, runs bounded local work, registers reusable runtimes, and closes outcomes after reality answers.

Use AccInt when you want agent work to compound across projects without sending the Work Model to a cloud memory service. The substrate is a local SQLite file (acc.db), and the same file can be shared across Claude Code, Codex, OpenCode, and Cursor host wiring.

Source Review

These sources were reviewed on 2026-06-18. Prefer the repository README, install guide, official MCP Registry entry, and live site for current install paths and platform support.

Features

  • Two MCP tools: acc_retrieve for scored Work Model retrieval and acc_act for actions such as solve, continue, outcome, exec, register, and browser or registered runtimes.
  • Local-first storage through a user-owned acc.db SQLite substrate.
  • Official MCP Registry identity io.github.maxbaluev/accint with MCPB packages for supported macOS, Linux, and Windows targets.
  • Host wiring for Claude Code, Codex, OpenCode, and Cursor through acc hosts-sync.
  • Outcome-credit workflow where passing tests, owner approval, delivered actions, or other grounded results can strengthen future retrieval and action choices.
  • Public Apache-2.0 installer/docs/plugins/registry glue with a proprietary local engine binary under the AccInt EULA.

Installation

Install AccInt from the Official MCP Registry entry io.github.maxbaluev/accint when your client supports MCPB packages. For broader self-serve setup, follow the repository install guide and review the installer before running it.

If AccInt is already installed locally, add the stdio server to Claude Code:

claude mcp add accint -- acc --db /absolute/path/to/acc.db mcp

To wire all detected local agent hosts after installation:

acc hosts-sync
acc status

MCPB-aware clients can install the official MCP Registry entry io.github.maxbaluev/accint instead of running the broad self-serve installer. The registry path ships the local acc binary, not a prebuilt acc.db.

Configuration

If you wire the MCP server manually, point your client at the local acc binary and choose a database path:

{
  "mcpServers": {
    "accint": {
      "command": "acc",
      "args": ["--db", "/absolute/path/to/acc.db", "mcp"]
    }
  }
}

The same acc.db path can be reused across compatible host agents when you want one Work Model to accumulate lessons from multiple tools.

Use Cases

  • Let Claude retrieve project- or business-specific context that has been strengthened by real outcomes rather than raw recall alone.
  • Record a commitment before agent work starts and close it when a test passes, a browser flow completes, or the owner confirms the result.
  • Reuse routines that have already worked, such as scripts, browser flows, or MCP runtimes, instead of re-reasoning through the same task every session.
  • Share one local Work Model between Claude Code and other coding-agent hosts.
  • Keep operational learning on a machine you control while still allowing explicit, approved external actions.

Safety and Privacy

AccInt runs as a local binary with real host permissions, so install it only on machines where that trust boundary is acceptable. Review the installer, release binary, EULA, and MCP client permissions before connecting it to sensitive workspaces. acc_act can invoke local execution, browser, and registered runtime paths; external actions are designed to require owner authority before publishing, sending, deploying, deleting important data, or using credentials.

The Work Model stays in a local SQLite file chosen by the user. The MCPB bundle does not ship a database, and retrieval, scoring, prediction, and sandboxed work run locally. The public installer enables opt-out anonymous telemetry limited to event names and source refs; it excludes prompts, files, memory, and Work Model data. Disable it with ACC_NO_TELEMETRY=1 during install or acc telemetry off later.

Troubleshooting

Claude cannot find the tools

Run acc hosts-sync, restart Claude Code, then check that the configured MCP server points at the installed acc binary and a writable acc.db path.

First run takes a long time

The installer may download the embedding model on first use, which can be several GB. Let the installer finish, then run acc status or acc doctor for health output.

You need a marketplace install

Use the Official MCP Registry entry io.github.maxbaluev/accint when your client supports MCPB packages. The installer remains the broader path when you want host auto-wiring across local agent tools.

Telemetry is not acceptable

Set ACC_NO_TELEMETRY=1 before running the installer, or run acc telemetry off after installation.

Duplicate Check

No AccInt, Accreted Intelligence, accreted-intelligence, maxbaluev, or matching AccInt source URL entry was found in content/mcp or the repository content before this submission.

Source citations

Add this badge to your README

Show that AccInt MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/accint-mcp-server.svg)](https://heyclau.de/entry/mcp/accint-mcp-server)

How it compares

AccInt MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldAccInt MCP Server for Claude

Local-first AccInt MCP server that gives Claude a scored Work Model through `acc_retrieve` and `acc_act`, so agent work can compound from real outcomes while the `acc.db` substrate stays on the user's machine.

Open dossier
Engram MCP Server

Local-first persistent memory MCP server for AI coding agents, backed by a single Go binary, SQLite, FTS5 search, CLI, HTTP API, and TUI.

Open dossier
Roam Code

Local codebase intelligence CLI and MCP server that gives Claude a SQLite code graph, change-safety gates, code health checks, impact analysis, review tools, and audit evidence for agent-assisted coding.

Open dossier
bb-browser MCP Server

Browser-control MCP server and CLI that lets AI agents use a real Chrome session, including logged-in browser state, site adapters, DOM snapshots, authenticated fetches, network traces, screenshots, and page actions.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorMax BaluevGentleman ProgrammingCranotepiral
Added2026-06-182026-06-052026-06-062026-06-06
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesThe MCP server launches the local `acc` binary; review the release binary, EULA, and installer before running it on sensitive machines. `acc_act` can run bounded local work through runtimes such as `exec`, `browser`, and registered reusable actions, so host permissions and approvals matter. External actions such as publishing, sending, deploying, deleting important data, or using credentials are designed to require owner authority before leaving the machine. The installer probes hardware, downloads and verifies the matching release binary, and may download a large embedding model on first run. The public repository contains Apache-2.0 installer, docs, plugins, and registry glue; the core engine binary is proprietary under the AccInt EULA.Engram can save, update, delete, search, compare, judge, merge, and summarize project memories that may influence future agent behavior. Incorrect or stale memories can steer an agent toward bad assumptions, so review saved decisions, architecture notes, and task learnings periodically. Use explicit project selection or repo-local configuration when multiple projects are visible to the MCP server. Cloud sync is opt-in; review project scope, tokens, allowed projects, and repair flows before enabling shared replication.Roam Code exposes many code-intelligence MCP tools; choose the narrowest `ROAM_MCP_PRESET` needed for the workflow. The server indexes local source code into a `.roam` SQLite-backed graph and may write run ledgers, decision receipts, caches, and generated evidence files. Some workflows can support change planning, review, and higher-authority modes, so keep `ROAM_AGENT_MODE` aligned with the MCP client's approval model. Static analysis, blast-radius, security, and health checks can miss runtime behavior or project-specific constraints. Treat Roam Code output as guidance for review and testing, not as proof that a change is safe to merge.bb-browser can control a real browser session, inspect pages, click elements, fill inputs, evaluate JavaScript, fetch URLs with browser authentication, capture screenshots, and inspect network traffic. Commands may act as the logged-in user on social, finance, job, developer, shopping, and knowledge websites. Keep the daemon bound to trusted local interfaces unless you deliberately configure remote access through a private network. Review community site adapters before using them with authenticated accounts or valuable sessions. Require human approval before posting, submitting forms, changing account settings, applying to jobs, making purchases, or running destructive site actions.
Privacy notesThe Work Model substrate is a local SQLite file (`acc.db`) owned by the user; the MCPB bundle does not include that database. Retrieval, scoring, prediction, and the local sandbox run on the user's machine rather than in a cloud memory service. The public installer enables opt-out anonymous telemetry for event names and source refs only; it does not send prompts, files, memory, or Work Model data. Use `ACC_NO_TELEMETRY=1` during install or `acc telemetry off` later if anonymous installer/runtime telemetry is not acceptable. Receipts, commitments, and learned outcomes are written into the local substrate, so choose the database path and file permissions deliberately.Memories can contain product plans, architecture decisions, code paths, prompts, implementation notes, incident details, and sensitive lessons learned. Local SQLite storage, exported sync chunks, Git-tracked memory files, cloud replication, HTTP API logs, and TUI copy actions can expose memory content. Do not store secrets, credentials, customer data, or unreleased security details unless the local store and any sync targets are approved for that data.Local source paths, symbols, imports, call graphs, git history, dependency relationships, and run evidence can be written to local Roam Code artifacts. The README describes the project as local by default with no API keys required and opt-in summary-only metrics push as the outbound surface. Review `.roam` artifacts, generated evidence, SARIF, reports, and logs before sharing them outside the repository. Avoid indexing private, regulated, or customer code unless the local machine, MCP client, and model workflow are approved for that codebase.Tab URLs, titles, DOM snapshots, page content, selected elements, screenshots, network requests, responses, console output, traces, and authenticated fetch results may be exposed to the MCP client and model. Browser login state is used by the page and browser; even if cookies are not extracted directly, commands can act through authenticated sessions. Network request bodies and response data may contain tokens, account data, personal messages, search history, customer information, or internal application data. The upstream privacy doc says communication is local and there is no telemetry or external server, but model providers still receive any data your MCP client sends in prompts or tool results.
Prerequisites
  • Claude Code or another MCP client that can launch a local stdio server.
  • macOS, Linux, or Windows with permission to install the AccInt release binary.
  • Local disk space for `acc.db` plus the first-run embedding model download, which can be several GB.
  • Use the Official MCP Registry entry `io.github.maxbaluev/accint` when your client supports MCPB packages.
  • Engram binary installed through Homebrew, GitHub Releases, Go install, or a source build.
  • MCP-compatible coding agent such as Claude Code, Codex, OpenCode, Gemini CLI, VS Code, Cursor, or Windsurf.
  • Project selection rules for where memories should be written, especially in monorepos or parent workspaces.
  • Optional cloud server configuration only when shared or cross-machine memory replication is desired.
  • Python 3.10 or newer.
  • A local repository that can be indexed by Roam Code.
  • Permission for the MCP client to read the target codebase and write Roam Code local index and evidence artifacts.
  • Run `roam init` or `roam index` in the repository before expecting complete graph-aware answers.
  • Node.js 18 or newer.
  • Chrome session, local daemon, and Chrome extension or supported OpenClaw browser path configured according to the upstream README.
  • MCP client such as Claude Code, Codex, Cursor, or another compatible host.
  • Explicit approval to let an agent use the active browser's logged-in state.
Install
claude mcp add accint -- acc --db /absolute/path/to/acc.db mcp
brew install gentleman-programming/tap/engram
pip install "roam-code[mcp]"
npx -y bb-browser --mcp
Config
{
  "mcpServers": {
    "accint": {
      "command": "acc",
      "args": ["--db", "/absolute/path/to/acc.db", "mcp"]
    }
  }
}
{
  "mcpServers": {
    "engram": {
      "command": "engram",
      "args": ["mcp"]
    }
  }
}
{
  "mcpServers": {
    "roam-code": {
      "command": "roam",
      "args": ["mcp"],
      "env": {
        "ROAM_MCP_PRESET": "core",
        "ROAM_AGENT_MODE": "read_only"
      }
    }
  }
}
{
  "mcpServers": {
    "bb-browser": {
      "command": "npx",
      "args": ["-y", "bb-browser", "--mcp"]
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.