Skip to content
AI & MLQuality Score: 34

OpenAI API MCP Configuration

The OpenAI API MCP configuration provides a hosted JSON schema that connects AI assistants — including Claude Desktop, Cursor, Windsurf, and VS Code Copilot — to the OpenAI API API via the Model Context Protocol. This configuration maps 10 API endpoints as callable tools, including Answers the specified question using the provided documents and examples. The endpoint first [searches](/docs/api-reference/searches) over provided documents or files to find relevant context. The relevant context is combined with the provided examples and question to create the prompt for [completion](/docs/api-reference/completions). , Transcribes audio into the input language., Translates audio into into English., and more. No authentication credentials are needed — it works out of the box. The configuration is auto-generated from the OpenAI API OpenAPI specification (v1.2.0) and has a quality score of 34/99 (fair documentation coverage). Use the hosted URL below to auto-load this schema into any compatible MCP client.

Quick Specs Reference

AuthenticationNo Auth Required
Available Endpoints10 tools mapped
Integration Modeauto Generation

Hosted Config URL

Use this hosted URL in any client that supports remote MCP schema auto-loading.

https://mcpbridge.org/config/openai-com.json

One-Click Client Setup

Copy the configurations below to wire your local coding assistant directly.

Claude Desktop

claude_desktop_config.json
{
  "mcpServers": {
    "openai-com": {
      "command": "npx",
      "args": [
        "-y",
        "@mcp/openai-com"
      ],
      "env": {
        "OPENAI_API_API_KEY": "your_openai_api_api_key"
      }
    }
  }
}

Cursor & VS Code

MCP Server URL Setup
{
  "mcpServers": {
    "openai-com": {
      "url": "https://mcpbridge.org/config/openai-com.json"
    }
  }
}

Raw Configuration JSON

For local command line wrappers or dynamic shell bindings.

{
  "mcpServers": {
    "openai-com": {
      "command": "npx",
      "args": ["-y","@mcp/openai-com"],
      "env": {
      "OPENAI_API_API_KEY": "your_openai_api_api_key"
}
    }
  }
}

Required Environment Keys

Substitute these secrets inside your configuration directory environment definitions.

OPENAI_API_API_KEY
Replace your_openai_api_api_key with your secret key credential

Mapped Web APIs & Tools

The following routes will be exposed directly as protocol tools for the LLM.

POST/answers

Answers the specified question using the provided documents and examples. The endpoint first [searches](/docs/api-reference/searches) over provided documents or files to find relevant context. The relevant context is combined with the provided examples and question to create the prompt for [completion](/docs/api-reference/completions).

POST/audio/transcriptions

Transcribes audio into the input language.

POST/audio/translations

Translates audio into into English.

POST/chat/completions

Creates a completion for the chat message

POST/classifications

Classifies the specified `query` using provided examples. The endpoint first [searches](/docs/api-reference/searches) over the labeled examples to select the ones most relevant for the particular query. Then, the relevant examples are combined with the query to construct a prompt to produce the final label via the [completions](/docs/api-reference/completions) endpoint. Labeled examples can be provided via an uploaded `file`, or explicitly listed in the request using the `examples` parameter for quick tests and small scale use cases.

POST/completions

Creates a completion for the provided prompt and parameters

POST/edits

Creates a new edit for the provided input, instruction, and parameters.

POST/embeddings

Creates an embedding vector representing the input text.

GET/engines

Lists the currently available (non-finetuned) models, and provides basic information about each one such as the owner and availability.

GET/engines/{engine_id}

Retrieves a model instance, providing basic information about it such as the owner and availability.

Similar Configurations

OpenAI API

Generate text, images, and embeddings. Integrate GPT models and DALL-E into your AI agent.

https://mcpbridge.org/config/openai.json

Anthropic API

Access Claude AI models for text generation, analysis, and code assistance through the Anthropic API.

https://mcpbridge.org/config/anthropic.json

Amazon CodeGuru Profiler

