protocols-io-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROTOCOLS_IO_CLIENT_ACCESS_TOKEN | Yes | Your protocols.io API access token |
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": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_public_protocolsA | Search for public protocols on protocols.io using a keyword. Results are sorted by protocol popularity and paginated with 3 protocols per page (use the page parameter to navigate, default is 1). When searching for reference protocols to create a new protocol:
|
| get_my_protocolsA | Retrieve basic information for all protocols belonging to the current user. To get detailed protocol steps, use get_protocol_steps. |
| get_protocolA | Retrieve basic information for a specific protocol by its protocol ID. To get detailed protocol steps, use get_protocol_steps. |
| get_protocol_stepsA | Retrieve the steps for a specific protocol by its protocol ID. |
| create_protocolA | Create a new protocol with the given title and description. Before creating a new protocol, ensure you have searched for at least 2 relevant public protocols using search_public_protocols and reviewed their detailed steps with get_protocol_steps for reference when adding steps. |
| update_protocol_titleA | Update the title of an existing protocol by its protocol ID. |
| update_protocol_descriptionA | Update the description of an existing protocol by its protocol ID. |
| set_protocol_stepsA | Replace the entire steps list of a specific protocol by its protocol ID with a new steps list. The existing steps will be completely overwritten. |
| add_protocol_stepA | Add a step to the end of the steps list for a specific protocol by its protocol ID. |
| delete_protocol_stepB | Delete a specific step from a protocol by providing both the protocol ID and step ID. |
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 10 tools
Each tool has a clearly distinct purpose: create, read, update, delete for protocols and steps, plus search. No overlapping functionality.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_protocol, get_protocol_steps). No deviations.
10 tools is well-scoped for managing protocols and steps, covering CRUD operations and search without excess.
Missing explicit delete_protocol tool and individual step update (only add, delete, replace all). Users cannot delete a protocol entirely, which is a notable gap.