OpenAI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHONPATH | No | Path to your mcp-server-openai directory | |
| 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask-openaiC | Ask my assistant models a direct question |
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 one tool, there is no possibility of ambiguity or overlap between tools. The tool 'ask-openai' has a clear and singular purpose, making it impossible for an agent to misselect between tools.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'ask-openai' follows a verb_noun pattern, and with no other tools to compare against, there are no inconsistencies.
A single tool is generally too few for a server's purpose, as it limits functionality and scope. For an 'OpenAI MCP Server', one might expect more comprehensive coverage such as different model interactions, fine-tuning, or other API endpoints, making this feel thin and under-scoped.
The tool set is severely incomplete for an 'OpenAI MCP Server'. With only a direct question tool, it lacks essential operations like model listing, chat completions, embeddings, or file handling, which are core to OpenAI's API. This will likely cause agent failures due to missing functionality.