@outerview/mcp
The official Model Context Protocol server for Outerview.
It gives an MCP host one focused tool for searching visual observations of the
physical world: places, objects, conditions, and 360-capable captures.
Install
npm install -g @outerview/mcp
Create an Outerview API key, then provide it only to the MCP server process:
export OUTERVIEW_API_KEY="ov_your_key"
outerview-mcp
For PowerShell:
$env:OUTERVIEW_API_KEY = "ov_your_key"
outerview-mcp
Configure an MCP host
Use the outerview-mcp command as a stdio server. A typical host entry looks
like this:
{
"mcpServers": {
"outerview": {
"command": "outerview-mcp",
"env": { "OUTERVIEW_API_KEY": "ov_your_key" }
}
}
}
Tool: search_world
The server exposes search_world.
query | Yes | A description of what to find in real-world visual data. |
limit | No | Result count, constrained by the API key's plan. |
interactive | No | Set true to return only 360-capable results. |
Example prompt for an MCP client: “Search for protected bike lanes in Montreal
and return 25 results.” For immersive capture work: “Find interactive 360
waterfront paths in Chicago.”
Results and access
The tool returns the raw Outerview JSON payload so an agent can inspect the
GeoJSON features, dates, location geometry, and result properties. Video access
is limited to Pro and Scale API keys. Use interactive: true before asking a
client to render a 360 view.
Environments and limits
Set OUTERVIEW_BASE_URL to use a compatible development endpoint; otherwise
the server calls https://api.outerview.ai. Free allows 5 RPM and 5 results;
Developer allows 500 RPM and 50 results; Pro allows 2,000 RPM and 50 results;
Scale allows 8,000 RPM and 200 results. See billing documentation.