Protocol Guide

io.github.thefiredev-cloudPublished by GitHub account thefiredev-cloudv1.0.0Updated Oct 24, 2026

Cited US EMS protocol search by agency and state, with exact protocol-number lookup.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Lets an assistant search cited US EMS protocols by agency and state, and look up a protocol by its exact number.

What you can do
Protocol Guide is a remote MCP server for US emergency medical services protocols. It supports searching protocols by agency and state and retrieving a protocol by its exact protocol number, with citations. The manifest lists no individual tools, so the exact tool names and parameters are not documented here.
When to use it
Useful when an assistant needs to find or quote a specific US EMS protocol for a given agency or state, for example during clinical reference or policy questions. Less relevant if you work outside US EMS or need protocols for other regions.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's host. Authentication is OAuth and is required, so the client must support the OAuth flow. No environment variables or headers are declared.
Before you install
Access requires an OAuth sign-in to a third-party service, so review what account data and queries are shared with that provider. Protocol content is reference material and may not reflect the latest local revisions; verify against the issuing agency before relying on it.

Installation

In SourceWeft

  1. Open Protocol Guide in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.thefiredev-cloud%2Fprotocol-guide/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "protocol-guide": {
      "type": "http",
      "url": "https://protocol-guide.com/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 10, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.