Skip to main content

Connect with Clients

OpenSolar MCP works with MCP-compatible hosts that support remote Streamable HTTP servers and OAuth. Use the same production URL in every client:

https://mcp.opensolar.com/mcp

No API keys belong in client config. Clients discover OAuth from the server and open a browser so you can sign in at OpenSolar.

Prerequisites​

Gemini CLI​

Gemini CLI reads MCP servers from settings.json. Use httpUrl for Streamable HTTP servers; OAuth is discovered automatically when the server returns 401.

  1. Add OpenSolar to ~/.gemini/settings.json (or your project settings.json):
{
  "mcpServers": {
    "opensolar": {
      "httpUrl": "https://mcp.opensolar.com/mcp"
    }
  }
}
  1. Restart Gemini CLI, or run /mcp to reload servers. On first connect Gemini CLI detects OAuth from server metadata, opens your browser, and stores tokens in ~/.gemini/mcp-oauth-tokens.json.
  2. Sign in in the browser when prompted.
  3. If authentication did not start automatically, run:
/mcp auth opensolar

Claude Code​

Claude Code recommends HTTP transport for remote MCP servers. Add OpenSolar with claude mcp add or project .mcp.json, then authenticate from /mcp.

  1. Add the server from your terminal:
claude mcp add --transport http opensolar https://mcp.opensolar.com/mcp
  1. Or add equivalent JSON to .mcp.json in your project (type is required for url entries):
{
  "mcpServers": {
    "opensolar": {
      "type": "http",
      "url": "https://mcp.opensolar.com/mcp"
    }
  }
}
  1. In a Claude Code session, run /mcp and authenticate opensolar. Claude Code runs the OAuth flow for HTTP servers that return 401. Sign in at OpenSolar login when the browser opens.

Codex​

Codex (ChatGPT desktop app, CLI, and IDE extension) share MCP servers in config.toml. OpenSolar uses Streamable HTTP with OAuth, so no API keys belong in the file.

  1. Add OpenSolar to ~/.codex/config.toml (global) or .codex/config.toml (trusted projects only):
[mcp_servers.opensolar]
url = "https://mcp.opensolar.com/mcp"
  1. Or add the server from your terminal:
codex mcp add opensolar --url https://mcp.opensolar.com/mcp
  1. Authenticate opensolar when prompted (ChatGPT desktop or IDE: Settings → MCP servers → Authenticate). From the CLI, run the following if OAuth did not start automatically. Codex uses dynamic client registration and opens your browser to sign in at OpenSolar.
codex mcp login opensolar
  1. Type /mcp in Codex to confirm opensolar is connected.

Cursor​

Cursor supports remote MCP servers via mcp.json using a url field. OpenSolar uses OAuth (Streamable HTTP), so no API keys go in the file.

  1. Add OpenSolar to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):
{
  "mcpServers": {
    "opensolar": {
      "url": "https://mcp.opensolar.com/mcp"
    }
  }
}
  1. Open Cursor → Customize → MCP and enable the opensolar server. Remote servers that require OAuth show an Authenticate action. Cursor completes dynamic client registration and opens your browser to sign in.
  2. Complete sign-in in the browser when Cursor opens it, then return to Cursor.
  3. Approve MCP tool calls in chat when Cursor prompts you (or allowlist tools in Run Mode).

When prompted in any client, sign in with email/password, Google, or your organisation SSO. If you belong to more than one organisation, select the organisation for this grant. Choose scopes (READ, WRITE, DELETE) and approve.

Verify the connection​

Ask the agent to run whoami. A successful call returns identity claims from your MCP token (organisation, scopes, client) without calling OpenSolar API and without consuming daily MCP tokens.

Then ask the agent what it can do. That confirms the connection, available tools, Raw Data API Access, and scopes.