fluent-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_helpA | Find ANSYS Fluent documentation URLs for your query. This tool helps you navigate to the right online documentation. Use WebFetch to retrieve the actual content from the returned URLs. Args: query: Search term (e.g., "flamelet model", "read case", "turbulence") max_suggestions: Maximum manual section suggestions to return (default: 3) Returns: URLs and navigation hints for finding the documentation |
| list_topicsA | List common Fluent topics with quick documentation links. Returns: List of pre-mapped topics for faster navigation |
| get_manual_linkA | Get direct link to a specific Fluent manual or section. Args: manual: Manual name (user_guide, tui, theory, udf) section: Optional section path (e.g., "turbulence", "file/read-case") Returns: Direct URL to the manual or section |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_online_docs_info | Provide information about ANSYS Fluent online documentation. Returns: Guide for accessing official ANSYS Fluent documentation |
TDQS
Scored across 3 tools
Each tool has a clear, distinct purpose: get_manual_link fetches a direct link to a specific manual section, list_topics provides pre-mapped common topics, and search_help performs general searches. No overlap in functionality.
All tool names follow a consistent verb_noun pattern: get_manual_link, list_topics, search_help. The naming is predictable and readable.
With 3 tools, the set is compact but covers the essential operations for Fluent documentation access: direct linking, topic listing, and search. This count is appropriate for a focused server, though slightly lower than typical ranges.
The tools cover the main use cases for finding documentation: specific manual links, common topics, and free-text search. Minor gaps like browsing by category or full table of contents are acceptable for the scope.