Connect · MCP

Connect.

TERN runs as an MCP server. Point any compatible client at it and the market becomes tools your own agents can use.

The tool surface

Five tools today. Each returns evidence with its provenance attached.

The tools TERN exposes over MCP
Tool	Returns
market.observe	Assets, operators and capacity in an area
catchment.compare	Overlap and share movement between locations
peak.profile	Demand shape over time, with its range
site.underwrite	Build, upgrade or walk away, with rationale
evidence.cite	The sources behind any figure

Tool names are placeholders pending the final API surface.

01 / Credentials
A scoped credential carries the markets, tools and call limits your team is allowed.
02 / Point a client
Add TERN as a remote MCP server. The client discovers the tool surface itself.
03 / Ask
Your agent picks the tools. Every result carries its sources and window.

Connection details

A remote MCP endpoint plus a bearer credential issued to your team.

TODO — connection string issued per team, not published pre-launch.

Scoping: Calls outside the agreed markets and asset scope return a refusal.
Per-tool permissions: Read and underwriting tools are granted separately.
Audit trail: Caller, arguments, sources and model version are recorded, and yours to export.
Replay: Any past run can be re-executed against today and compared.

Credentials are issued per team while TERN is pre-launch. Tell us which client you work in.