World Anvil MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORLD_ANVIL_APP_KEY | Yes | World Anvil API application key | |
| WORLD_ANVIL_USER_TOKEN | Yes | World Anvil user authentication token |
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 |
|---|---|
| get_api_statusB | Check World Anvil API connection status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_config_status | Expose server configuration status as a resource. Returns: JSON string with configuration details |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'get_api_status' has a clear, singular purpose of checking API connection status, so an agent cannot misselect between non-existent alternatives.
A single tool inherently has perfect naming consistency since there is nothing to compare it against. The tool name 'get_api_status' follows a clear verb_noun pattern, which would be consistent if more tools were added.
A single tool is too few for a server named 'World Anvil MCP Server', which suggests a broader domain like world-building or content management. This minimal toolset severely limits functionality and does not match the implied scope, making it inappropriate for typical agent workflows.
The tool surface is severely incomplete for the apparent domain. With only an API status check, there are obvious gaps in core operations such as creating, reading, updating, or deleting world-building content (e.g., articles, characters, timelines). This will cause agent failures as basic CRUD/lifecycle coverage is entirely missing.