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
    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.

    Figma MCP server

    Figma MCP server

    The Figma MCP server enables design context delivery from Figma files to AI agents and code editors, empowering teams to generate code directly from design selections. It supports both a remote hosted server and a locally hosted desktop server, allowing seamless integration with popular editors through Code Connect and a suite of tools that extract design context, metadata, variables, and more. This guide covers enabling the MCP server, configuring clients (VS Code, Cursor, Claude Code, and others), and using a curated set of MCP tools to fetch structured design data for faster, more accurate code generation. It also explains best practices, prompts, and integration workflows that help teams align generated output with their design systems. The documentation includes concrete JSON examples for configuring servers in editors like VS Code and Cursor, as well as command examples for Claude Code integration and plugin installation.

    MarkItDown MCP

    MarkItDown MCP

    MarkItDown-MCP is a lightweight MCP (Model Context Protocol) server provided as the markitdown-mcp package. It exposes a STDIO, Streamable HTTP, and SSE MCP server designed for calling MarkItDown to convert content to Markdown. The package focuses on simplicity and accessibility, enabling you to run the MCP server locally via a simple CLI, or in Docker for containerized workflows, with integration options for Claude Desktop. The core capability is exposed through a single tool, convert_to_markdown(uri), which accepts a URI in http:, https:, file:, or data: schemes to fetch content and convert it to Markdown. This MCP server is easy to install with pip and can be used in various transport modes, including STDIO and HTTP/SSE, making it a flexible choice for automations and integrations.

    Chrome MCP Server

    Chrome MCP Server

    Chrome MCP Server is a Chrome extension-based Model Context Protocol (MCP) server that exposes your Chrome browser functionality to AI assistants like Claude, enabling complex browser automation, content analysis, and semantic search. It leverages your existing Chrome environment, including login states and configurations, to allow large language models and chatbots to control the browser natively without needing to launch a separate automation process. The project emphasizes privacy by remaining fully local and offers capabilities such as cross-tab context, streamable HTTP communication, and a built-in vector database for semantic search and content analysis. As an early-stage project, it includes a growing set of tools for browser control, inspection, and automation, with ongoing development to broaden compatibility and features.

    MCP server for Appwrite docs

    MCP server for Appwrite docs

    The MCP server for Appwrite docs enables LLMs and code-generation tools to interact with comprehensive Appwrite documentation. It empowers AI assistants to access up-to-date API references, SDK guides, and implementation examples, facilitating intelligent code generation, troubleshooting, and best-practice guidance directly from the official docs. This MCP brings real-time context, semantic search, and seamless integration with popular editors and IDEs to accelerate development workflows around Appwrite's APIs and SDKs.