Stellaris Modding MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| stellaris-versionA | ステラリスの現在のバージョン情報を取得します。ビルドID、最終更新日時、利用可能なバージョン番号などmodding に必要な情報を提供します。 |
| cwtools-configA | CWToolsのStellarisコンフィグルール(.cwt files)を取得します。最新の安定版または開発版から、config/直下およびサブディレクトリ（common/等）内の特定のファイルまたは全ファイルを取得できます。 |
| stellaris-searchA | OldEnt/stellaris-triggers-modifiers-effects-listリポジトリからStellarisの最新バージョンのドキュメントを検索し、指定したキーワードに一致する箇所をコードスニペットとして返します。大きなファイルを効率的に検索できます。 |
| stellaris-validateA | 指定したtrigger、effect、modifier、scope、localizationが最新バージョンのStellarisで有効かどうかをチェックします。modding時の互換性確認に便利です。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct and non-overlapping purpose: cwtools-config handles configuration file retrieval, stellaris-search performs documentation searches, stellaris-validate checks code validity, and stellaris-version provides version information. There is no ambiguity in their functions, making tool selection clear for an agent.
Three tools follow a consistent 'stellaris-' prefix pattern (stellaris-search, stellaris-validate, stellaris-version), while cwtools-config deviates slightly with a different prefix. This minor inconsistency does not hinder readability, as all names are descriptive and use snake_case consistently.
With 4 tools, the count is reasonable for a modding server, covering key areas like configuration, search, validation, and version info. It might benefit from additional tools for broader modding workflows, but it is well-scoped and not overly sparse or bloated.
The tools cover essential modding tasks such as configuration retrieval, documentation search, code validation, and version checking. However, there are notable gaps, such as missing tools for creating or editing mod files, testing mods, or managing dependencies, which could limit agent effectiveness in full modding workflows.