What is the habitable zone?

The habitable zone ('Goldilocks zone') is the range of distances from a star where liquid water could exist on a planet's surface — not too hot, not too cold. We filter for equilibrium temperatures between 200-320K and rocky sizes (< 2 Earth radii).

NASA Exoplanets — Worlds Beyond Our Solar System MCP Server for VS Code Copilot 4 tools — connect in under 2 minutes

Name: NASA Exoplanets — Worlds Beyond Our Solar System
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 4 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install NASA Exoplanets — Worlds Beyond Our Solar System and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "nasa-exoplanets-worlds-beyond-our-solar-system": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

NASA Exoplanets — Worlds Beyond Our Solar System

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About NASA Exoplanets — Worlds Beyond Our Solar System MCP Server

Direct SQL-like access to NASA's Exoplanet Archive — the world's most comprehensive database of confirmed planets beyond our solar system.

GitHub Copilot Agent mode brings NASA Exoplanets — Worlds Beyond Our Solar System data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 4 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Search Planets — By name, method, facility, year
Transit Planets — Kepler and TESS discoveries
Habitable Zone — Rocky planets where water could exist
Statistics — Totals, methods, trends

No API Key Required

The Exoplanet Archive TAP service is completely open.

The NASA Exoplanets — Worlds Beyond Our Solar System MCP Server exposes 4 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect NASA Exoplanets — Worlds Beyond Our Solar System to VS Code Copilot via MCP

Follow these steps to integrate the NASA Exoplanets — Worlds Beyond Our Solar System MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using NASA Exoplanets — Worlds Beyond Our Solar System

Ask Copilot: "Using NASA Exoplanets — Worlds Beyond Our Solar System, help me..." — 4 tools available

Why Use VS Code Copilot with the NASA Exoplanets — Worlds Beyond Our Solar System MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with NASA Exoplanets — Worlds Beyond Our Solar System through the Model Context Protocol.

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

NASA Exoplanets — Worlds Beyond Our Solar System + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the NASA Exoplanets — Worlds Beyond Our Solar System MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

NASA Exoplanets — Worlds Beyond Our Solar System MCP Tools for VS Code Copilot (4)

These 4 tools become available when you connect NASA Exoplanets — Worlds Beyond Our Solar System to VS Code Copilot via MCP:

get_habitable_zone

These are the most promising candidates for life. Get exoplanets in the habitable zone — where liquid water could exist

get_planet_stats

Shows how exoplanet science has exploded since Kepler's launch in 2009. Get global exoplanet discovery statistics: totals, methods, yearly trends

get_transit_planets

Transit is the most productive method (>75% of all discoveries). Kepler and TESS are the primary transit missions. Get exoplanets discovered via the transit method (Kepler/TESS)

query_confirmed_planets

Filter by planet name, discovery method (Transit, Radial Velocity, Imaging, Microlensing), discovery facility (Kepler, TESS, Keck), or year. Returns orbital period, radius, mass, equilibrium temperature. Search confirmed exoplanets by name, discovery method, facility, or year

Example Prompts for NASA Exoplanets — Worlds Beyond Our Solar System in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with NASA Exoplanets — Worlds Beyond Our Solar System immediately.

"How many exoplanets have been discovered?"

"Show me planets in the habitable zone"

Troubleshooting NASA Exoplanets — Worlds Beyond Our Solar System MCP Server with VS Code Copilot

Common issues when connecting NASA Exoplanets — Worlds Beyond Our Solar System to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

NASA Exoplanets — Worlds Beyond Our Solar System + VS Code Copilot FAQ

Common questions about integrating NASA Exoplanets — Worlds Beyond Our Solar System MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.