Cassini Mission Plan MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Cassini Mission Plan MCPlist activities in 2005"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Cassini Mission Plan MCP
A read-only Model Context Protocol server over the Cassini-Huygens mission dataset (~62k activity rows). Built as an AI workshop demo: clean, readable TypeScript that runs live in Claude Desktop.
Live endpoint: https://cassini-mission-plan.redfour.workers.dev
What it does
Exposes 7 MCP tools so an LLM client can query the Cassini master_plan table:
Tool | What it answers |
| Filtered, paginated rows (date range, team, target) |
| Single row by id |
| FTS5 full-text search over title + description |
| Row count matching the same filters as list |
| Group-by counts (team / target / spass_type) |
| Bucketed counts over a date range (year or month) — zero-filled |
| Distinct values of team / target / spass_type |
Related MCP server: telemetry-mcp
Architecture
Runtime: Cloudflare Workers (TypeScript)
Data: Cloudflare D1 (SQLite) —
master_plantable + FTS5 virtual tableTransport: hand-rolled MCP-over-HTTP (JSON-RPC 2.0 over plain HTTP POST)
Validation: zod schemas per tool; errors surface as JSON-RPC error objects
See docs/ARCHITECTURE.md for the full design.
Project setup
npm installRun tests
npm test # Jest — all specs against in-memory SQLiteThe deploy spec (spec/deploy-and-initialize.spec.ts) needs a live URL:
DEPLOY_URL=https://cassini-mission-plan.redfour.workers.dev npm testDeploy (one-time setup)
Create the D1 database:
npx wrangler d1 create cassiniCopy the
database_idintowrangler.toml.Import the data (generates
data/cassini.d1.sqlfromdata/cassini.db):node scripts/import.js # or: npx ts-node scripts/import.ts npx wrangler d1 execute cassini --remote --file=data/cassini.d1.sqlDeploy:
npm run deploy
Local dev
npm run dev # wrangler dev (uses local D1)Docs
File | What's in it |
| Problem, audience, goals, scope |
| Components, data model, key decisions |
| Tool API reference + functional/non-functional requirements |
| User stories (source for the spec suite) |
| Build task checklist (all complete) |
| Decision log maintained with Claude Code |
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for aerospace calculations: orbital mechanics, ephemeris, DSN operations, ...
Read-only MCP server for The Quiet Protocol's engines, benchmarks, proof, and business data.
Bureau-operated public read-only MCP service for public Context Packets and Cases.
OAuth-protected, read-only-by-default MCP server for provenance-labeled QuillCaddie project memory.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceMCP server that wraps the NASA Space-Track API to provide tools for TLE lookup, conjunction query, and satellite catalog search.-
- AlicenseNot gradedqualityAmaintenanceA read-only MCP server for querying telemetry data from configurable backends. Provides tools to list sources, describe schemas, run bounded queries, and compute aggregates.MIT
- AlicenseNot gradedqualityDmaintenanceEnables querying of the Cassini-Huygens mission dataset with tools for listing, searching, counting, aggregating, and browsing activities.MIT

spedas-mcpofficial
AlicenseBqualityBmaintenanceUnified SPEDAS-oriented MCP server for Claude Code and Codex agents, providing tools to discover and fetch heliophysics and planetary science data from CDAWeb, NASA PDS, and SPICE kernels.213MIT