fcop-mcp · Canonical MCP adapter for FCoP
mcp-name: io.github.joinwell52-AI/fcop
fcop-mcp exposes the official FCoP Python Core
to Codex, Cursor, Claude Desktop, and other MCP clients. It is a thin adapter
over Core, which remains the sole authority for protocol facts, validation,
state transitions, persistence, locking, and recovery.
Current version: 4.0.5. The default server exposes exactly 25 Canonical MCP Tools and 6 read-only Core Resources. The tool registry is derived from one canonical manifest. The resource registry projects versioned content owned by Core.
Install
Install the matching 4.0.5 package pair in a dedicated Python 3.10–3.13 environment:
python -m pip install "fcop==4.0.5" "fcop-mcp==4.0.5"
fcop-mcp==4.0.5 declares fcop>=4.0.5,<4.1.0. Verify both distributions:
python -c "from importlib.metadata import version; print('fcop', version('fcop')); print('fcop-mcp', version('fcop-mcp'))"
python -c "from fcop_mcp.server import mcp; print('fcop-mcp ready')"
For an isolated launcher:
uvx --from fcop-mcp==4.0.5 --with fcop==4.0.5 fcop-mcp --root /absolute/path/to/repository
Canonical 4.0.5 surface
The workspace tools include init_workspace, inspect_workspace, and
validate_workspace. create_task is the canonical TASK creation entry.
Profiles are explicit extensions. Toolkit commands, compatibility shims,
packaging operations, Host configuration, Runtime services, and application
scaffolding are outside the default MCP registry.
Team models, Solo mode, ME or other fixed roles, seats, and Host sessions are
not Base Protocol prerequisites. The default server neither requires nor
creates them. init_workspace does not generate AGENTS.md, CLAUDE.md,
Cursor rules, role templates, or session state.
The prior inventory is the historical 49-tool implementation surface. It
is not the current MCP contract. Every historical tool has one disposition in
the 4.0.5 migration guide.
For example, write_task is an opt-in deprecated Python compatibility shim,
and fcop_audit is a Toolkit CLI command. Neither appears in default
tools/list.
See the generated MCP tools reference for all 25 names, descriptions, and input schemas.
Configure an MCP client
A fixed virtual environment gives predictable startup and avoids importing a different editable package from another project.
{
"mcpServers": {
"fcop": {
"command": "/absolute/path/to/venv/bin/python",
"args": ["-m", "fcop_mcp", "--root", "/absolute/path/to/repository"]
}
}
}
On Windows, command is the virtual environment's Scripts\\python.exe.
Restart the MCP host after changing its configuration.
Installation only installs packages. It does not initialize or migrate a workspace, deploy rules, modify Host instructions, or configure another application.
CLI — Setup, inspect, and diagnose
CLI = Setup + Observe + Diagnose; MCP = Work.
| Command | Purpose |
|---|---|
fcop init |
Initialize a pure FCoP workspace |
fcop status |
View workspace status |
fcop inspect |
Inspect TASK / REPORT / ISSUE / REVIEW |
fcop validate |
Validate protocol structure |
fcop tools |
Inspect the installed MCP catalog |
fcop doctor |
Diagnose installation, environment, and compatibility |
fcop version |
Show installed versions |
fcop spec |
Show specification and rule identity |
fcop migrate |
Explicitly plan or apply a legacy workspace migration |
python -m pip install fcop
fcop version
fcop doctor
fcop init --root ./my-project
fcop status --root ./my-project
fcop validate --root ./my-project
python -m pip install fcop-mcp
fcop tools
fcop tools merge_branches --json
The local CLI operates without starting MCP. fcop tools reads this adapter's
canonical catalog without starting a server. Work operations such as
create_task, lifecycle transitions, Branch merge, and authorization use MCP
or the Python API. Canonical v4 workspace state belongs under <project>/fcop/.
fcop doctor does not access the network or modify Host configuration.
Authority and package boundary
An optional authorization Profile and evaluator must be supplied by the trusted application. A role name, TASK field, Profile document, or tool argument does not grant authority by itself.
| Package | Responsibility |
|---|---|
fcop |
Protocol Core, validation, atomic persistence, and recovery |
fcop-mcp |
25 canonical MCP tools and 6 read-only Core resources |
FCoP uses local stdio by default. Relay support is an explicit optional extra.
Python applications that use Project directly only need fcop.
中文简介
fcop-mcp 4.0.5 是 FCoP Core 的薄 MCP 适配层。默认服务精确提供
25 个 Canonical MCP Tools和 6 个只读 Core Resources。
Core 是协议事实和状态迁移的唯一权威。Team、Solo、ME、seat、Host session、
Profile、Toolkit、Compatibility 与 Runtime 都不会成为 Base Protocol 的默认前置条件。
历史 49 工具实现面的每个入口均已在 4.0.5 迁移指南中给出明确去向。
Documentation
- Repository
- Authoritative install prompt (English)
- 权威安装提示词(中文)
- Installation prompt MCP Resource
- MCP tools reference
- 4.0.5 migration guide
- Protocol introduction
- 中文协议入门
- Changelog
License
MIT · LICENSE
Metadata
Release files for fcop-mcp 4.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| fcop_mcp-4.0.5.tar.gz | 112.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fcop_mcp-4.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 236.0 kB
Release files / fcop_mcp-4.0.5.tar.gz
| Download URL | fcop_mcp-4.0.5.tar.gz |
|---|---|
| Size | 112.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
894c8fa87556bad60e4c8b0854093d5a3b461467d798d8c66a2018c1a3b83ebf
|
|
BLAKE2b-256 checksum How to use checksums |
a391c7e3d9521c679e5cdd50ba7c145b9a752ff87347a1211e72fc3302cceb81
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.9
|
Release files / fcop_mcp-4.0.5-py3-none-any.whl
| Download URL | fcop_mcp-4.0.5-py3-none-any.whl |
|---|---|
| Size | 123.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1ca030a12ddfd52b60411b9b95ab3f0072c8b2a8a34ae7fde17998b3550d5d2f
|
|
BLAKE2b-256 checksum How to use checksums |
6848d3083f48fa1290d8e8b603218d091761a306d800d8a346803f9076f45ff0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.9
|