OpenAI Assistant MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHONPATH | No | The absolute path to the project directory | |
| OPENAI_API_KEY | Yes | Your OpenAI API key for authentication |
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 |
| list-assistantsB | List OpenAI assistants |
| retrieve-assistantC | Retrieve an OpenAI assistant by ID |
| create-assistantC | Create a new OpenAI assistant |
| update-assistantB | Update an existing OpenAI assistant |
| delete-assistantC | Delete an OpenAI assistant |
| upload-fileC | Upload a file for use by assistants |
| list-filesB | List files available for assistants |
| delete-fileC | Delete a file |
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 9 tools
Each tool has a clearly distinct purpose targeting specific resources and actions in the OpenAI Assistant domain. For example, list-assistants vs. retrieve-assistant for listing all vs. getting one by ID, and create-assistant vs. update-assistant vs. delete-assistant for full lifecycle management. No tools appear to overlap in functionality.
All tool names follow a consistent verb_noun pattern with hyphens, such as create-assistant, delete-assistant, list-assistants, and upload-file. The naming is uniform throughout, making it predictable and easy for agents to understand the action and target resource.
With 9 tools, this server is well-scoped for managing OpenAI assistants and related files. The count is appropriate, covering core operations like CRUD for assistants and file management without being overwhelming or too sparse. Each tool earns its place in the workflow.
The tool set provides complete coverage for the OpenAI Assistant domain, including full CRUD lifecycle for assistants (create, retrieve, update, delete, list) and file management (upload, list, delete). The ask-openai tool adds a direct interaction capability, ensuring no obvious gaps for agent workflows.