MSFS SDK 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 |
|---|---|
| search_msfs_docsC | Search MSFS SDK documentation for specific topics |
| get_doc_contentC | Get detailed content from a specific MSFS SDK documentation page |
| list_categoriesB | List all available MSFS SDK documentation categories |
| natural_language_queryC | Process natural language queries like "Search livery op msfs sdk" |
| list_category_itemsC | Returns all items for a given documentation category |
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 5 tools
Most tools have distinct purposes: get_doc_content retrieves specific pages, list_categories and list_category_items handle hierarchical browsing, and search_msfs_docs performs keyword searches. However, natural_language_query overlaps with search_msfs_docs as both handle search-like functionality, which could cause minor confusion for an agent.
All tool names follow a consistent snake_case pattern with clear verb_noun structures (e.g., get_doc_content, list_categories, search_msfs_docs). The naming is predictable and readable throughout the set.
With 5 tools, this server is well-scoped for its purpose of accessing MSFS SDK documentation. Each tool serves a distinct role in browsing, retrieving, and searching documentation, making the count appropriate and manageable.
The tool set covers core documentation access needs: browsing categories, listing items, retrieving content, and searching. A minor gap exists in update or management operations, but this is reasonable for a read-only documentation server, and agents can work effectively with the provided tools.