Files

42 lines
1.3 KiB
YAML

# Nous-approved MCP catalog entry.
# Presence in this directory = approval. Merged via PR review.
manifest_version: 1
name: railway
description: 'Railway: projects, services, deployments, and environments.'
source: https://docs.railway.com/guides/mcp-server
# Official vendor-hosted remote MCP (URL-only — Hermes never spawns a local
# process for this entry). Native OAuth 2.1 + Dynamic Client Registration
# (verified live: RFC 9728 protected-resource metadata -> AS metadata with
# registration_endpoint); Hermes's MCP client + mcp_oauth_manager handle
# discovery, PKCE, token exchange, and refresh.
transport:
type: http
url: https://mcp.railway.com
auth:
type: oauth
# Excluded: railway-agent hands the request to Railway's server-side AI
# agent for multi-step infra operations — an opaque delegation meta-layer
# that acts outside Hermes's per-tool approval loop. The remaining tools
# are direct (and destructive ones carry vendor destructive-hints).
tools:
default_excluded:
- railway-agent
# Composer-suggestion triggers (desktop brand pills).
suggest:
keywords:
- railway
- railway deploy
hosts:
- railway.com
- railway.app
post_install: |
On first connection Hermes opens a browser to authorize with
Railway (or run `hermes mcp login railway`). Approve access,
then restart the session so tools load.