Which integrations are available for this server?

Allows Obsidian to edit the human-readable Markdown layer of a ContextPact workspace, with planned reconciliation, import/export, backup and recovery.

How do I use ContextPact?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ContextPact Show approved decisions and task handoffs from my ContextPact workspace." That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

ContextPact

by aniklavida

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

ContextPact

Any agent. Same approved context.

ContextPact is a local-first context and coordination layer for people who move between AI tools or run several agents in parallel. It is designed to keep durable knowledge, current decisions, task ownership and handoffs outside any one AI product.

Project status

ContextPact is under active pre-release development. The repository currently contains the approved v1 specification, architecture, repository foundation and an experimental workspace bootstrap. It is not yet a production-ready context system and has not been released to npm.

Implemented and tested in the current foundation:

TypeScript build and test pipeline.
Context item and workspace contracts.
Local workspace layout creation.
SQLite schema bootstrap with WAL and FTS5.
Complete knowledge lifecycle, context-pack retrieval, and supersession.
Single-machine task leases, conflict handling, and structured handoffs.
Transport-independent core with 1:1 parity between CLI commands and MCP tools across bootstrap, context, decisions, tasks, and handoffs.
Guided MCP client configuration adapters (connect claude, connect codex, connect cursor) and generic MCP block generator.
Stdio connection self-check (contextpact connect --check) validating live server bootstrap and tool invocation.
Profile-based tool exposure ensuring default agent profiles never see approval tools.
Parity test suite enforcing zero undocumented gaps across interfaces.
Dual-store workspace backup and point-in-time restore covering both Markdown vault and SQLite database.
Portable workspace export and import with deterministic ID collision policies (skip, replace, error).
Workspace doctor diagnosing layout, schema versions, index freshness, orphaned files, expired leases, missing provenance, and rebuilt database state.

Planned for v1.0 and not yet advertised as supported:

Clean-machine recorded release evidence for Claude Code, Codex, and Cursor host integrations.
Obsidian edit reconciliation workflow and packaging.
Cross-platform clean-install and end-to-end proof.

Related MCP server: 50 First Tapes MCP Server

Intended experience

contextpact init
contextpact connect claude
contextpact connect codex
contextpact connect --check
contextpact status

Host connection status

ContextPact provides guided configuration adapters for supported hosts and generic output for other MCP clients:

Host Client	Adapter Status	Host Evidence Status	Configuration Target
Claude Code	experimental	planned	`~/.claude.json`
Codex	experimental	planned	`~/.codex/config.toml`
Cursor	experimental	planned	`~/.cursor/mcp.json`
Generic MCP	experimental	planned	Standard stdio block

Every host adapter merges ContextPact MCP server settings without modifying unrelated keys, remains strictly idempotent across repeated runs, and fails without writes on malformed configurations. Host verification remains planned until clean-machine release evidence is recorded.

Command and tool surface

ContextPact exposes its command surface identically through CLI commands and MCP tools over one transport-independent core:

Category	CLI Command	MCP Tool	Description
Bootstrap	`contextpact status`	`context_status`	Inspect workspace initialization and storage health
Context	`contextpact propose`	`context_propose`	Propose durable context or record operational notes
Context	`contextpact get <id>`	`context_get`	Retrieve context item by ID across lifecycle states
Context	`contextpact search <query>`	`context_search`	FTS5 full-text search with BM25 ranking
Context	`contextpact pack`	`context_pack`	Retrieve deterministic token-budgeted context pack
Context	`contextpact archive <id>`	`context_archive`	Archive approved context item
Context	`contextpact approve <id>`	`context_approve`	Approve proposed context (elevated/human profiles only)
Decisions	`contextpact decision propose`	`decision_propose`	Propose architectural or product decision
Tasks	`contextpact task create`	`task_create`	Create coordination task with declared scopes
Tasks	`contextpact task claim <taskId>`	`task_claim`	Claim, renew, or takeover single-machine task lease
Tasks	`contextpact task release <taskId>`	`task_release`	Release task lease with terminal status
Tasks	`contextpact task get <taskId>`	`task_get`	Inspect task and active lease state
Handoffs	`contextpact handoff create`	`handoff_create`	Record evidence-bearing structured handoff
Handoffs	`contextpact handoff get <id>`	`handoff_get`	Retrieve handoff narrative and evidence by ID
Handoffs	`contextpact resume <id>`	`handoff_resume`	Resume task from handoff and claim lease

