R

MCP Entry

Railway MCP Server

Railway documents a Model Context Protocol server at docs.railway.com/ai/mcp-server with local stdio mode via `railway mcp` in the Railway CLI and a remote hosted endpoint at `https://mcp.railway.com` authenticated through OAuth. `railway mcp install` merges configs into Cursor, Claude Code, VS Code, Codex, and other supported clients; `--remote` switches to the HTTP server. Local tools documented include `check-railway-status`, `list-projects`, `create-project-and-link`, `deploy`, `deploy-template`, `list-variables`, `set-variables`, `generate-domain`, and `get-logs`; remote tools add `whoami`, `redeploy`, `accept-deploy`, and `railway-agent` for multi-step debugging per the MCP reference. Railway notes destructive actions use confirmation guards and that the deprecated npm `@railway/mcp-server` package now delegates to `railway mcp`.

Category Developer Tools
Install railway mcp install
Runtime Railway CLI / Hosted HTTP MCP
railwaydeploymentpaas

Use cases

  • Ask Cursor to `deploy-template` Postgres for a feature branch
  • Pull Railway variables into a local `.env` via MCP tools
  • Use remote `railway-agent` to debug failing production deploy logs
  • Generate domains and redeploy API services from natural-language prompts
  • Prefer local stdio MCP when sharing the CLI's linked project context

Key features

  • Cursor
  • Claude Desktop
  • Claude Code
  • VS Code
  • Codex
  • Windsurf

Frequently Asked Questions

Should I use local or remote Railway MCP?
Railway docs recommend local stdio (`railway mcp`) for coding-agent workflows sharing CLI auth; remote `mcp.railway.com` suits OAuth-only setups.
Is `npx @railway/mcp-server` still supported?
The npm package is a deprecated shim that launches `railway mcp`—migrate to CLI per docs.railway.com/cli/mcp.
Which destructive tools need extra care?
Docs flag `redeploy`, `accept-deploy`, and remote `railway-agent`; review LLM-proposed actions before approving.

Related

Related

3 Indexed items

PostHog MCP Server

Monitoring

PostHog documents a free hosted Model Context Protocol endpoint at `https://mcp.posthog.com/mcp` per posthog.com/docs/model-context-protocol that lets MCP clients query analytics, manage feature flags, investigate errors, run HogQL, triage support workflows, and configure CDP destinations from natural-language prompts. The PostHog Wizard installs the server into Cursor, Claude Code, Claude Desktop, Codex, VS Code, Windsurf, and Zed via `npx @posthog/wizard@latest mcp add`. Authentication routes to the correct US or EU data region; manual setups can pass a personal API key with the MCP Server preset through `mcp-remote` and an `Authorization` Bearer header. Source lives in the PostHog monorepo at `services/mcp` (the standalone PostHog/mcp repository redirects there).

Datadog MCP Server

Monitoring

Datadog documents a remote Model Context Protocol server at docs.datadoghq.com/bits_ai/mcp_server that connects AI agents in Cursor, Claude Code, Codex CLI, VS Code, Gemini CLI, and other MCP clients to observability data across APM, logs, metrics, monitors, dashboards, and security signals. Setup guides describe OAuth-based connection to Datadog's hosted MCP endpoint (distinct from the local-only Code Security MCP Server used for SAST/SCA scans). Fair-use limits listed in docs include 50 requests per 10 seconds burst and 50,000 monthly tool calls; Audit Trail records MCP actions with tool name, arguments, user identity, and client, while metrics `datadog.mcp.session.starts` and `datadog.mcp.tool.usage` tag usage by client and tool.

PlanetScale MCP Server

Database

PlanetScale documents a hosted Model Context Protocol server at planetscale.com/docs/connect/mcp, reachable at `https://mcp.pscale.dev/mcp/planetscale` with OAuth authentication for organizations, databases, branches, schemas, and Insights data. An insights-only endpoint at `https://mcp.pscale.dev/mcp/planetscale-insights-only` omits read/write query tools. Tools documented include organization/database/branch listing, schema inspection, `planetscale_get_insights`, documentation search, and—when scopes allow—`planetscale_execute_read_query` and `planetscale_execute_write_query` with replica routing, ephemeral credentials, and destructive-query safeguards per the January 2026 changelog. PlanetScale notes the older local CLI MCP path is deprecated in favor of the hosted HTTP server for Cursor, Claude Code, and other MCP clients.