Amazon CodeGuru Profiler is an advanced application performance profiling service provided by Amazon Web Services (AWS). It continuously collects runtime performance data—such as CPU utilization, memory allocation, and thread contention—from live production applications, then analyzes this data using machine learning algorithms to pinpoint performance bottlenecks and inefficiencies. The API serves as the programmatic interface for managing the profiling lifecycle, allowing developers to create and configure profiling groups, adjust agent settings, retrieve performance metrics and findings, and manage notification configurations. Enterprise use cases include optimizing microservice latency in high-traffic systems, reducing cloud compute costs by identifying inefficient code paths, and maintaining application health in continuous deployment pipelines where performance regressions must be detected early. For development teams, it provides actionable insights to guide code optimization efforts based on real-world usage rather than synthetic benchmarks. When exposed as tools via the Model Context Protocol (MCP) to AI coding assistants such as Claude Desktop or Cursor, the CodeGuru Profiler API unlocks a powerful paradigm where an AI agent can directly interact with live performance telemetry. The primary value lies in enabling the AI to contextualize code suggestions with actual runtime behavior. Instead of analyzing static code alone, the AI can query the latest profiling data to understand which functions are consuming the most resources under real load, validate whether a suggested refactor addresses a genuine bottleneck, or even predict the performance impact of a proposed change. This transforms the assistant from a generic code generator into a performance-aware partner, capable of providing recommendations that are not just syntactically correct but are also optimized for the specific performance profile of the deployed application. In a practical workflow, a developer could instruct their AI agent to perform dynamic, performance-informed tasks. For example, the AI could use the GET /profilingGroups/{profilingGroupName} endpoint to retrieve the current status and ARN of a profiling group, then use POST /profilingGroups/{profilingGroupName}/configureAgent to dynamically update agent configuration parameters (like sampling intervals) in response to a detected performance anomaly. An AI agent could query GET /internal/findingsReports to pull the latest list of performance findings, analyze the patterns, and then generate a pull request with code fixes targeted at the top recommendations. Furthermore, the agent could automate notification setup by using POST /profilingGroups/{profilingGroupName}/notificationConfiguration to ensure the team is alerted when CPU utilization exceeds a threshold identified through previous profiling data, creating a closed-loop system for performance management. Developers integrating this API via an MCP server must adhere to critical security and configuration practices. Although the listed authentication is "None," the API fundamentally requires AWS Identity and Access Management (IAM) credentials for all calls, as it is an AWS service. The authentication method "None" in this context likely refers to the lack of a separate API key system, relying instead on standard AWS SigV4 signing. Therefore, security best practices are paramount: apply the principle of least privilege by granting the AI's execution environment only the specific CodeGuru Profiler permissions needed (e.g., profiler:DescribeProfilingGroups, profiler:GetFindingsReport), and avoid wildcard permissions. Credentials should be securely managed via environment variables or an AWS role, never hard-coded. Network security should ensure the AI tool operates within a controlled environment (like a VPC or with strict egress rules) to prevent unauthorized data exfiltration, and all API interactions should be logged and audited for compliance.

https://mcpbridge.org/config/amazonaws-com-codeguruprofiler.json

Amazon CodeGuru Reviewer

The Amazon CodeGuru Reviewer API is a powerful programmatic interface to Amazon's automated code analysis service, designed to elevate code quality and developer productivity. This API exposes the core functionalities of a managed service that combines deep static analysis, machine learning models trained on vast code repositories, and pattern recognition to identify complex defects, security vulnerabilities, and non-idiomatic code patterns that are often missed in manual reviews. Specifically targeting Java and Python codebases, CodeGuru Reviewer analyzes code changes submitted through integrated repositories like AWS CodeCommit, GitHub, or Bitbucket, and generates actionable recommendations. Its primary enterprise use cases are integrated into continuous integration and continuous delivery (CI/CD) pipelines for automated, mandatory code quality gates; conducting security and compliance audits on critical application code; and providing scalable, consistent feedback during the pull request process, thereby reducing the burden on human reviewers and accelerating safe code deployments. When exposed as tools via the Model Context Protocol (MCP) to an AI coding assistant such as Claude Desktop, Cursor, or Cline, this API becomes a force multiplier for AI-driven development workflows. The AI agent gains the ability to not only understand code but to actively invoke professional-grade quality assurance services. Instead of the developer manually switching context to a web console, the AI can be directly instructed to perform sophisticated, context-aware actions. This integration transforms the AI from a code generation helper into a comprehensive code lifecycle manager. The agent can programmatically create and monitor code reviews, retrieve specific line-level recommendations with their explanations, and even manage the feedback loop by reading or submitting developer responses to those recommendations, all through natural language commands within the coding environment. A developer can instruct the AI agent to execute a variety of dynamic, high-value tasks. For example, a command like "Analyze the recent changes in my repository for security issues" would trigger the agent to use the POST /codereviews endpoint to initiate a review on the latest commit or pull request, and then use GET /codereviews/{CodeReviewArn}/Recommendations to fetch and summarize the findings. The agent can be tasked with "Fetch all unresolved 'Critical' recommendations from the last three reviews on this file," which would involve querying GET /codereviews#Type to list recent reviews, filtering by status, and then aggregating recommendations from each. Furthermore, it can automate feedback tracking: "Update the feedback on this recommendation to 'acknowledged' since we've decided to address it in the next sprint," which the agent would accomplish via POST /feedback/{CodeReviewArn}#RecommendationId. These interactions create a seamless bridge between the AI's understanding of the code and the external, authoritative source of truth for its quality. Critical to setting up this API integration is acknowledging the security model. While the described API documentation reference indicates no built-in authentication, accessing the real Amazon CodeGuru Reviewer API requires secure AWS credentials. A dedicated IAM user or role with the least-privilege policy—granting only the specific CodeGuru Reviewer permissions needed (e.g., codeguru-reviewer:CreateCodeReview, codeguru-reviewer:GetCodeReview)—must be configured. These credentials (Access Key ID and Secret Access Key) should be securely managed in the AI tool's environment variables or secret store, never hardcoded. The AI assistant's MCP server implementation must be designed to handle these credentials securely, using them to sign requests via AWS Signature Version 4. Developers must also ensure the AWS region is correctly specified, as CodeGuru Reviewer is a regional service, and they should be mindful of potential costs associated with API calls and analyzed lines of code when enabling automated, large-scale reviews.

https://mcpbridge.org/config/amazonaws-com-codeguru-reviewer.json