Exposes the FCoP Python Core protocol to AI clients through 25 canonical tools and 6 read-only resources for durable agentic workflows.
Also known as joinwell52-AI/FCoP, fcop-mcp
- Stars
- 4
- Tools
- —
- Downloads, 30 days
- 1,016
- Latest version
- 4.0.5
- Last commit
- Nov 13, 2026
- License
- MIT
What is fcop MCP?
fcop exposes the FCoP Python Core protocol to AI clients through 25 canonical tools and 6 read-only resources for durable agentic workflows.
Summary generated from the project's README
About fcop MCP server
Managing durable agentic workflows through the FCoP Python Core protocol is what this server enables for developers using AI clients like Claude Desktop, Cursor, or Codex. It acts as a thin adapter that exposes 25 canonical tools and 6 read-only resources to your local environment. By connecting via local stdio, the server allows an AI agent to interact with a structured workspace while the underlying core handles all validation, state transitions, and persistence.
Setting up the server requires a dedicated Python 3.10 to 3.13 environment where both the fcop and fcop-mcp packages are installed in lockstep. Users must configure their MCP client with the absolute path to the virtual environment's Python executable and set the FCOP_PROJECT_DIR to the specific project root. This setup ensures that the AI can perform critical operations such as initializing workspaces, creating tasks, and managing lifecycle transitions within a reliable protocol framework.
What you can do with it
- 1Initialize a new workspaceAn AI agent can set up a fresh FCoP environment for a project using the workspace initialization tool.
- 2Create and manage tasksDevelopers can instruct an AI to generate new tasks within the protocol to track work progress.
- 3Inspect project resourcesAn AI client can read versioned content and protocol facts through the provided read-only resources.
Written from the project's README. Every use case is checked against a quote from it.
How to install fcop MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall fcop MCP in Claude Code
$ claude mcp add fcop -- uvx fcop-mcpInstall fcop MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"fcop": {
"command": "uvx",
"args": [
"fcop-mcp"
]
}
}
}Install fcop MCP in VS Code
.vscode/mcp.json
{
"servers": {
"fcop": {
"type": "stdio",
"command": "uvx",
"args": [
"fcop-mcp"
]
}
}
}Install fcop MCP in VS Code CLI
$ code --add-mcp '{"name":"fcop","type":"stdio","command":"uvx","args":["fcop-mcp"]}'Install fcop MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"fcop": {
"command": "uvx",
"args": [
"fcop-mcp"
]
}
}
}Install fcop MCP in Codex
$ codex mcp add fcop -- uvx fcop-mcpInstall fcop MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.fcop] command = "uvx" args = ["fcop-mcp"]
Install fcop MCP in Gemini CLI
$ gemini mcp add -s user fcop uvx -- fcop-mcpInstall fcop MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"fcop": {
"command": "uvx",
"args": [
"fcop-mcp"
]
}
}
}Configuration
FCOP_PROJECT_DIRAbsolute path to your project root (optional, auto-detected if omitted).
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablejoinwell52-ai/fcop is public and reachablegithub.com/joinwell52-ai/fcop ↗Pass
- Package names this repository as its sourcefcop-mcp names joinwell52-ai/fcop as sourcepypi.org/project/fcop-mcp/ ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-13github.com/joinwell52-ai/fcop ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from fcop-mcpPass
- No critical advisory in the package or its dependencies69 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- 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 GitHubfcop-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')"
fcop and fcop-mcp are released in lockstep within the same minor line.
Do not mix incompatible minor versions.
macOS (Intel and Apple silicon)
FCoP MCP supports both Intel and Apple silicon Macs; Rosetta is not required. With Python 3.10–3.13:
python3 -m venv ~/.local/share/fcop/venv
~/.local/share/fcop/venv/bin/python -m pip install --upgrade \
"fcop>=4.0.5,<4.1.0" \
"fcop-mcp>=4.0.5,<4.1.0"
~/.local/share/fcop/venv/bin/fcop version
~/.local/share/fcop/venv/bin/fcop doctor
~/.local/share/fcop/venv/bin/fcop tools --json
The installed CLI provides init, status, inspect, validate, tools, doctor, version, spec, and migrate. MCP additionally requires a client that supports local stdio servers. Configure the command as the absolute /Users/.../.local/share/fcop/venv/bin/python path, pass ["-m", "fcop_mcp"], and set FCOP_PROJECT_DIR to the actual project root.
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
fcop MCP questions
How do I add fcop MCP to Claude Code?
Run claude mcp add fcop -- uvx fcop-mcp in your terminal. Add --scope user to make it available in every project.
How do I add fcop MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools are included in the default fcop-mcp server?
The default server provides exactly 25 Canonical MCP Tools and 6 read-only Core Resources.
Does fcop-mcp initialize my workspace automatically?
No, installation only installs the packages; you must use the CLI or other methods to initialize or migrate a workspace.
Can I use fcop on macOS?
Yes, it supports both Intel and Apple silicon Macs without requiring Rosetta.