Railhook

io.github.vadymkykaloPublished by GitHub account vadymkykalov3.7.0Updated Oct 28, 2026

Webhooks for AI agents: send events, manage endpoints, inspect and retry deliveries.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Railhook's MCP server lets an assistant send webhook events, manage endpoints and subscriptions, and inspect or replay deliveries in a Railhook project.

What you can do
  • Send events into a Railhook project
  • List and create webhook endpoints
  • List and create subscriptions
  • List and inspect deliveries, and replay a failed delivery
  • Connect either to the hosted remote endpoint or through a local stdio bridge package
When to use it
Useful when an assistant should trigger or debug webhook traffic for a project: firing test events, setting up endpoints and subscriptions, or checking why a delivery failed and replaying it.
Requirements
A Railhook project API key supplied as RAILHOOK_API_KEY (a READ_ONLY key is enough for read-only use). Remote clients connect to the hosted MCP endpoint; clients that only start local processes use the npm package, which needs Node.js 18 or later. Self-hosted setups set RAILHOOK_BASE_URL to their own origin.
Before you install
The API key is sent as a bearer token and grants access to the project it belongs to; a non-read-only key can create endpoints and subscriptions, send events and replay deliveries, which changes data and may trigger real webhook traffic to third parties. Use a READ_ONLY key when only inspection is needed.

Installation

In SourceWeft

  1. Open Railhook 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.vadymkykalo%2Frailhook/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": {
    "railhook": {
      "type": "http",
      "url": "https://railhook.io/mcp"
    }
  }
}

README

@railhook/mcp

[Wellknown]

A stdio bridge to Railhook's MCP server, for clients that only start local processes, such as Claude Desktop.

Clients that support remote servers (Claude Code, Cursor) should connect to https://railhook.io/mcp, or <your origin>/mcp when self-hosted, and skip this package. The bridge passes tools/list and tools/call through and has no tools of its own.

Use

Requires Node.js 18 or later.

json
{  "mcpServers": {    "railhook": {      "command": "npx",      "args": ["-y", "@railhook/mcp"],      "env": {        "RAILHOOK_API_KEY": "your-project-api-key"      }    }  }}
VariableRequiredMeaning
RAILHOOK_API_KEYyesA project API key. A READ_ONLY key allows the read tools and refuses every write.
RAILHOOK_BASE_URLnoDefault https://railhook.io. Set it to your origin when self-hosted.

The key is sent as Authorization: Bearer <key> and is never logged.

Tools: send_event, list_endpoints, create_endpoint, list_subscriptions, create_subscription, list_deliveries, get_delivery, replay_delivery. Each acts on the project the key belongs to.

Full guide: https://railhook.io/docs/tools/mcp/

Develop

bash
npm cinpm testnpm run build

License

MIT

Source: sdks/mcp/README.md at commit b552824

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

17
  1. v3.7.0LatestOct 8, 2026
  2. v3.6.0Oct 1, 2026
  3. v3.5.0Oct 1, 2026
  4. v3.3.0Sep 30, 2026
  5. v3.1.0Sep 30, 2026
  6. v3.0.0Sep 27, 2026
  7. v2.32.2Sep 27, 2026
  8. v2.32.0Sep 26, 2026
  9. v2.31.1Sep 25, 2026
  10. v2.30.2Sep 22, 2026
  11. v2.30.0Sep 21, 2026
  12. v2.29.0Sep 20, 2026
  13. v2.28.2Sep 20, 2026
  14. v2.28.0Sep 20, 2026
  15. v2.25.0Sep 19, 2026
  16. v2.24.0Sep 19, 2026
  17. v2.21.2Sep 18, 2026

Score

85% 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
  • License10 pts