Article
Access & permissions
Who can use the Load Factor MCP server, why a sign-in is refused, and how your Load Factor plan shapes every answer.
- MCP
- Updated
Overview
The MCP server gives you exactly the access your Load Factor account has, and nothing more. This page explains who can connect, why a sign-in can be refused, and what each part of your plan changes in the answers. To see your own access at any time, ask your assistant "What can I access through Load Factor?" (the whoami tool).
Who can connect
MCP access is off for every account until a Load Factor admin switches it on for yours. With it on, you can sign in when all of these hold:
- you sign in with Google using the email address of your Load Factor account, and Google has verified that address;
- your Load Factor account is active: not blocked, not retired, and your invite has been accepted;
- your account has at least one market (ISO) whose access is currently open.
If any of these fails, sign-in is refused and no token is issued. The same checks run again on every request, so access that ends mid-conversation stops there.
Why a sign-in or request is refused
| Situation | What happens |
|---|---|
| MCP access is not switched on | Refused. Ask your Load Factor admin to switch it on. |
| The email is not a Load Factor user | Refused. Sign in with the Google account that matches your Load Factor login. |
| The account is blocked or retired | Refused. |
| The invite has not been accepted | Refused until you accept your Load Factor invite. |
| Access to every ISO has ended, or has not started yet | Refused, with the ISO and the date. |
| Your Load Factor sessions were revoked (for example, you were signed out everywhere) | Your connection stops. Disconnect and connect again to sign in afresh. |
What your plan decides
Admins see every ISO with full detail, evidence and proof. For everyone else, each part of the plan applies per ISO:
| Setting | Effect on MCP answers |
|---|---|
| ISOs | Queue data comes only from the ISOs on your plan. Tools that serve one ISO's data are hidden without it: transmission_projects (MISO), search_permits (PJM, Virginia filings) and search_dg_projects (NYISO). |
| View level | Full shows every field your evidence level allows. Restricted shows list-level fields only: no coordinates, no SPV (interconnection customer), owner or parent-company names, no source links, and full project detail only for priority projects. grid_context then gives distance bands instead of miles. SEC parents of projects, and SEC registrants linked as a company's parent, follow the same rule (SEC company intelligence). |
| Evidence depth | Full includes source links and the raw source text of evidence. Summary leaves both out. |
| Confirmation proof | When proof is hidden, the explanation of which records back a developer is left out. |
| Rows per call | A tool returns at most your plan's rows per page (the strictest of the ISOs a question covers), and never more than the tool's own maximum. |
| Access window | Your access to an ISO can start and end on set dates. Outside the window that ISO is not available. |
| Modules | Decide which tools you see at all (next section). |
With full view, project coordinates are rounded to one decimal place; only admins see them unrounded.
Which tools your modules unlock
Tools your plan does not include are not listed to your assistant at all. Calling one by name gets the same answer as a tool that does not exist.
| Load Factor module | Tools |
|---|---|
| Any plan | search, fetch, whoami, data_catalog |
| Developer Tracker or Map | search_projects, get_project, get_project_evidence, queue_stats, find_companies, get_company_profile, sec_search_companies, sec_company_filings, sec_company_subsidiaries, search_plants, get_plant, search_dg_projects |
| Developer Tracker | ppa_price_benchmarks, ppa_counterparties, ppa_top_buyers, ppa_expiring_contracts, search_deals_news |
| LMP Tracker or Map | grid_context |
| LMP Tracker | lmp_snapshot |
| Transmission, Map or Developer Tracker | transmission_projects |
| Developer Tracker, Calculator or Map | market_fundamentals |
| Incentives | search_incentives, get_incentive_program |
| Permits | search_permits |
| Map, with the Data Centers view (Load Factor Demand) | search_data_centers, get_data_center |
search and fetch return only the kinds of records your modules cover.
Agents that connect with a service account get a fixed, read-only subset of these tools, whatever modules the account holds.
When your access changes
The server re-reads your account on every request (with a cache of about 15 seconds). When an admin switches off MCP access, blocks your account, ends your access window or changes your plan, the change applies within seconds, even in a conversation that is already connected. Switching MCP access off also stops your client from renewing its sign-in.
Withheld for everyone
Some information never leaves Load Factor through MCP, whatever the plan: landowner names and land-record details, e-mail addresses, phone numbers, street addresses and names of individuals in evidence, and contact details in incentive program text. New York distributed-generation developer values that look like a private person's name are withheld too.