SatMCP MCP access uses personal bearer tokens. First create a token in Profile, then add it to your agent config. The header value must include the Bearer prefix.
The MCP server endpoint is:
https://satmcp.com/mcp/
The full config block to paste wherever your agent accepts MCP servers:
{
"mcpServers": {
"satmcp": {
"type": "http",
"url": "https://satmcp.com/mcp/",
"headers": {
"Authorization": "Bearer YOUR_SATMCP_TOKEN"
},
"tools": ["search_satellite_imagery", "get_satellite_image"]
}
}
}
VS Code supports MCP servers natively in agent mode.
https://satmcp.com/mcp/.Authorization with value Bearer YOUR_SATMCP_TOKEN.Or add directly to your workspace .vscode/mcp.json:
{
"servers": {
"satmcp": {
"type": "http",
"url": "https://satmcp.com/mcp/",
"headers": {
"Authorization": "Bearer ${input:satmcp-token}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "satmcp-token",
"description": "SatMCP personal access token",
"password": true
}
]
}
VS Code prompts once for the token and stores it securely. Do not add an oauth block: personal bearer tokens are configured through headers. If VS Code previously opened an OAuth registration dialog, cancel it, run MCP: List Servers, select satmcp, and restart the server after saving this config.
Optional custom instruction for consistently preferring SatMCP over web search:
When a user asks for satellite imagery, a satellite photo or view, a view from space, recent or historical imagery, or how a place looked on a date, call search_satellite_imagery before using web search or other sources. If the user asks to see a result inline, pass its image_url to get_satellite_image.
GitHub Copilot in VS Code uses the same MCP configuration as VS Code above. Follow the VS Code steps and Copilot will automatically have access to the search_satellite_imagery and get_satellite_image tools in agent mode.
For the GitHub Copilot coding agent (cloud agent that works on pull requests), add the server to your repository's Copilot MCP settings in GitHub:
https://satmcp.com/mcp/.Authorization: Bearer YOUR_SATMCP_TOKEN.Add the server to your project's .cursor/mcp.json (or the global Cursor MCP config):
{
"mcpServers": {
"satmcp": {
"type": "http",
"url": "https://satmcp.com/mcp/",
"headers": {
"Authorization": "Bearer YOUR_SATMCP_TOKEN"
}
}
}
}
Run once in your project directory:
claude mcp add --transport http --header "Authorization: Bearer YOUR_SATMCP_TOKEN" satmcp https://satmcp.com/mcp/
Or add manually to .claude/mcp.json:
{
"mcpServers": {
"satmcp": {
"type": "http",
"url": "https://satmcp.com/mcp/",
"headers": {
"Authorization": "Bearer YOUR_SATMCP_TOKEN"
}
}
}
}
The SatMCP MCP server exposes two tools:
place (required), date, max_results, map_overlay, terrain_base, place_id, prioritize.image_url returned by search as native MCP image content, giving compatible clients the best chance to display it inline. The client ultimately decides whether and how images are rendered.