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.

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.

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.

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 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 <comma-separated-required-scopes> with the scopes specified by the server, rather than assuming a broad default grant.

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.

In a client that supports remote Streamable HTTP MCP, add https://railyai.com/mcp and complete its browser OAuth flow when supported. Claude Code/Desktop and Grok Bot UI are not certified by this bundle release. Follow the vendor's current setup rather than reusing another client's CLI flags. Manage/revoke Raily access at Integrations. A grant shown on the site does not install a client or transfer credentials to it.

If the client can only spawn a local stdio MCP process, use the existing mcp-remote bridge. Do not publish or install a first-party Raily CLI for this:

{
  "mcpServers": {
    "raily": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://railyai.com/mcp"]
    }
  }
}

Complete the browser OAuth flow that mcp-remote opens. A branded npx railyai wrapper would call the same command.

Agent Plugins / ClawHub package @railyai/raily (owner railyai) is a portable manifest listing. It is not required to reach the hosted MCP:

openclaw plugins install clawhub:@railyai/raily

Cursor Marketplace, official MCP Registry and npm are separate channels. See PUBLISHING.md.

The Raily server's isolated 2026-09-21 certification exercised official Grok 1.0.34, Codex 0.154.0 and Cursor Agent 2026.08.11-e8db854 (composer-2.5), including native settings write/read-back, replay/conflict, scope refusal and revocation. This describes that recorded server/client wave, not every future client version or installation of this bundle. Grok doctor exposes a count, not all tool names; Codex JSON does not expose its complete negotiated catalog. Claude was excluded. Later runner assertions received hermetic coverage without a new native wave.

Node.js 22 or later is needed only for repository validation, not to use the remote server. The bundle has no JS runtime or dependencies. Stdio clients that run mcp-remote pull that tool from npm on demand.

npm run catalog:sync   # refresh generated catalog from the live canonical registry mirror
npm run check          # offline manifest/version/catalog checks
npm run catalog:check  # fail if the server catalog has changed
mcp-publisher validate server.json
npm pack --dry-run

Release all manifest versions together. CHANGELOG.md records the bundle changes; the server remains independently deployed at the stable endpoint.