Developer and Agent Resources
Use these canonical resources to understand Stellaris Companion without scraping the interface or guessing at private endpoints. The public API is intentionally small; campaign data remains on the player’s computer and is exposed to compatible local AI clients through the desktop app’s Local MCP bridge.
OpenAPI 3.1
↗/openapi.jsonTyped operations and response schemas for the supported public feedback service.
API catalog
↗/.well-known/api-catalogRFC 9727 linkset connecting service descriptions, documentation, health, and privacy.
Agent documentation index
↗/llms.txtWhen-to-use guidance and a concise map of the public documentation corpus.
Complete agent corpus
↗/llms-full.txtThe combined Field Manual and strategy-guide corpus in plain text.
Agent skills
↗/.well-known/agent-skills/index.jsonDiscoverable product and Local MCP instructions with integrity digests.
Product facts
↗/.well-known/product-facts.jsonCurrent release, download, platform, language, compatibility, provider, and privacy facts.
Feedback and service health
The published OpenAPI document covers reading the public feedback board, submitting website feedback, and checking service health at feedback.galacticfilingcabinet.com. Agents may submit feedback only after an explicit user request and should avoid duplicate, speculative, or test reports.
Campaign tools stay local
The desktop app ships a local stdio MCP server for strategy context, recent events, Chronicle drafting, and explicit Chronicle save-back. It is configured from the app and launched by the user’s local MCP client. The website does not host a remote campaign MCP endpoint and cannot inspect a local save archive.
Read Local MCP setup →Interfaces that are not offered
- No public hosted API for reading a player’s campaign or raw save file.
- No remote campaign MCP server, cloud-save synchronization service, or public webhooks.
- No supported third-party access to the app-owned Chronicle publication credentials or private local Electron backend.