Stellar Raven

Remote MCP server on Cloudflare Workers exposing two tools, search and execute, over a
unified catalog of Stellar ecosystem services and skills. Agents use search to discover
capabilities, then call execute with JavaScript that runs in a Dynamic Worker isolate with no
network access; service calls go through host-side adapters. The server instructions also include
a generated source-family micro-map so agents can plan which catalog family should ground a
question before searching.

Design: PLAN.md. Code-verified mechanics and operating limits:
ARCHITECTURE.md.

Deployed as the Cloudflare worker stellar-raven-codemode at https://raven.stellar.buzz — the
worker/service name deliberately keeps the codemode suffix even though the repo is stellar-raven.

Quickstart

Server URL:   https://raven.stellar.buzz        (live since 2026-07-02; alias: https://agents.stellar.buzz still works)
MCP endpoint: POST https://raven.stellar.buzz/mcp   (streamable HTTP)  # or https://agents.stellar.buzz/mcp
Health:       GET  /health

Local dev: use Node 24, run npm ci, populate .dev.vars, then npm run dev and point a client at
http://localhost:8787/mcp. Note: wrangler dev does NOT hot-reload .dev.vars edits —
restart it after changing them.

Connect

Add https://raven.stellar.buzz/mcp in an MCP client that supports streamable HTTP and OAuth
(Claude, Cursor, or any compatible client). The Worker is its own OAuth authorization server and
hands sign-in to WorkOS AuthKit; clients should discover and complete that flow automatically.

Operational auth details live in ARCHITECTURE.md and
research/auth-workos.md. Vulnerability reporting and researcher
scope live in SECURITY.md.

Development

# use Node 24, matching CI
npm ci
npm run typecheck  # tsc
npm test           # vitest (offline; auth suite in test/auth.test.ts)
npm run typegen    # regenerate env.d.ts after wrangler.jsonc/.dev.vars changes

For local MCP testing, populate .dev.vars, run npm run dev, and point a client at
http://localhost:8787/mcp. Restart wrangler dev after editing .dev.vars.

Observability

Structured JSON events (src/observability.ts) land in Workers Logs; traces are enabled with a
custom codemode.execute span around each sandbox run (the Worker Loader isolate is not
auto-instrumented). Both are queryable in the dash (Workers & Pages → Observability) or via the
telemetry query API. Survey of the whole surface — pricing, query API, OTel export, GraphQL
metrics: research/observability-cloudflare.md.

For cap/rate-limit reviews, start with ARCHITECTURE.md §7:
it lists the shared execute sandbox limits, demo-only chat limits, MCP-only artifact/auth limits,
and the log event names to query.

License

Apache-2.0 © 2026 Tyler van der Hoeven — except vendored third-party content
(the ecosystem-skills/skills/<source>/ mirrors and src/catalog/vendor/), which retains its
upstream licenses: see THIRD-PARTY-NOTICES.md. Notably, the
openzeppelin-stellar skills subtree is AGPL-3.0.