Binder MCP server
Commit Oct 20, 2026Lets AI agents query, create, and update typed entities in a local Markdown-synced knowledge base via MCP.
Also known as mpazik/Binder
- Stars
- 40
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Oct 20, 2026
- License
- MIT
What is Binder MCP?
Binder lets AI agents query, create, and update typed entities in a local Markdown-synced knowledge base via MCP.
Summary generated from the project's README
About Binder MCP server
Managing structured data for AI agents and automation pipelines is what Binder enables through a local-first, Markdown-synced knowledge base. It allows developers to define typed entities like Tasks, Contacts, or Decisions using a YAML schema, creating a persistent memory layer that agents can use to share state. The system functions as a graph of entities where every change is recorded as an immutable transaction, providing a full audit trail and the ability to undo or replay history.
Users interact with their data through multiple surfaces including a CLI, editor extensions for VS Code, WebStorm, or Neovim, and an MCP server for direct AI integration. For web-based workflows, the binder http command launches a local API and record browser. This setup is ideal for building small operations tools, inboxes for triaging leads, or registries for research without needing a full SaaS application.
What you can do with it
- 1Automated task trackingAn AI agent can manage a project pipeline by creating and updating task statuses via MCP.
- 2Maintaining agent memoryDevelopers can provide a structured way for different AI tools to share persistent context.
- 3Building custom admin panelsYou can host a local JSON API to build custom dashboards for managing your local records.
- 4Synchronized data editingManually editing Markdown files in an editor will automatically update the underlying database.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablempazik/binder is public and reachablegithub.com/mpazik/binder ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-20github.com/mpazik/binder ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubBinder
The database for tools you build with AI
Local-first, accessible from your editor, scripts, agents, and browser.
What it's for • Getting Started • How it works • Features • Working with Binder • Roadmap
What it's for
Binder is a perfect storage for all sorts of tools and automation built with agents. It especially excels when you need programmatic access and agent or human in the loop. Things like:
- Trackers and pipelines task tracking, hiring or sales. Binder holds the schema for stages, organizes files by status, and logs every change.
- Inboxes and queues of stuff to triage. Support tickets, leads, things an agent works through. Agents read and write over MCP or CLI. Scripts batch-process. Mistakes undo cleanly.
- Catalogs and registries you look things up in: vendors, subscriptions, research, contacts. Records are typed and link to each other. Query from the CLI. Autocomplete in the editor.
- Dashboards and admin panels for small ops tools that don't justify a SaaS or a full app.
binder httpgives you an API and a record browser. Drop inserver.tsfor your own routes. - Agent context and memory so your AI tools have somewhere typed and persistent to share state among themselves and people. Structured, fully transparent and easy to maintain.
Getting Started
1. Install Binder
npm install -g @binder.do/cli
bun install -g @binder.do/cli
2. Set up a workspace
binder init
The setup wizard will prompt you to pick a blueprint: a starter schema for common use cases like project management or personal notes.
3. Editor extension
Adds autocomplete for field names and valid values, inline validation, and syncs file edits back to the database on save.
- VS Code: install the Binder extension. Activates automatically in any Binder workspace.
Install the Binder plugin. Activates automatically in any Binder workspace.
require('lspconfig').configs.binder = {
default_config = {
cmd = { 'binder', 'lsp' },
filetypes = { 'markdown', 'yaml' },
root_dir = require('lspconfig.util').root_pattern('.binder'),
},
}
require('lspconfig').binder.setup({})
How it works
Binder stores your data as a graph of entities: each one a flexible collection of field-value pairs classified by a type like Task, Decision, or Contact. Fields are defined once and reused across types. References link entities directly, forming the graph. Types and fields are defined in .binder/types.yaml:
items:
- key: Task
fields:
- title: { required: true }
- status: { only: [pending, active, complete] }
- priority
- partOf: { only: [Milestone] }
- requires: { only: [Task] }
Editors, scripts, and agents all write to the same data. When something goes wrong, you need to know what changed and undo it. Binder records every change as an immutable transaction, attributed to its source. Full history, undo and redo, replay to any past state.
Markdown files are a view over this graph. Navigation rules define where each entity lives on disk. Change a field value and Binder moves the file automatically:
items:
- where: { type: Task, status: { op: in, value: [pending, active] } }
path: tasks/{priority} {key}
- where: { type: Task, status: complete }
path: archive/tasks/{key}
Features
Working with Binder
Same data, different surfaces. Use whichever fits the task.
Editors
Open any Markdown file in your coding editor to read, adjust, and review. Binder's LSP provides validation, autocomplete, and navigation across all entity files.
Install the VS Code extension to get started, or see Getting Started for WebStorm/IntelliJ and Neovim setup.
AI Agents
For autonomous work: querying context, capturing decisions, writing new entities. Agents can use the CLI directly or connect via MCP for a typed read/write API.
Add to .mcp.json to enable MCP:
{
"mcpServers": {
"binder": {
"type": "stdio",
"command": "binder",
"args": ["mcp"]
}
}
}
Scripts and Automation
For pipelines, batch operations, reports, or embedding Binder in your own apps and libraries. Query, create, and update records without parsing Markdown. Changes write back to files automatically.
$ binder search type=Task status=active -f "title,status,priority,partOf(title,status)"
items:
- title: Add dark mode support
status: active
priority: p2
partOf:
title: MVP Release
status: active
Pipe to any tool:
$ binder search type=Task status=active -q | jq '.items[] | .key + ": " + .title'
"setup-auth: Set up authentication"
"fix-layout-bug: Fix layout orientation bug"
Create and update without opening a file:
$ binder create Task dark-mode title="Add dark mode support" status=active priority=p2 partOf=mvp-release
$ binder update dark-mode status=complete
Embed Binder directly. Use it in a one-off script, a long-running service, a library, or any Node/Bun app:
import { open, isErr } from "@binder/repo/local";
const repo = await open("/path/to/workspace"); // omit to run from cwd
if (isErr(repo)) throw repo.error;
const { data: kg } = repo;
const r = await kg.search({ filters: { type: "Task", status: "complete" } });
if (!isErr(r)) for (const t of r.data.items) console.log("-", t.title);
await kg.close();
Workspace scripts. As a convenience, files in .binder/scripts/ (.ts, .js, .mjs, .sh) become first-class subcommands:
$ binder weekly-report # runs .binder/scripts/weekly-report.ts
$ binder run weekly-report # equivalent, never shadowed by built-ins
HTTP
For browser UIs, webhooks, and integrations. binder http starts a local server with a record browser at http://127.0.0.1:4000, plus a JSON API:
GET /api/schema- types and fieldsGET /api/records?type=Task&status=active- query recordsGET /api/records/:key- fetch onePOST /api/transactions- apply a transaction
Bring your own UI with --static <dir>, or drop one at .binder/web/ for zero config. The built-in record browser is the fallback.
Drop a server.ts next to your static files to add custom routes, built on Hono. Source files aren't served.
import { Hono } from "hono";
import type { ServerModule } from "@binder.do/cli";
const mod: ServerModule = ({ kg }) => {
const app = new Hono();
app.get("/api/stats", async (c) => {
const r = await kg.search({ filters: { type: "Task" } });
return c.json({ tasks: "data" in r ? r.data.length : 0 });
});
return app;
};
export default mod;
→ See HTTP server docs for the full reference.
Hooks
Run a shell command on every committed transaction. The transaction is piped to stdin as JSON. Declare them in .binder/config.yaml:
hooks:
- name: notify-slack
command: ./scripts/notify-slack.sh
- name: audit
command: jq -c . >> .binder/audit.log
Roadmap
Next
- More blueprints and examples
- Full-text and semantic search
- Transaction log compaction
Future
- Cross-device synchronisation
- E2E encrypted backup
- Encrypted fields
- Web / Mobile UI
Contributing
Binder is early-stage and actively shaped by feedback. Found a bug or have an idea? Open an issue. All input welcome.
License
Binder MCP questions
How do I connect an AI agent to Binder over MCP?
Add a binder entry to your .mcp.json with type stdio and the command binder mcp. Agents can then query, create, and update entities through a typed read/write API.
How do I query records from the command line?
Use binder search with filters like type and status, optionally selecting fields; output can be piped as JSON to tools like jq.
Can Binder expose an HTTP API?
Yes, binder http starts a local server with a JSON API and record browser, and you can add custom routes with a server.ts file.