FastAPI OpenAPI 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_endpointsC | 高级搜索 API 接口，支持关键词、正则表达式、标签、方法等多种搜索方式 |
| generate_examplesC | 根据 OpenAPI 规范生成各种格式的 API 调用示例 |
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 2 tools
The two tools have clearly distinct purposes: one generates API call examples from an OpenAPI spec, while the other searches API endpoints with various filters. There is no overlap in functionality, making it easy for an agent to select the correct tool.
Both tools follow a consistent verb_noun naming pattern (generate_examples and search_endpoints), using snake_case throughout. The verbs 'generate' and 'search' clearly indicate their actions, maintaining a predictable and readable convention.
With only 2 tools, the server feels thin for a FastAPI OpenAPI MCP server, which typically involves more operations like validating specs, listing endpoints, or generating documentation. This limited set may not cover the full scope expected for such a domain.
The tool surface has significant gaps for an OpenAPI-focused server. Missing are core operations such as retrieving or parsing the OpenAPI spec, validating endpoints, or generating documentation. While the existing tools are useful, they do not provide a complete workflow for interacting with OpenAPI specifications.