How to Use the ESA Near Earth Objects MCP in CrewAI

Q: How do I give my CrewAI agents access to the ESA Near Earth Objects MCP tools?

Install crewaitools. For basic access, add the server URL to the mcps array in your agent definition. The agent will automatically discover tools like getprioritylist.

Q: Can I restrict which ESA Near Earth Objects MCP tools a specific CrewAI agent uses?

Yes. Import the HTTP transport from crewai.mcp and apply a toolfilter. You can allow your orbital agent to use getobjectephemerides while blocking it from accessing the risk lists.

Q: How does CrewAI handle large datasets from the ESA Near Earth Objects catalog?

Tools like getallnealist return thousands of entries. Your research agent processes this raw output and stores only the relevant designations in the crew's shared memory for other agents to analyze.

Q: What happens if an agent fails to fetch orbital elements?

CrewAI agents are autonomous. If getobjectorbitalelements returns an error, the agent will read the failure message, adjust its parameters, and attempt the call again without crashing the entire crew.

Deploy an autonomous CrewAI team to monitor, analyze, and escalate asteroid threats using the ESA Near Earth Objects MCP server.

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 CrewAI

Create your Vinkius account to connect ESA Near Earth Objects to CrewAI 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 CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Coordinate Asteroid Threat Teams

`get_all_nea_list` hands your CrewAI research agent the complete catalog of known near-Earth asteroids. You don't just run one prompt. You assign a tracker agent to pull designations, while an analyst agent evaluates the data. Look, planetary defense requires specialization. The researcher grabs the raw catalog. It passes specific designations to the orbital dynamics agent, which then runs `get_object_orbital_elements` to compute the actual trajectory. The shared memory keeps the context intact across the entire crew.

Automate Close Approach Tracking

`get_object_close_approaches` retrieves the miss distance, date, velocity, and brightness for specific encounters. You can configure a CrewAI monitor agent to run this tool continuously for high-interest targets like Apophis. If the monitor finds a concerning velocity vector, it escalates the finding to a moderator agent. You pass the HTTP endpoint directly into your agent's configuration. The crew handles the hierarchical execution automatically, deciding whether to file a report or trigger an alert based on the telemetry.

Delegate ESA Near Earth Objects MCP Server Tasks

`get_object_physical_properties` pulls data straight from the ESA NEOCC physical properties database. Your science agent extracts the albedo and diameter, then hands those metrics to the risk assessment agent. Here is the math: impact energy relies on mass, and mass relies on these physical properties. The risk agent cross-references this data with `get_risk_list` to verify the Torino Scale rating. Using the MCP HTTP transport, you restrict the science agent to physical data and the risk agent to threat metrics.

Setup guide

Set up ESA Near Earth Objects MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke ESA Near Earth Objects tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="ESA Near Earth Objects Analyst",
    goal="Access and analyze ESA Near Earth Objects data via MCP.",
    backstory="Expert analyst with direct ESA Near Earth Objects access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent ESA Near Earth Objects transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="ESA Near Earth Objects Analyst",
        goal="Access and analyze ESA Near Earth Objects data via MCP.",
        backstory="Expert analyst with direct ESA Near Earth Objects access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent ESA Near Earth Objects transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

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 CrewAI

Install `crewai[tools]`. For basic access, add the server URL to the `mcps` array in your agent definition. The agent will automatically discover tools like `get_priority_list`.

Yes. Import the HTTP transport from `crewai.mcp` and apply a `tool_filter`. You can allow your orbital agent to use `get_object_ephemerides` while blocking it from accessing the risk lists.

Tools like `get_all_nea_list` return thousands of entries. Your research agent processes this raw output and stores only the relevant designations in the crew's shared memory for other agents to analyze.

CrewAI agents are autonomous. If `get_object_orbital_elements` returns an error, the agent will read the failure message, adjust its parameters, and attempt the call again without crashing the entire crew.

The integration only forwards the specific string arguments required by the tools, such as the asteroid designation or date range. Your crew's internal prompts, shared memory, and agent instructions never leave your local environment.

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