GPT-5 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENV_FILE | No | Path to .env file for loading environment variables | |
| OPENAI_MODEL | No | The OpenAI model to use | gpt-5 |
| OPENAI_API_KEY | Yes | Your OpenAI API key (required) | |
| REASONING_EFFORT | No | Default reasoning effort level (low|minimal|medium|high) | medium |
| DEFAULT_VERBOSITY | No | Default verbosity level (low|medium|high) | medium |
| OPENAI_TIMEOUT_MS | No | Timeout for OpenAI API calls in milliseconds | 60000 |
| OPENAI_MAX_RETRIES | No | Maximum number of retries for OpenAI API calls | 3 |
| WEB_SEARCH_CONTEXT_SIZE | No | Default web search context size (low|medium|high) | medium |
| WEB_SEARCH_DEFAULT_ENABLED | No | Whether web search is enabled by default (true|false) | false |
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 |
|---|---|
| gpt5_queryC | Query GPT-5 with optional Web Search Preview. Supports verbosity and reasoning effort. |
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 single tool 'gpt5_query' has a clear and distinct purpose, making it impossible for an agent to misselect between tools.
The naming is trivially consistent as there is only one tool. It follows a clear verb_noun pattern ('gpt5_query'), and with no other tools to compare, there are no deviations or inconsistencies in naming conventions.
A single tool is generally too few for most server purposes, as it limits functionality and flexibility. For a server named 'GPT-5 MCP Server', which suggests a domain of AI querying and interaction, having only one tool feels thin and under-scoped, potentially causing agents to lack necessary operations.
The tool surface is severely incomplete for the inferred domain of AI querying. While 'gpt5_query' handles queries, there are obvious gaps such as no tools for managing conversations, handling different models, or performing related tasks like summarization or translation, which are typical in such domains.