How to Use the ESA Near Earth Objects MCP in VS Code Copilot

Q: How do we roll out ESA Near Earth Objects to our entire team in VS Code Copilot?

Commit a .vscode/mcp.json file containing the MCP server configuration to your Git repository. Every developer on your team using VS Code Copilot will automatically gain access to the asteroid tracking tools.

Q: Does VS Code Copilot write automated scripts to check the ESA Near Earth Objects API status?

Yes, Copilot calls checkesaneoccstatus to verify connection health and output the service URL. It uses this response to write automated monitoring scripts for your deployment pipeline.

Q: How do we query the entire catalog of known near-Earth asteroids?

Use getallnealist to fetch the complete designation index. Because this list contains thousands of entries, Copilot writes scripts to filter and paginate the results locally.

Connect VS Code Copilot to the ESA Near Earth Objects server for team-wide asteroid tracking.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect ESA Near Earth Objects MCP to VS Code Copilot

Create your Vinkius account to connect ESA Near Earth Objects to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup ESA Near Earth Objects with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Share planetary defense tools across your VS Code team

The `get_priority_list` tool identifies critical targets requiring immediate telescope follow-up directly within your shared workspace. By committing the configuration to your repo, every developer on your team can query unconfirmed orbital arcs. This shared MCP Server setup ensures your entire engineering team works with identical tracking tools. Copilot uses the live priority list to help developers write coordinated observation schedules.

Validate asteroid impact vectors inside Copilot Chat

The `get_impact_table` tool delivers raw impact probabilities and projected dates directly to your VS Code Copilot panel. Your team analyzes Palermo Scale values and Torino ratings during code reviews without leaving the editor. It combines this risk data with `get_recent_close_approaches` to compare historical flybys against predicted threats. Copilot formats these complex vectors into clean JSON or CSV structures for your database migrations.

Query physical properties for database seeding

The `get_object_physical_properties` tool pulls verified asteroid diameters, masses, and albedos directly into your VS Code terminal. Your team uses this real-world data to seed production databases with accurate astronomical profiles. Copilot reads this structural data to write database schemas and validation scripts. This MCP integration eliminates manual data entry and ensures your database tests use official ESA metrics.

Setup guide

Set up ESA Near Earth Objects MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the ESA Near Earth Objects MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the ESA Near Earth Objects tools listed. Try asking: "List my recent ESA Near Earth Objects transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "esa-near-earth-objects-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by ESA NEOCC. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect ESA Near Earth Objects now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about ESA Near Earth Objects MCP in VS Code Copilot

Commit a `.vscode/mcp.json` file containing the MCP server configuration to your Git repository. Every developer on your team using VS Code Copilot will automatically gain access to the asteroid tracking tools.

Yes, Copilot calls `check_esa_neocc_status` to verify connection health and output the service URL. It uses this response to write automated monitoring scripts for your deployment pipeline.

Yes, the server runs inside a SOC 2 compliant, zero-trust sandbox on Vinkius. It handles all authentication tokens centrally, so your team only needs a single MCP endpoint token to access the tools.

Use `get_all_nea_list` to fetch the complete designation index. Because this list contains thousands of entries, Copilot writes scripts to filter and paginate the results locally.

The server exclusively accesses public ESA asteroid designations, orbital elements, and physical properties. It never reads your proprietary code or workspace files, and all queries run in an ephemeral, isolated container that wipes its memory after each execution.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript