ACDP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACDP_TOKEN | No | Authentication token for the socket server. Required when connecting to a remote server. | |
| ACDP_AGENT_ID | No | Unique agent identifier for coordination. Recommended for multi-agent setups. | |
| ACDP_SOCKET_URL | No | WebSocket URL of the ACDP socket server. Defaults to ws://localhost:3100. |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_localA | Start a local ACDP coordination server on this machine. You become the owner. Other agents can connect to your server using your IP and the generated token. Use this when YOU are hosting the coordination. |
| connect_remoteA | Connect to a remote ACDP coordination server on another machine. Use this when you need to coordinate with agents running on a different computer. You will need the server IP/hostname and the secret token (found in acdp-socket-server/config.json on the remote machine). ASK THE USER for these values if you do not have them. |
| connection_statusA | Check which coordination server you are currently connected to. |
| check_locksA | List all active file locks. Shows which files are locked, by whom, and when they expire. |
| lock_filesA | Lock files before modifying them. Other agents will see these files as unavailable. Fails if any file is already locked by another agent. |
| release_filesA | Release your locks on files. Use this when you no longer need exclusive access. |
| request_commitA | Request permission to commit changes to files. Auto-approved if you hold the lock and the files are not in a manual-approval path. Otherwise waits for owner approval. |
| notify_syncA | After committing changes, notify all other agents that these files have been updated. They will know to sync. This also auto-releases your locks on these files. |
| list_agentsA | List all agents registered on the coordination server and their connection status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| coordination-protocol | Instructions for how to coordinate file changes with other agents via the ACDP socket server |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/gabogabucho/ACDP-PCAD'
If you have feedback or need assistance with the MCP directory API, please join our Discord server