MCP (Model Context Protocol)
Connect AI agents like Claude and ChatGPT to SateAIs via the Model Context Protocol.
The SateAIs MCP server lets AI agents call satellite detection tools directly. Generate a connection URL from the SateAIs API Console and paste it into any MCP-compatible client.
How it works
- Endpoint:
https://mcp.spcsft.com/mcp - Authentication: Your SateAIs API key, passed as the
sateaisApiKeyquery parameter - Transport: Streamable HTTP (stateless, JSON)
Keep your URL private
The connection URL embeds your API key. Treat it like a password — never commit it to a public repository or paste it into shared documents.
1. Generate the connection URL
- Sign in to the SateAIs API Console.
- Open API Keys in the sidebar.
- Click Generate MCP Link in the Connect to AI Agents (MCP) card.
- The full URL is copied to your clipboard.
The URL has the form:
https://mcp.spcsft.com/mcp?sateaisApiKey=sk_live_xxxxx2. Configure your client
Claude.ai (Pro / Team / Enterprise) supports remote MCP servers natively — no local bridge required.
-
Open Claude.ai and go to Settings → Customize → Connectors.
-
Click Add custom connector.
-
Paste your generated MCP URL:
https://mcp.spcsft.com/mcp?sateaisApiKey=sk_live_xxxxx -
Choose No authentication (the API key is already in the URL) and save.
-
The
sateaisconnector becomes available in any new chat — toggle it on from the conversation's tools menu.
Custom connectors require a Claude.ai paid plan. Free accounts cannot add custom MCP servers — use Claude Desktop instead.
Edit the Claude Desktop configuration file and add a sateais entry under mcpServers:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"sateais": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.spcsft.com/mcp?sateaisApiKey=sk_live_xxxxx"
]
}
}
}Restart Claude Desktop. The sateais server appears under Settings → Developer → MCP Servers, and the tools become available in any chat.
mcp-remote is a stdio↔HTTP bridge — Claude Desktop launches it locally and it forwards requests to mcp.spcsft.com. Node.js 18+ is required.
ChatGPT supports MCP via Custom connectors (Developer mode, currently rolling out to Plus / Pro / Enterprise plans).
-
Open ChatGPT and go to Settings → Connectors → Advanced → Developer mode.
-
Click Add custom connector.
-
Set the connector URL to your generated MCP link:
https://mcp.spcsft.com/mcp?sateaisApiKey=sk_live_xxxxx -
Choose No authentication (the API key is already in the URL) and save.
-
Enable the connector for the conversation where you want to use it.
Custom connectors require ChatGPT Developer mode, which may not be available on all plans. See OpenAI's MCP documentation for the latest availability.
Available tools
The MCP server exposes the same detection capabilities as the REST API:
| Tool | Description |
|---|---|
detect_ship | Detect vessels in Sentinel-1 SAR imagery. |
detect_oilslick | Identify oil spills on the sea surface. |
detect_newbuilding | Find newly constructed structures between two periods. |
detect_disappearbuilding | Identify buildings missing between two periods. |
detect_timeseries | Detect surface change between observations. |
check_job_status | Poll the status of a submitted job. |
get_job_result | Fetch the GeoJSON result of a completed job. |
open_polygon_draw | Open a polygon-drawing widget for AOI definition. |
Credits, rate limits, and endpoint permissions follow the same rules as the REST API — see Authentication and Rate limits.
Rotating the URL
Because the URL embeds your API key, rotating the key invalidates the URL. After rotation:
- Re-open API Keys in the Console.
- Click Generate MCP Link again to copy the new URL.
- Update each client's configuration with the new URL.
Rotate on leak
If the MCP URL is exposed — for example pasted into a public document or AI prompt — rotate the underlying API key immediately. Leaked URLs can consume your credits until the key is revoked.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
401 Unauthorized from the MCP server | Missing or revoked API key | Regenerate the MCP link in the Console. |
403 Forbidden on a tool call | Plan lacks permission for the endpoint | Check entitlements in the Console. |
| Claude Desktop shows no tools | mcp-remote failed to launch | Confirm Node.js 18+ is on PATH, then restart Claude Desktop. |
Job stays pending for >2 hours | Underlying detection job stalled | Call check_job_status directly; contact support if it remains stuck. |