fcop-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| init_workspaceB | Create only a canonical FCoP 4.0 workspace at the server-bound root. An optional explicit profile is a reference, never executable authority. |
| inspect_workspaceA | Inspect protocol identity, envelopes, lifecycle, families and recovery facts without repair. |
| validate_workspaceA | Deterministically validate canonical workspace facts through Core validators; never repair or consult host/runtime state. |
| create_taskC | Create a TASK using Core T1 and its workspace-scoped operation identity. Repeated requests retain Core idempotency semantics. |
| claim_taskC | Request Core T2 inbox to active; actor records attribution and grants no authority. |
| submit_taskD | Request Core T3 active to review with the explicit current-attempt REPORT. |
| approve_taskD | Request Core T4 review to done using independently validated review and authorization evidence. |
| reject_taskD | Request Core T5 review to active; Core validates evidence and advances the attempt. |
| reopen_taskC | Request Core T6 done to active with explicit reopen evidence and authorization. |
| archive_taskD | Request Core T7 done to archive; Core enforces authorization and family convergence. |
| inspect_taskC | Read Core lifecycle, current attempt and transition evidence for a TASK. |
| list_tasksC | List validated canonical TASK facts, optionally filtered by stage or relations. |
| read_taskC | Read a canonical TASK by its typed identity through Core. |
| create_branchC | Create a branch TASK through Core T1 with an explicit branch_of relation. |
| inspect_familyC | Read Core family membership, REPORT heads, digest and convergence readiness. |
| merge_branchesC | Record the caller's convergence decision atomically in Core; never choose winners or archive the root. |
| write_reportC | Append a Core REPORT for the explicit TASK attempt; reporting does not accept or archive work. |
| write_issueC | Append a Core ISSUE with explicit workspace and subject identity. |
| write_reviewC | Append a typed Core REVIEW. Authority is evaluated only by trusted startup Profile evaluators. |
| list_reportsC | List REPORTs through Core, including exact attempt and head selection semantics. |
| read_reportC | Read a canonical REPORT through Core identity resolution. |
| list_issuesC | List validated canonical ISSUE facts, with deterministic filtering and pagination. |
| list_reviewsC | List validated canonical REVIEW facts; listing grants no authorization. |
| read_reviewB | Read a validated REVIEW from its canonical bucket without changing its decision. |
| mark_human_approvedC | Ask Core to append independent authorization evidence. Caller-supplied approver text alone is never authority; expires_at must be explicit. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| read_rules | Read package-owned FCoP 4.x rule facts through Core. |
| read_protocol | Read package-owned FCoP 4.x rule facts through Core. |
| read_guidance_sequential_en | Read package-owned FCoP 4.x rule facts through Core. |
| read_guidance_sequential_zh | Read package-owned FCoP 4.x rule facts through Core. |
| read_guidance_parallel_en | Read package-owned FCoP 4.x rule facts through Core. |
| read_guidance_parallel_zh | Read package-owned FCoP 4.x rule facts through Core. |
TDQS
Scored across 25 tools
Most tools target distinct resources or lifecycle transitions, and the descriptions clarify stage-specific actions. However, inspect_task versus read_task and inspect_workspace versus validate_workspace have subtle boundaries that could cause misselection, and the many lifecycle verbs require careful reading.
All tool names use consistent snake_case verb_noun phrasing, such as create_task, inspect_family, write_review, and mark_human_approved. The convention is predictable across lifecycle operations, artifact operations, and workspace operations.
Twenty-five tools is heavy for the apparent scope, sitting at the upper boundary before the surface feels excessive. The complex protocol justifies many lifecycle operations, but several read/inspect/list variants push the set beyond an ideal well-scoped size.
The surface covers workspace setup and validation, full task lifecycle transitions, branch/family convergence, reports, reviews, issues, and human approval evidence. Minor gaps remain, notably no read_issue equivalent despite write_issue and list_issues, but core workflows are otherwise covered.