BLOGWorldEye in Claude: Connect the MCP Server in About a Minute
▸ Why Claude is the natural fit
Anthropic created the Model Context Protocol in late 2024, and the rest of the industry has been adopting it since. For WorldEye that makes Claude the simplest connection in this whole series: there is no translation layer and nothing to install on our side. The same public endpoint documented on our developers page — https://worldeye.app/api/v1/mcp — is the one Claude clients connect to.
The server is small on purpose: five read-only tools over the camera catalogue whose operators cleared it for redistribution, plus the USGS earthquake feed. Claude can search cameras by place or kind, fetch one camera's current snapshot and watch link, find cameras near a named place or coordinates, list the last 24 hours of magnitude 2.5+ earthquakes, and check your key's remaining quota. Every camera record carries its operating agency's credit.
▸ Connecting, client by client
Start with a free key: sign in at worldeye.app, open Account Settings → API keys, and create one. It starts with wek_ and is shown once. A free key covers 100 requests a day; WorldEye plans raise that (Lite 1,000, Pro 5,000, Ultra 25,000).
Claude Code and Claude Desktop read MCP servers from a JSON config: add a “worldeye” entry with the endpoint URL and an Authorization header carrying “Bearer” plus your key, then restart the client. The key travels as a header, never as a tool argument, so it does not leak into conversations. On claude.ai, custom connectors let you add a remote MCP server by URL from the Connectors settings; if your plan's connector form asks for OAuth only, use a config-based client instead — the endpoint itself is identical. Step-by-step detail lives on our WorldEye in Claude page.
▸ The directory listing: not submitted yet
Anthropic opened a connector directory submission portal (claude.ai/directory/manage) in September 2026: submissions are scanned automatically and listed as Community connectors by default. Submitting requires signing in with a paid Claude plan — that account is the site owner's, so the listing is staged on his side, not done. Until it lands, the direct connection above is the way in, and it is fully functional. Nothing about that is a limitation of the server: it is the same endpoint either way.
▸ Frequently asked questions
Do I need a paid Claude plan to connect WorldEye?+
No. The connection works in config-based clients (Claude Code, Claude Desktop) and as a user-added custom connector. A paid plan is only needed for submitting a public directory listing, which is the site owner's step, not yours.
Is my API key safe inside Claude?+
The key is sent as an Authorization header to WorldEye's endpoint only, never as a tool argument, so it does not appear in conversation text. Keys are free, shown once at creation, and can be revoked from Account Settings at any time.
What can Claude do with WorldEye connected?+
Search the cleared camera catalogue, fetch a camera's current snapshot and watch link, find cameras near a place, list the latest USGS earthquakes, and check the key's plan and remaining daily quota. It cannot stream video, change anything, or see any user data.
Try it live on the map.
Everything in this guide runs on WorldEye — the free 3D globe with flights, cameras, satellites, and natural hazards. No signup.
One email when the sky does something big
Rocket launches, storms overhead and new camera drops — plus major WorldEye news. Rare, and no spam, ever.
Instant subscribe — no confirmation email. We check the address as you type it in.