IO Aerospace MCP Server Details

IO Aerospace MCP Server is a production-ready Model Context Protocol (MCP) server designed for aerospace and astrodynamics calculations. It exposes a rich set of tools for celestial body ephemeris, orbital mechanics, DSN ground station operations, solar system object properties, and comprehensive unit and time system conversions. Built on the IO Aerospace Astrodynamics framework, this server delivers core algorithms for ephemerides, geometry, and time systems, enabling developers to integrate advanced aerospace calculations into local or hosted deployments. The project supports both modern streamable-HTTP transport and legacy SSE/STDIO configurations, with self-hosting options via Docker or native .NET deployments for flexible integration into existing ecosystems.

Use Case

This MCP server provides a comprehensive suite of tools for aerospace missions and research. Users can query ephemerides, transform between reference frames, perform orbital element conversions, and compute coordinates for ground stations and deep-space networks. The server is designed to be consumed by MCP clients (e.g., Node.js SDKs or Claude Desktop) via streamable-HTTP or STDIO transports. Example usage with a hosted server includes listing available tools and calling a tool by name. For local development, you can run the STDIO server or the HTTP transport server and connect with a client. Key code snippets from the documentation illustrate how to connect to the hosted server and how to configure clients to use either STDIO or HTTP transports.

Code examples from the docs:

  • SSE example (legacy):

  • // Only use this if you have an old client that requires SSE
    const eventSource = new EventSource('https://mcp.io-aerospace.org/sse');

    eventSource.onmessage = (event) => {
    console.log('message', event.data);
    };

    eventSource.onerror = (err) => {
    console.error('sse error', err);
    };


  • Node.js MCP client (streamable-HTTP) example:

  • import { Client } from "@modelcontextprotocol/sdk/client/index.js";
    import { HttpClientTransport } from "@modelcontextprotocol/sdk/client/transport/http.js";

    // Modern streamable-HTTP transport (recommended)
    const transport = new HttpClientTransport(new URL("https://mcp.io-aerospace.org"));
    const client = new Client(
    { name: "example-client", version: "1.0.0" },
    { capabilities: { tools: {}, prompts: {}, resources: {} } },
    transport
    );

    await client.connect();
    const tools = await client.listTools();
    console.log("Tools:", tools);

    // Example: call a tool
    // const result = await client.callTool({ name: "GetEphemerisAsStateVectors", arguments: { /<em> ... </em>/ } });
    // console.log(result);


  • Claude Desktop STDIO configuration (example):

  • {
    "mcpServers": {
    "astrodynamics": {
    "command": "/path/to/Server.Stdio",
    "args": ["-k", "/path/to/kernels"]
    }
    }
    }

  • Claude Desktop STDIO with environment variable:

  • {
    "mcpServers": {
    "astrodynamics": {
    "command": "/path/to/Server.Stdio",
    "args": [],
    "env": {
    "IO_DATA_DIR": "/path/to/kernels"
    }
    }
    }
    }

  • Claude Desktop HTTP transport to hosted server:

  • {
    "mcpServers": {
    "astrodynamics": {
    "transport": {
    "type": "http",
    "url": "https://mcp.io-aerospace.org"
    }
    }
    }
    }

    Available Tools (37)

    Examples & Tutorials

    Real example usage patterns from the documentation:

  • SSE example (legacy):

  • // Only use this if you have an old client that requires SSE
    const eventSource = new EventSource('https://mcp.io-aerospace.org/sse');

    eventSource.onmessage = (event) => {
    console.log('message', event.data);
    };

    eventSource.onerror = (err) => {
    console.error('sse error', err);
    };


  • Node.js MCP client (streamable-HTTP) example:

  • import { Client } from "@modelcontextprotocol/sdk/client/index.js";
    import { HttpClientTransport } from "@modelcontextprotocol/sdk/client/transport/http.js";

    // Modern streamable-HTTP transport (recommended)
    const transport = new HttpClientTransport(new URL("https://mcp.io-aerospace.org"));
    const client = new Client(
    { name: "example-client", version: "1.0.0" },
    { capabilities: { tools: {}, prompts: {}, resources: {} } },
    transport
    );

    await client.connect();
    const tools = await client.listTools();
    console.log("Tools:", tools);

    // Example: call a tool
    // const result = await client.callTool({ name: "GetEphemerisAsStateVectors", arguments: { /<em> ... </em>/ } });
    // console.log(result);


  • Claude Desktop STDIO configuration (STDIO):

  • {
    "mcpServers": {
    "astrodynamics": {
    "command": "/path/to/Server.Stdio",
    "args": ["-k", "/path/to/kernels"]
    }
    }
    }

  • Claude Desktop STDIO configuration (ENV):

  • {
    "mcpServers": {
    "astrodynamics": {
    "command": "/path/to/Server.Stdio",
    "args": [],
    "env": {
    "IO_DATA_DIR": "/path/to/kernels"
    }
    }
    }
    }

  • Claude Desktop HTTP transport to hosted server:

  • {
    "mcpServers": {
    "astrodynamics": {
    "transport": {
    "type": "http",
    "url": "https://mcp.io-aerospace.org"
    }
    }
    }
    }

    Installation Guide

    Step-by-step installation instructions with actual commands from the documentation:

  • Docker Development:

  • git clone https://github.com/IO-Aerospace-software-engineering/mcp-server
    cd mcp-server
    docker-compose up

    The HTTP server will be available at http://localhost:8080.
  • Production (Docker):

  • Copy docker-compose.prod.example.yml to docker-compose.prod.yml

  • Update the domain names in the production file

  • Ensure kernel data exists at ./data/solarsystem/

  • Deploy using the automated script:

  • ./deploy-production.sh

  • Native .NET Deployment:

  • Clone and Build:

  • git clone https://github.com/IO-Aerospace-software-engineering/mcp-server
    cd mcp-server
    dotnet build

  • Solar System Data Setup (STDIO):

  • ./Server.Stdio -k /path/to/kernels

  • Transport selection and HTTP server:

  • cd Server.Http
    dotnet run
    <h1 class="text-2xl font-semibold mt-5 mb-3">Server available at http://localhost:8080</h1>

    Integration Guides

    Frequently Asked Questions

    Is this your MCP?

    Claim ownership and get verified badge

    Repository Stats

    Sponsored

    Ad Space Available
    Important Notes

    Notes:

  • Modern MCP clients should use the base URL with streamable-HTTP transport. The SSE endpoint is legacy and kept for backward compatibility with older clients.

  • Self-hosting is optional; Docker and native .NET deployment are supported. Ensure SPICE kernels are available at the configured data path.

  • If you need to use the STDIO transport, provide the kernels path via CLI (-k) or IO_DATA_DIR environment variable.
  • Prerequisites

    Requirements before using this MCP (Node.js version, API keys, etc.) - from the docs: .NET 9.0 SDK or runtime; Docker (for containerized deployment); Solar system kernels data (SPICE kernels).

    Details
    Last Updated1/1/2026
    SourceGitHub

    Compare Alternatives

    Similar MCP Tools

    9 related tools
    Graphiti MCP Server

    Graphiti MCP Server

    Graphiti MCP Server is an experimental implementation that exposes Graphiti's real-time, temporally-aware knowledge graph capabilities through the MCP (Model Context Protocol) interface. It enables AI agents and MCP clients to interact with Graphiti's knowledge graph for structured extraction, reasoning, and memory across conversations, documents, and enterprise data. The server supports multiple backends (FalkorDB by default and Neo4j), a variety of LLM providers (OpenAI, Anthropic, Gemini, Groq, Azure OpenAI), and multiple embedder options, all accessible via an HTTP MCP endpoint at /mcp/ for broad client compatibility. It also includes queue-based asynchronous episode processing, rich entity types for structured data, and flexible configuration through config.yaml, environment variables, or CLI arguments.

    Context7 MCP Server

    Context7 MCP Server

    Context7 MCP Server delivers up-to-date, code-first documentation and examples for LLMs and AI code editors by pulling content directly from the source. It supports multiple MCP clients and exposes tools that help you resolve library IDs and retrieve library documentation, ensuring prompts use current APIs and usage patterns. The repository provides installation and integration guides for Cursor, Claude Code, Opencode, and other clients, along with practical configuration samples and OAuth options for remote HTTP connections. This MCP server is designed to keep prompts in sync with the latest library docs, reducing hallucinations and outdated code snippets.

    TrendRadar MCP

    TrendRadar MCP

    TrendRadar MCP is an AI-driven Model Context Protocol (MCP) based analysis server that exposes a suite of specialized tools for cross-platform news analysis, trend tracking, and intelligent push notifications. It integrates with TrendRadar’s multi-platform data aggregation (RSS and trending topics) and provides advanced AI-powered insights, sentiment analysis, and cross-platform correlation. The MCP server enables developers to query, analyze, and compare news across platforms using a consistent toolset, with ongoing updates that expand capabilities such as RSS querying, date parsing, and multi-date trend analysis. This documentation references the MCP module updates, tool additions, and architecture changes that enhance extensibility, cross-platform data handling, and AI-assisted reporting.

    ChainAware Behavioural Prediction MCP

    ChainAware Behavioural Prediction MCP

    The ChainAware Behavioural Prediction MCP is an MCP-based server that provides AI-powered tools to analyze wallet behaviour prediction, fraud detection, and rug pull prediction. Designed for Web3 security and DeFi analytics, it enables developers and platforms to integrate risk assessment, predictive wallet behavior insights, and rug-pull detection through MCP-compatible clients. The server exposes three specialized tools and uses Server-Sent Events (SSE) for real-time responses, helping safeguard DeFi users, monitor liquidity risks, and score wallet or contract trustworthiness. Access to production endpoints is API-key gated, reflecting a private backend architecture that supports secure, scalable risk analytics across wallets, contracts, and pools.

    Playwright MCP

    Playwright MCP

    Playwright MCP server. A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright. This server enables large language models (LLMs) to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or visually-tuned models. The server is designed to be fast, lightweight, and deterministic, offering LLM-friendly tooling and a rich set of browser automation capabilities via MCP tools. It supports standalone operation, containerized deployments, and integration with a variety of MCP clients (Claude Desktop, VS Code, Copilot, Cursor, Goose, Windsurf, and others).

    Sequential Thinking MCP Server

    Sequential Thinking MCP Server

    Sequential Thinking MCP Server provides a dedicated MCP tool that guides problem-solving through a structured, step-by-step thinking process. It supports dynamic adjustment of the number of thoughts and allows revision and branching within a controlled workflow, making it ideal for complex analysis and solution hypothesis development. This server is designed to register a single tool, sequential_thinking, and is integrated with common MCP deployment methods (NPX, Docker) as well as editor integrations like Claude Desktop and VS Code for quick setup. The documentation provides exact configuration snippets, usage patterns, and building instructions to help you deploy and use the MCP server effectively, including Codex CLI, NPX, and Docker installation examples.

    N8N MCP Server

    N8N MCP Server

    An MCP (Model Context Protocol) server designed to integrate Claude Desktop, Claude Code, Windsurf, and Cursor with n8n workflows. This MCP enables users to build, test, and orchestrate complex workflows by exposing a set of tools that bridge Claude’s capabilities with n8n’s automation platform. The project emphasizes robust trigger handling, multi-tenant readiness, and progressive documentation to help developers understand how tools map to real-world workflow tasks. It also outlines future tooling integration points (such as getNodeEssentials and getNodeInfo) to further enhance node-structure awareness within MCP-powered automations.

    Hugging Face MCP Server

    Hugging Face MCP Server

    Hugging Face Official MCP Server connects your large language models (LLMs) to the Hugging Face Hub and thousands of Gradio AI Applications, enabling seamless MCP (Model Context Protocol) integration across multiple transports. It supports STDIO, SSE (to be deprecated but still commonly deployed), StreamableHTTP, and StreamableHTTPJson, with the Web Application allowing dynamic tool management and status updates. This MCP server is designed to be run locally or in Docker, and it provides integrations with Claude Desktop, Claude Code, Gemini CLI (and its extension), VSCode, and Cursor, making it easy to configure and manage MCP-enabled tools and endpoints. Tools such as hf_doc_search and hf_doc_fetch can be enabled to enhance document discovery, and an optional Authenticate tool can be included to handle OAuth challenges when called.

    Shadcn UI MCP Server v4

    Shadcn UI MCP Server v4

    Shadcn UI v4 MCP Server is an advanced MCP (Model Context Protocol) server designed to give AI assistants comprehensive access to shadcn/ui v4 components, blocks, demos, and metadata. It enables multi-framework support (React, Svelte, Vue, and React Native) with fast, cache-friendly access to component source code, demos, and directory structures, empowering AI-driven development workflows. The project emphasizes production-readiness with Docker Compose, SSE transport for multi-client deployments, and smart caching to optimize GitHub API usage while providing rich metadata and usage patterns for rapid prototyping and learning across frameworks.