MCP server and REST API

Everything you see in SolarScope, your AI agent can do too

Connect SolarScope to Claude, Cursor, Codex or your own code. Your agent screens US sites for solar resource, grid distance and FEMA flood risk, ranks them, saves the best to your projects and makes a PDF report. It uses the same data and the same verdict as Site Studio.

  • Claude
  • Cursor
  • Codex
  • GitHub Copilot
  • Windsurf

Included in the Pro and Portfolio plans.

One prompt, five sites, one report

A real answer from Claude Code connected to SolarScope (shortened).

Screen these 5 sites for solar, rank them, save the best one to SolarScope and make a one-page PDF report: Buckeye AZ, Pahrump NV, Pecos County TX, Miami FL, Antelope Valley CA.

Buckeye, AZ is the best site. It's the only one with strong sun, a nearby high-voltage line and a clear margin from flood zones all at once.

RankSiteSun (GHI)Nearest lineFloodVerdict
1Buckeye AZ5.821.5 km, 238 kVOutside high-risk zonesGood
2Pahrump NV5.782.8 km, 138 kVOutside, high-risk zone 0.27 km awayGood
3Pecos County TX5.620.18 km, 138 kVOutside high-risk zonesGood
4Miami FL5.174.6 km, 138 kVInside FEMA zone AEPossible deal-breaker
5Antelope Valley CA5.8314.2 kmInside FEMA zone AOPossible deal-breaker

Saved Buckeye AZ to your SolarScope projects and created a one-page PDF site report. This is a first screen: confirm line capacity with the utility and get a flood survey of the site.

What your agent can do

Seven tools, the same as in the app.

screen_site

Screen a site

Solar resource, nearest transmission line (distance and voltage), FEMA flood zone and a good / check / deal-breaker verdict for one US location.

screen_sites

Screen and rank sites

Up to 25 sites at once, ranked best first, so your agent can shortlist a pipeline.

save_site

Save a site

Saves a site to your SolarScope projects, so it shows up in Site Studio and your portfolio.

list_projects

List your projects

Your saved Site Studio projects with their verdicts. Free.

get_project

Read a project

Everything saved for one project: data, notes and the AI first read. Free.

create_report

Create a PDF report

A branded PDF site report for a saved project, returned as a link.

get_usage

Check usage

This month's screenings and reports used and included. Free.

How to connect

1. Create an API key under Account > API & AI agents (Pro and Portfolio plans). Keep it private, like a password.
2. Add SolarScope to your AI tool:

MCP server URL: https://solarscope.io/mcp, with the header Authorization: Bearer YOUR_KEY

Claude (claude.ai and Claude Desktop)
In Claude, open Settings > Connectors > Add custom connector. Name it SolarScope, use the URL https://solarscope.io/mcp and add your API key. Then ask Claude about a site.
Claude Code
Run in a terminal:
claude mcp add --transport http solarscope https://solarscope.io/mcp --header "Authorization: Bearer YOUR_KEY"
Cursor
Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
  "mcpServers": {
    "solarscope": {
      "url": "https://solarscope.io/mcp",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}
Codex
Add to ~/.codex/config.toml and set SOLARSCOPE_API_KEY in your environment:
[mcp_servers.solarscope]
url = "https://solarscope.io/mcp"
bearer_token_env_var = "SOLARSCOPE_API_KEY"
GitHub Copilot in VS Code
Add to .vscode/mcp.json. VS Code asks for the key once and stores it securely:
{
  "inputs": [{ "type": "promptString", "id": "solarscope-key", "description": "SolarScope API key", "password": true }],
  "servers": {
    "solarscope": {
      "type": "http",
      "url": "https://solarscope.io/mcp",
      "headers": { "Authorization": "Bearer ${input:solarscope-key}" }
    }
  }
}
Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
{
  "mcpServers": {
    "solarscope": {
      "serverUrl": "https://solarscope.io/mcp",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}
REST API, for scripts
The same tools as plain HTTPS endpoints with JSON in and out:
curl -H "Authorization: Bearer YOUR_KEY" -H "Content-Type: application/json" \
  -d '{"lat": 33.351, "lng": -112.75}' https://solarscope.io/api/v1/screen
  • POST /api/v1/screen one site, POST /api/v1/screen/batch up to 25 sites, ranked
  • GET /api/v1/projects, GET /api/v1/projects/<id>, POST /api/v1/projects to save a site
  • POST /api/v1/projects/<id>/report returns a link to the PDF; GET /api/v1/usage
  • Full tool list with input schemas: https://solarscope.io/api/v1/tools

Included in your plan

Listing and reading your saved projects is always free. Screening or saving a site uses one screening; a PDF report uses one report.

Pro

50 site screenings and 10 PDF reports per month

Portfolio

500 site screenings and 50 PDF reports per month

Agent access is for paid plans and is not part of the free trial. Need more? Extra screenings at $0.50 each are coming soon; until then, contact us.

Questions

Does SolarScope have an MCP server?

Yes. The SolarScope MCP server is at https://solarscope.io/mcp (Streamable HTTP). Connect it to Claude, Claude Code, Cursor, Codex, GitHub Copilot, Windsurf or any MCP client that can send an API key. There is also a REST API at https://solarscope.io/api/v1.

What can an AI agent do with SolarScope?

Screen US sites for solar resource (NREL), distance and voltage of the nearest transmission line (HIFLD) and FEMA high-risk flood zones, rank up to 25 sites at once, save sites to your projects, read your saved projects and create PDF site reports.

How much does it cost?

It is included in the paid plans: Pro includes 50 screenings and 10 PDF reports per month, Portfolio 500 screenings and 50 reports. Listing and reading saved projects is free. Agent access is not part of the free trial.

Can my agent see other people's projects?

No. An API key only works for its own account: your agent sees and saves your projects only. You can revoke a key at any time under Account > API & AI agents, and it stops working right away.

Does it work outside the US?

Solar resource works worldwide (NREL in the Americas, PVGIS elsewhere). Transmission lines and FEMA flood zones are US data, so outside the US those checks are marked unavailable rather than guessed.

Is the screening a substitute for a utility or flood study?

No. It is a fast first screen to decide which sites deserve a closer look. Confirm line capacity with the utility and get a flood survey before you commit to a site.