OpenCOOP MCP Server
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileB | Read the contents of a file in the shared project. |
| write_fileB | Create or overwrite a file in the shared project. |
| edit_fileB | Make a targeted edit to a file using search and replace. |
| list_filesB | List files and directories in the shared project. |
| search_filesC | Search for files matching a glob pattern. |
| grep_contentC | Search file contents using regex pattern. |
| directory_treeB | Get a tree view of the project directory structure. |
| lock_fileB | Acquire an exclusive lock on a file before editing. |
| unlock_fileA | Release a lock on a file after editing. Reports the truth about whether the lock was actually released. |
| list_locksA | List all currently active file locks in the project. |
| check_lockB | Check if a specific file is currently locked. |
| view_changesB | View recent changes made by all team members. |
| view_statsB | View statistics about the project. |
| who_is_onlineB | See which team members are currently connected. |
| list_snapshotsA | List saved previous versions of a shared-project file. Use before rollback_file to pick a version. |
| rollback_fileA | UNDO YOUR MISTAKE: restore a shared-project file to a previous version. Pass ONLY path to undo the last change. For a specific version: list_snapshots first, then pass path + snapshot_id. SAFE: current state is snapshotted first, so rollback is reversible. |
| opencoop_guideA | START HERE — call FIRST in every new conversation BEFORE any file work. Explains the shared project and behavior rules. |
| invite_memberB | Generate an invite link for a new team member. |
| list_membersA | List all team members and their permissions. |
| revoke_accessC | Revoke a team member's access. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Each tool targets a distinct action or resource: file CRUD, lock management, snapshot rollback, project views, team administration, and a guide. Related tools like check_lock vs. list_locks and list_members vs. who_is_online have clearly separated scopes. No two tools appear to do the same thing.
Most names follow a predictable verb_noun snake_case pattern (read_file, lock_file, list_snapshots, invite_member). There are a few minor deviations such as who_is_online, directory_tree, and opencoop_guide, but the set remains readable and mostly consistent.
At 20 tools, the set is on the heavier side but each tool maps to a meaningful collaboration operation. File operations, locking, snapshots, team management, and project visibility all justify their own tools. It is slightly expansive but not bloated.
The file lifecycle covers read, write, edit, list, and search, plus robust lock and rollback support. However, obvious file operations such as delete and move/rename are missing, and there is no explicit snapshot creation or diff operation. These are notable gaps in an otherwise broad collaboration surface.