arma3-wiki MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARMA3_WIKI_DATA | No | Cache directory for the wiki data | ./wiki |
| ARMA3_WIKI_BRANCH | No | Branch of the upstream repository to use | dist |
| ARMA3_WIKI_UPSTREAM | No | Upstream repository URL to clone the wiki data from | |
| ARMA3_WIKI_REFRESH_HOURS | No | Background refresh interval in hours | 24 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_commandB | Full wiki YAML for an SQF script command (syntax, params, return, locality, examples). Case-insensitive. |
| lookup_eventC | Full wiki YAML for an event handler. Categories: standard, eden, group, mission, multiplayer, music, projectile, user_action, user_interface. |
| searchA | Keyword search over command/event names, groups and full text. All words must match. kind: all | commands | events. Name matches rank first. |
| list_groupA | List commands in a wiki group (e.g. 'Multiplayer', 'Particles'). Pass '' to list all groups. |
| list_tutorialsA | List the bundled scripting tutorials (best practices, MP scripting, optimisation). |
| get_tutorialB | Read a scripting tutorial by name (see list_tutorials). |
| wiki_statusB | Server version, data revision, cache location, entry counts and last refresh result. |
| refresh_wikiB | Fetch the latest upstream wiki data now and rebuild the index. |
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 8 tools
Each tool targets a clearly distinct operation: exact command lookup, exact event lookup, keyword search, group listing, tutorial listing/reading, status, and refresh. The boundary between lookup_command/lookup_event and search is well explained by the descriptions (exact YAML vs keyword search).
All names use snake_case consistently, but the verb/prefix conventions vary (lookup_, list_, get_, wiki_, refresh_, bare search). The mix is still readable and understandable, with only minor deviations from a pure verb_noun pattern.
Eight tools is well-scoped for a wiki lookup server: it covers lookup, search, browsing, tutorials, and maintenance without excessive redundancy. Each tool earns its place.
The surface covers the main lifecycle: exact lookups, keyword search, group browsing, tutorials, status, and refresh. Minor gaps exist, such as no explicit list of event categories or a dedicated event-listing tool, but agents can work around these via search.