01 / AGENT-NATIVE SPATIAL INTELLIGENCE

Give your agent a sense of place.
Keep the evidence attached.

Connect Claude, ChatGPT, Codex and IDE agents to Shelob. They can resolve places, compare change, follow relationships and return every answer with its sources and licence records.

SKILL: Install the workflow
MCP: Use live spatial tools
API: Build repeatable queries

02 / SUPPORTED AGENTS

Connect Shelob to the agents your team already uses.

Install the skill in compatible coding agents. Connect desktop and IDE agents through authenticated remote MCP. Use REST in custom agents and production systems.

Claude Desktop

Claude Code

Codex

ChatGPT

Cursor

GitHub Copilot

Windsurf

Cline

Roo Code

Install the Shelob skill ↓Connect via remote MCP ↘Use the REST API ↗

One plan covers every connection: the API with your key, MCP with your sign-in.

PLAN
ENTITLEMENT

One plan. Every connection.

Your plan sets your query allowance. The REST API authenticates with your plan key; MCP clients sign in once through your browser. Both return the same records, with the same source and licence labels.

ACTIVE PLANSPATIAL INTELLIGENCE / TEAM

DATA LICENCE: Customer-specific terms
REST: Entitled base URL
MCP: Remote agent endpoint
CREDENTIAL: API key (REST) · sign-in (MCP)

Usage from every connection counts against the same plan.

04 / CONNECT

Three steps to a sourced spatial answer.

Choose your agent surface

Install the Shelob skill in Codex or another skill-compatible agent. For other clients, connect the authenticated remote MCP server directly.

SKILLREMOTE MCPRESTDIRECT

Install the Shelob skill ↓

Connect your plan once

Add the MCP server to your client and sign in when it asks. For the API, keep your key in the host’s secret manager, out of prompts and shared configuration.

SHELOB_MCP_URL="https://app.shelob.ai/mcp"
SHELOB_API_URL="issued with plan"
SHELOB_API_KEY="••••••••"   # REST only

Ask about the real world

Your agent can now query place, change and relationships with the source and licence attached.

INSURANCE AGENT QUESTION

Which insured logistics sites have higher flood and access exposure than at their last renewal?

SHELOB · FIND_CHANGES06 sitesillustrative · sources attached

05 / CONNECTION ROUTES

Choose how your agent
uses Shelob.

Install the workflow with the skill, give an agent live tools through MCP or call Shelob directly through REST. Every route returns the same sources, dates and data rights.

01INSTALL THE SKILL

Codex and coding agents

Install Shelob’s query workflow, tool guidance and evidence rules in a skill-compatible agent.

Download skill ↓

02CONNECT REMOTE MCP

Desktop and IDE agents

Add the authenticated Shelob MCP endpoint once, then ask spatial questions without leaving your agent or editor.

Connect via MCP ↗

03USE THE API

Custom agents and products

Use REST for repeatable queries, batch work and production systems. Every response keeps its sources, observation dates and licence records.

View API setup ↗

WHAT “MCP SUPPORT” MEANS

Point a compatible client at Shelob. Authenticate once. Use the tools your plan allows.

The host chooses when to call a tool. Shelob resolves the location, runs the bounded spatial operation and returns structured evidence that the agent can inspect and cite.

01REMOTE ENDPOINT

Streamable HTTP MCP

→

02SIGN IN

OAuth, in your browser

→

03SHELOB TOOLS

Place · area · change · verify

→

04GROUNDED RESULT

Evidence · source · licence

DIRECT CONNECTION: Codex, Claude, Cursor and compatible IDE agents can use the Shelob skill or remote MCP endpoint.

MANAGED WORKSPACES: ChatGPT custom MCP apps depend on the workspace plan and administrator configuration.

SEE IT
IN CONTEXT

DESKTOP · IDE · SYSTEM

What Shelob looks like inside a chat, a coding task and an IDE.

Illustrative sessions. Ask in plain language, hand an agent a portfolio check, or call Shelob while writing product code. Every answer comes back structured, with its sources.

Claude DesktopMCP CONNECTED

YOU

Which depots moved into a higher-risk flood trajectory this quarter?

SHELOBfind_changes✓

CLAUDE

Six depots need review. The answer includes 12 attributed sources and their licence records.

CLAUDE DESKTOPAsk naturally. Inspect the evidence.

CodexSKILL ACTIVE

TASK

Check every proposed site against current boundaries and hazard change.

SHELOBverify_place × 24✓

RESULT

24 sites checked. Three conflicts were flagged with the supporting observations attached.

CODEX DESKTOPInstall the skill. Delegate the work.

IDE · portfolio-risk.tsAGENT MODE

const res = await fetch(
  `${SHELOB_API_URL}/grounded/find_changes` +
  `?min_longitude=-95.38&min_latitude=29.72` +
  `&max_longitude=-95.24&max_latitude=29.80&since_days=90`,
  { headers: { "X-API-Key": SHELOB_API_KEY } }
);

AGENT

Shelob returned 6 changed sites.

View sources ↗Open map ↗

IDE AGENTSUse MCP in the editor. Use REST in the product.

ONE CONNECTION

Add Shelob once. Use it across your agent stack.

The skill handles the workflow. MCP handles live tool use. REST handles repeatable system calls. Every result follows the same plan entitlements and keeps its evidence attached.

Marketplace or direct installOne plan keyMCP + RESTWorkspace to production

Connect your agent ↗

07 / DATA RIGHTS

Agents can read the data. They also need to know the rules.

Attribution stays attached

Publisher, source URL, Shelob ID and observation time travel with the answer.

Licence records stay visible

Agents surface permissive, restricted, unknown and review-required status instead of assuming permission.

Labels come with every record

Whatever the plan, each record returns its licence status, so an agent can check it before reusing anything.

08 / START

Give your agents
spatial context they can cite.

Choose a Team or Scale plan, install the skill and connect with the issued MCP endpoint and plan key.