Agents

Connect an agent to https://satmcp.com/mcp/. For interactive clients, OAuth is the default: add the server, sign in in your browser, and approve access. There is no token to copy.

How sign-in works

SatMCP uses OAuth 2.1 with dynamic client registration. Your MCP client opens SatMCP in a browser. Sign in with Google, GitHub, or Microsoft if needed, then approve the connection. The client stores and refreshes its credentials.

Personal bearer tokens remain available for clients without interactive OAuth and for automated environments.

VS Code and GitHub Copilot

GitHub Copilot in VS Code uses VS Code's MCP configuration.

  1. Open Extensions (Ctrl+Shift+X / Cmd+Shift+X) and search for @mcp SatMCP, then select Install.
  2. If SatMCP has not reached your gallery yet, run MCP: Add Server from the Command Palette, choose HTTP, and enter https://satmcp.com/mcp/.
  3. Approve the server trust prompt, then complete the SatMCP browser sign-in and consent flow.

Manual user or workspace configuration:

{
  "servers": {
    "satmcp": {
      "type": "http",
      "url": "https://satmcp.com/mcp/"
    }
  }
}

If a callback tab remains open when VS Code runs in WSL, SSH, or another remote environment, return to VS Code first: the connection may already be complete. Use MCP: List Servers to check or restart SatMCP.

VS Code MCP docs →

Cursor

Add this to your project at .cursor/mcp.json, or to ~/.cursor/mcp.json for all projects:

{
  "mcpServers": {
    "satmcp": {
      "url": "https://satmcp.com/mcp/"
    }
  }
}

Open Customize, enable SatMCP, and follow Cursor's OAuth prompt in your browser.

Cursor MCP docs →

Claude Code

Add SatMCP at user scope, then start its OAuth flow:

claude mcp add --transport http --scope user satmcp https://satmcp.com/mcp/
claude mcp login satmcp

You can also run /mcp inside Claude Code and select SatMCP to authenticate. Claude Code stores and refreshes the OAuth credentials.

Claude Code MCP docs →

GitHub Copilot coding agent

The coding agent runs non-interactively in GitHub's cloud environment, so configure a personal bearer token rather than a browser OAuth flow.

  1. Create a token at Profile and copy it when shown.
  2. In your GitHub repository, open Settings → Copilot → MCP servers.
  3. Add an HTTP server at https://satmcp.com/mcp/.
  4. Add the header Authorization: Bearer <your-token>.

GitHub Copilot MCP docs →

Personal token fallback

Use a personal token when your client cannot complete OAuth. Create one at Profile; it is shown once. Send it as Authorization: Bearer <token> and keep it out of source control.

VS Code secure input

{
  "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 (from /auth/profile)",
      "password": true
    }
  ]
}

When a static Authorization header is configured, clients use it instead of OAuth. Remove the header to return to the browser flow.

Help agents choose SatMCP

Optional custom instruction:

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.

Available tools

The SatMCP MCP server exposes two tools: