A
licenseB
qualityD
maintenanceProvides tools to manage OpenAI API keys and spending through the OpenAI API. Requires an OpenAI admin API key for secure access to account management features.
2
MIT
openai-workspace-mcp
by MSPbotsAI
Related Servers
Alternatives to openai-workspace-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceFull coverage of Anthropic Admin API to manage organization, workspaces, members, API keys, usage, and costs via natural language from any MCP client.21MIT
- FlicenseNot gradedqualityDmaintenanceExposes LiteLLM Proxy admin APIs as MCP tools for managing internal users, virtual keys, and spend logs via streamable-http, enabling agents to administer LiteLLM without custom HTTP glue.1-
- FlicenseBqualityDmaintenanceEnables interaction with OpenAI's Chat Completion and Assistants APIs, supporting assistant management, file operations, and direct queries to GPT models through standardized MCP tools.92-
- AlicenseNot gradedqualityDmaintenanceProvides tools to interact with OpenAI API including chat completions, embeddings, content moderation, and file management through natural language.MIT
- FlicenseNot gradedqualityCmaintenanceA local MCP server exposing the OpenAI platform REST API as tools for file management, fine-tuning, inference, images, audio, batch processing, and organization usage/costs.-
TDQS
A3.8/5.0
Scored across 31 tools
Disambiguation4/5
Each tool targets a distinct resource/action pair, and the descriptions are clear. A few similarly named tools (e.g., update_project_user_role vs update_user_role, add_project_user vs invite_user) could cause misselection, but their scopes are still distinguishable.
Naming Consistency4/5
The openai_ prefix and a general verb_noun pattern are consistently used. Minor deviations like mixing 'remove' and 'delete' for destructive actions, and 'invite_user' instead of 'create_invite', prevent a perfect score.
Tool Count2/5
At 31 tools, the set exceeds the 'too many' threshold of 25. While the broad domain explains the number, the granularity feels heavy and could have been consolidated (e.g., fewer separate get/list operations).
Completeness4/5
The surface nearly covers all management workflows for projects, users, invites, service accounts, API keys, rate limits, audit logs, usage, and costs. Notable gaps are a standalone API key creation tool and unarchiving projects, but these are edge cases rather than major holes.
Maintenance
ActivitySlowing
ResponsivenessNo issues