Stellar Ravencodemode

Remote MCP server live

Stellar Raven

Stellar docs and ecosystem context, one connection. Raven gives your AI agent the official docs, live ecosystem data, community intel, and proven playbooks — and cross-references them into answers no single source can give. No service API keys. Paste the endpoint, sign in, ask.

Connect your agent raven.stellar.org/mcp
terminal
# add the remote server over HTTP, then authorize
claude mcp add --transport http stellar-raven \
  "https://raven.stellar.org/mcp"
# run /mcp -> Authenticate -> sign in in your browser
terminal
# add the streamable-HTTP server, then log in
codex mcp add stellar-raven --url "https://raven.stellar.org/mcp"
codex mcp login stellar-raven  # opens your browser
~/.cursor/mcp.json
// ~/.cursor/mcp.json  (or .cursor/mcp.json per project)
{
  "mcpServers": {
    "stellar-raven": { "url": "https://raven.stellar.org/mcp" }
  }
}
// Cursor runs the OAuth sign-in on first use
Settings -> Connectors
# Settings -> Connectors -> Add custom connector
# paste the endpoint:
https://raven.stellar.org/mcp
# approve the browser sign-in — that's it
terminal
# add via the CLI (or .vscode/mcp.json)
code --add-mcp '{"name":"stellar-raven","type":"http","url":"https://raven.stellar.org/mcp"}'
mcp.json
# no native remote/OAuth support? bridge with mcp-remote
{
  "mcpServers": {
    "stellar-raven": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://raven.stellar.org/mcp", "--transport", "http-only"]
    }
  }
}
No service API keys — one browser sign-in Sandboxed — agent code runs with no network Low upkeep — checked against live services daily
54 live operations 276 catalog entries 18 playbooks 1 sign-in 0 API keys

Under one roof

Finally, Stellar context in one place.

Wired up separately, this is a stack of servers, API keys, and upkeep. Raven bundles it behind one endpoint — and keeps the catalog checked against live services.

Official docs

The source of truth, ranked for agents

Official Stellar developer docs, searched the way agents actually ask.

smart contractsSDKsRPC & HorizonSEPs & standards
Live ecosystem data

Current and graded, not training-data stale

Curated intelligence on who is building what across the network — refreshed from the live services.

920+ projects2,300+ graded reposbuilders & partnersresearch corpus
Community intel

What the ecosystem is shipping and funding

News, media, and money flows — the context your agent can't get from docs alone.

news & researchpodcasts & videoevents & jobsgovernance & SCF
Proven playbooks

Tested procedures, read mid-task

Eighteen step-by-step guides your agent pulls in section by section, exactly when it needs them.

smart contractspaymentsdAppsdata & indexing

Why a gateway

One install replaces the pile.

The point isn't fewer tabs — it's a smarter agent. When every source lives in one catalog, Raven can answer the questions that fall between services.

Wiring it yourself

  • A separate MCP server for every service
  • API keys to obtain, store, and rotate
  • Dozens of tool schemas crowding the context window
  • One source per question — you do the cross-referencing
  • Breaks quietly whenever any service changes

Pointing at Raven

  • One endpoint, one browser sign-in
  • No keys — secrets stay server-side, out of your agent's reach
  • Two lean tools that leave the context window to your work
  • One answer composed from several sources at once
  • Checked daily against the live services

Under the hood: two MCP tools. search ranks 276 catalog entries — operations, docs, and skill sections; execute runs your agent's JavaScript in a no-network sandbox where every call is validated against the catalog.

Two minutes from paste to expert. Connect your agent Try the playground