ABCM MCP Server

TypeScript/Bun library and runnable server for exposing Agent Build Context Manager workspaces through MCP and an authenticated REST file API.

Status

0.1.0-alpha.1 is the first working migration target. It provides:

• bounded workflow and scope-map discovery;

• safe, atomic workspace file list/read/write/delete/move/directory operations;

• REST access with ETags, stable problem responses, and static Bearer authentication;

• MCP tools and the abcm://map resource backed by the same application services;

• self-hosting ABCM metadata, feature plans, verification plans, and reusable project skills.

The normative baseline is specification 0.5.0 plus the extensions in docs/spec/extensions. The executed plan is PLAN-0001.

Related MCP server: MCP Security Server

Requirements

• Bun 1.3.14 or newer

Verify

bun install
bun run check
bun run build

Run REST

export ABCM_API_TOKEN='replace-with-at-least-16-characters'
ABCM_WORKSPACE_ID=self ABCM_WORKSPACE_ROOT="$PWD" bun run dev:rest

GET /health is public. All /v1 routes require Authorization: Bearer <token>. See the REST API and quickstart.

Run MCP stdio

ABCM_WORKSPACE_ID=self ABCM_WORKSPACE_ROOT="$PWD" bun run dev:mcp

See the MCP API.

Library entrypoint

import { createAbcmRuntime } from "abcm-mcp-server";

const runtime = createAbcmRuntime(
  { id: "project", root: "/absolute/project/path" },
  { bearerToken: process.env.ABCM_API_TOKEN },
);

Alpha boundaries

Scope-map revisions are kept in memory; SQLite history, ContextBundle assembly, domain resolution, document synchronization, per-principal authorization, and durable audit records are later milestones.

License

MIT