Get the FREE Ultimate OpenClaw Setup Guide →

protocols-io

An MCP server that enables MCP clients like Claude Desktop to interact with data from protocols.io.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio hqn21-protocols-io-mcp-server pipx run protocols-io-mcp \
  --env PROTOCOLS_IO_CLIENT_ID="Your Client ID for OAuth 2.0 (used with HTTP/SSE transport)" \
  --env PROTOCOLS_IO_MCP_BASE_URL="Base URL for MCP (used with HTTP/SSE transport), e.g., https://example.com" \
  --env PROTOCOLS_IO_CLIENT_SECRET="Your Client Secret for OAuth 2.0 (used with HTTP/SSE transport)" \
  --env PROTOCOLS_IO_CLIENT_ACCESS_TOKEN="Your Client Access Token for simple STDIO transport"

How to use

This MCP server exposes a suite of tools that connect protocols.io with MCP clients. Clients can search public protocols, retrieve protocol details and steps, or manage their own protocols and steps through create, update, and delete operations. In addition to retrieval and management, you can replace all steps of a protocol in one go or add and remove individual steps, enabling seamless synchronization of protocols.io content with your MCP workflow. To interact with Claude Desktop or other MCP clients, configure the server as an mcpServers entry and supply the necessary environment variables for authentication. The server supports STDIO transport by default and can be configured for HTTP or SSE transport as well, depending on your setup and credentials.

How to install

Prerequisites:

  • Python 3.10 or higher
  • pip (or use pipx for isolated execution)
  • Access to a protocols.io account with API credentials

Installation steps:

  1. Install the MCP server package (stdin example using pip):
pip install protocols-io-mcp
  1. (Optional) Install via pipx for isolated execution:
pipx install protocols-io-mcp
  1. Verify installation by running the CLI and ensuring it starts without errors:
protocols-io-mcp --help
  1. If you prefer using Docker, refer to the Docker-based deployment in the README (not shown here). Adjust environment variables as needed for your transport (STDIO, HTTP, or SSE).

Additional notes

Tips and examples:

  • For STDIO transport, only the CLIENT ACCESS TOKEN is required: set PROTOCOLS_IO_CLIENT_ACCESS_TOKEN in the environment before starting the server.
  • For HTTP/SSE transport, you will typically need CLIENT_ID, CLIENT_SECRET, and MCP_BASE_URL in addition to the token-based approach. Ensure the redirect URL is configured on protocols.io as described in the README.
  • When Claude Desktop reports spawn ENOENT, verify that the protocols-io-mcp executable is on your PATH. Use the full path to the executable if necessary (use which protocols-io-mcp to locate it).
  • If your MCP server is deployed behind a proxy or requires specific host/port binding, you can configure --host and --port when using the CLI transport options.
  • Always store sensitive credentials in environment variables and avoid committing them to configuration files.
  • If you switch between STDIO and HTTP/SSE transports, ensure the corresponding environment variables are defined for the chosen transport.

Related MCP Servers

Sponsor this space

Reach thousands of developers