Profile-based tool exposure

Default agent profiles connecting via MCP hold execution leases and propose knowledge, but cannot see or invoke approval tools. The context_approve tool is registered only for elevated reviewer or human operator profiles.

Documented interface differences

Ten CLI maintenance and runner commands have no MCP counterpart:

init: Workspace filesystem initialization executed from the terminal before agent processes launch.
connect: Host client configuration utility for writing MCP server definitions into external host configs (Claude, Codex, Cursor) or printing generic MCP blocks.
mcp: CLI transport launcher running the MCP server over stdio.
reindex: Offline administrative tool to rebuild SQLite FTS5 search indexes from disk.
reconcile: Offline administrative tool to reconcile external Markdown knowledge edits with SQLite state.
export: Offline administrative tool extracting Markdown vault and SQLite operational state into a structured archive.
import: Offline administrative tool importing external archives with deterministic collision policies.
backup: Offline administrative tool creating dual-store point-in-time snapshots covering both Markdown vault and SQLite database.
restore: Offline administrative recovery tool restoring snapshots covering both Markdown vault and SQLite database.
doctor: Diagnostic health check identifying damage, index staleness, schema drift, and rebuilt database state.

Architecture

Markdown owns human-readable knowledge, rules, goals, decisions and handoff narratives.
SQLite owns agents, sessions, tasks, leases, policies, versions and audit events.
FTS5 is a rebuildable search index; semantic retrieval is optional future work.
CLI and MCP call the same transport-independent core.
Obsidian may edit the Markdown layer but is never required.

See the product specification, architecture, roadmap, native modules and release checklist.

Development

Requires Node.js 22.14 or newer.

npm install
npm run check
npm run dev -- init ./scratch-workspace
npm run dev -- status ./scratch-workspace

Licence

MIT. See LICENSE.

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained

ResponsivenessUnresponsive

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

MDflowOAuth
cz.mdflow
Markdown workspace for AI agents: read, write, organize, and share markdown documents.
Note Taking Knowledge & Memory
2
writespace-mcp
io.github.write-space
Persistent docs and memory for AI agents — read, write, organize & search a shared workspace.
Knowledge & Memory Note Taking
2
Fastio
io.fast
Workspaces, file storage, sharing and AI search for agents and their humans.
handoff-mcp-server A
io.github.josephibra
Durable agent-to-agent handoffs and shared scratchpad for multi-agent workflows.
Agent Orchestration Autonomous Agents
2

Related MCP Servers

auxly-memory-cli
Knowledge & Memory File Systems
Tzamun-Arabia-IT-Co
A
license
Not graded
quality
A
maintenance
Local-first, file-based memory layer for AI agents — one shared Markdown vault across Claude, Codex, Gemini, Cursor and any MCP client. Provides read/write memory tools with an audit trail, per-agent trust levels, and Git sync; no cloud and no lock-in.
Updated 13 hours ago (2026-10-03 06:50 UTC)
2
MIT
50 First Tapes MCP Server
Note Taking Knowledge & Memory Version Control
adilzuberi
A
license
Not graded
quality
D
maintenance
Enables AI agents to read and write a local-first knowledge base of plain markdown files in git, with governance gates for safe, hash-anchored edits.
Updated 3 months ago (2026-07-08 06:34 UTC)
1
Apache 2.0
Coordination Memory MCP
Knowledge & Memory Autonomous Agents
yanqiw
A
license
B
quality
A
maintenance
An append-only coordination memory for multi-agent and human work, backed by SQLite, with a local dashboard and acceptance contracts that enforce integrator review before work is considered accepted.
Updated 20 days ago (2026-09-13 13:24 UTC)
43
1
MIT
AgentBridge MCP
Developer Tools Project Management
frograiny
A
license
Not graded
quality
C
maintenance
Enables coding agents to persist and resume shared working state—tasks, progress, decisions, commands, tests, checkpoints, and handoffs—backed by SQLite while keeping Git authoritative for files and repository state.
Updated 19 days ago (2026-09-15 05:46 UTC)
MIT

ContextPact

Project status

Intended experience

Host connection status

Command and tool surface

Profile-based tool exposure

Documented interface differences

Architecture

Development

Licence

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

auxly-memory-cli

50 First Tapes MCP Server

Coordination Memory MCP

AgentBridge MCP