Raily MCP server

Raily MCP

Connect your Raily personal agent through the hosted endpoint https://railyai.com/mcp (Streamable HTTP). The server runs there; this repository is metadata (tool catalog, plugin manifests, registry server.json). There is no first-party npx raily / npx railyai runtime.

Capabilities and permissions

The current server exposes 47 registered tools: status, Brief, match cards and contacts, Memory, Focus, settings, matching controls, and analysis/top-up handoffs. See the generated complete tool catalog, the API guide and live agent guide.

Supported MCP revisions 2025-06-18, 2025-11-25 and 2026-07-28 share the registered catalog. Discovery is not permission: each call requires its corresponding scope, supported credential type and enabled server capability. The default personal key from Keys currently has agent:read only; it does not authorize every listed read or write. Use browser OAuth consent/step-up for additional supported scopes.

Actions can change your data. Ask the agent for the intended action explicitly; it must follow the server's approval and idempotency contracts. Paid actions and Memory reset require their first-party approval flows. A top-up/analysis link opens a first-party flow; it is not proof of payment or completed analysis.

Connect directly

Use the official vendor client. Verify its executable provenance and version; third-party grok-dev is not official xAI Grok. Authentication to the LLM provider and authorization to Raily are separate. Never paste tokens into chat, commit credentials, or put bearer values on a command line. Keep them in a supported credential store or owner-only environment file. Never reset Keychain for setup.

Cursor Agent

Merge the URL-only entry from cursor-mcp.example.json into your project .cursor/mcp.json or private ~/.cursor/mcp.json, preserving other servers. Then use the official cursor-agent, not the editor launcher:

cursor-agent mcp enable raily
cursor-agent mcp login raily
cursor-agent mcp list-tools raily

Complete browser consent. Portable plugin mcp.json uses streamable-http; Cursor Agent's native config uses the URL-only example. Do not copy one format into the other. Installation in a marketplace is not authentication.

Codex CLI

codex mcp add raily --url https://railyai.com/mcp
codex mcp login raily
codex mcp list

Complete browser consent. When a requested action needs additional scopes, use codex mcp login raily --scopes with the scopes specified by the server, rather than assuming a broad default grant.

Official xAI Grok

On the certified Mac install the official executable was ~/.grok/bin/grok. Check your actual vendor installation, then configure the direct HTTP transport:

grok mcp add --transport http raily https://railyai.com/mcp
grok mcp doctor raily --json

These commands configure/check the connection; they do not themselves guarantee OAuth completion. If authentication is required, complete the client's supported auth flow or configure its private environment-backed bearer header. The certified Grok run used a separately provisioned Raily credential; do not infer browser OAuth or Grok Bot marketplace acceptance from that result. Never put a literal bearer secret in --header arguments or shared project configuration.

Other HTTP clients

Shortened. The full README is on GitHub.