Terrava

History on a living globe

Explore 8,000+ years of empires, kingdoms, and changing borders on an interactive globe. Ask for a polity or year, follow its mapped history, read profiles and sources, or start a Living Journey.

What you can ask

Show Carthage.

MCP connector

Server URL: https://terrava.earth/api/mcp
Login: None
Protocol: MCP 2025-11-25
Instructions: Requests to open, show, or put something in the side panel target the existing panel: "open Carthage in the side panel" and "show Orion in this panel" use with the target atlas_instance_id from the latest app context and the requested destination command. This explicit target overrides new-result routing, including followup: new_result; do not create another inline card. Use also for other explicit existing-map requests or for navigation in a direct-open workspace. New destination requests without an explicit existing target open independent map cards. Bare names such as "Athens", "Orion", "Carthage", and "now show Athens" use destination tools, even when a map is already open or expanded. resolves a name or polity_id; opens a constellation found by . atlas_instance_id supplies source context and never makes a destination tool update that map. updates one connected atlas and returns no widget. Playback, atlas/sky settings, and require a connected atlas_instance_id and never open a replacement card. Independent results and restoration resolve the latest release. scene_version is an optional command precondition; inspection reads the latest frame. Ambiguous names return choices. New results return accepted with rendered: false. For successful presentation requests, use a brief invitation naming the destination, such as "Explore the Kingdom of Mari in Terrava." Keep routine readiness and missing render confirmation out of conversational replies unless the user asks about rendering status. Report actual errors clearly. Do not claim rendering or execution is complete without confirmation. In-place commands return ready with rendered: true after frame confirmation. resets to the latest release.

Tools

Reads data8

Changes data17

Skills

None in the store listings or on the server

MCP connector

Server URL

https://terrava.earth/api/mcp

None

Protocol

MCP 2025-11-25

Instructions

Requests to open, show, or put something in the side panel target the existing panel: "open Carthage in the side panel" and "show Orion in this panel" use with the target atlas_instance_id from the latest app context and the requested destination command. This explicit target overrides new-result routing, including followup: new_result; do not create another inline card. Use also for other explicit existing-map requests or for navigation in a direct-open workspace. New destination requests without an explicit existing target open independent map cards. Bare names such as "Athens", "Orion", "Carthage", and "now show Athens" use destination tools, even when a map is already open or expanded. resolves a name or polity_id; opens a constellation found by . atlas_instance_id supplies source context and never makes a destination tool update that map. updates one connected atlas and returns no widget. Playback, atlas/sky settings, and require a connected atlas_instance_id and never open a replacement card. Independent results and restoration resolve the latest release. scene_version is an optional command precondition; inspection reads the latest frame. Ambiguous names return choices. New results return accepted with rendered: false. For successful presentation requests, use a brief invitation naming the destination, such as "Explore the Kingdom of Mari in Terrava." Keep routine readiness and missing render confirmation out of conversational replies unless the user asks about rendering status. Report actual errors clearly. Do not claim rendering or execution is complete without confirmation. In-place commands return ready with rendered: true after frame confirmation. resets to the latest release.

Tools