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. |
| 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. |
| 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 17 tools
Most tools have clear, distinct purposes (e.g., read vs. write vs. edit, search_files by name vs. grep_content by content). The only potential confusion is between list_files and directory_tree, but their descriptions clarify the difference.
Tool names mostly follow a verb_noun pattern (list_members, lock_file, invite_member). The main deviations are directory_tree and who_is_online, which break the pattern slightly but are still readable and predictable.
17 tools is on the higher end but appropriate for a collaborative file-sharing server covering file operations, locking, member management, and activity views. No tool feels redundant or excessive.
The surface covers file read/write/edit/list/search, locking, member management, and activity well. However, there is no delete_file tool, and member permissions cannot be updated, which are notable gaps for a full collaboration lifecycle.