mcp-openai-extended
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | Yes | Your OpenAI API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| openai_chatC | Send messages to OpenAI using a specified model. Supports GPT-4o, o1, and GPT-5 series models. |
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 1 tool
With only a single tool, there is no possibility of misselection or overlap. The one tool's purpose is unambiguous.
openai_chat uses a clear, readable snake_case verb_noun convention that fits the provider prefix. With only one name there is no pattern to validate consistency against, so it cannot earn full marks.
A single tool is thin for a server explicitly branded as 'extended' with multi-model support. The count is defensible for a minimal chat wrapper but feels under-scoped for the stated purpose.
Core chat completion is covered, but obvious companions are missing: model listing/discovery, conversation or state management, and other OpenAI surfaces implied by 'extended'. Agents can do basic work but hit dead ends beyond a single completion call.