OpenAI Tools MCP Server

ai.com.mcpPublished by mcp.com.aiOfficial publisherv0.6.0Updated Oct 24, 2026

Focused MCP server for OpenAI image/audio generation (v2.0.0). Wraps endpoints via HAPI CLI.

VerifiedStreamable HTTPWeb executableMedia & DesignAI & ML

Overview

AI-generated overview

A remote MCP server that exposes OpenAI image, audio, model and moderation endpoints as tools for an assistant.

What you can do
Generate images from prompts, edit or extend an existing image, and create variations of an image. Transcribe audio into its input language or translate audio into English. List and retrieve available models, and delete a fine-tuned model. Classify text against OpenAI's content policy with moderation.
When to use it
Useful when you want an assistant to produce or edit images, transcribe or translate audio, check text against OpenAI's content policy, or inspect and manage OpenAI models without writing API calls yourself.
Requirements
A remote endpoint reached over streamable HTTP. A bearer token in the Authorization header is required; the token is an OpenAI API key obtained from the OpenAI dashboard. Network access to the endpoint and to OpenAI is implied.
Before you install
The Authorization header carries an OpenAI API key, which is billed per use; image, audio and moderation calls consume paid quota. deleteModel permanently removes a fine-tuned model and requires the Owner role in the organization. Prompts, images and audio are sent to OpenAI and to the remote endpoint operator.

Installation

In SourceWeft

  1. Open OpenAI Tools MCP Server in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.com.mcp%2Fopenai-tools/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "openai-tools": {
      "type": "http",
      "url": "https://openai-tools.run.mcp.com.ai/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

HAPI MCP – Headless API for Model Context Protocol

Stop rewriting systems for AI. Instantly turn your APIs into MCP servers.

HAPI MCP lifts your OpenAPI catalog into MCP tools automatically, keeping design (OAS/Arazzo) and runtime (agents/LLMs) cleanly separated. Your existing APIs become AI-ready tools—no new business logic, no sidecar servers, no rework.

Key Features

  • No rewrites: Reuse 100% of your API logic. OpenAPI in, MCP tools out. No parallel codebase or shadow services.
  • Faster time-to-value: Turn specs into agent-ready tools in minutes. Update the spec, ship new tools instantly.
  • Reduced risk: Permissions, auth, rate limits, auditability are inherited from your APIs—governance without bolt-ons.
  • Scales with you: runMCP delivers serverless-like elasticity with long-running when needed. Cold-start fast, stay warm for throughput.
  • Deterministic orchestration: OrcA plans and executes multi-tool tasks predictably—no brittle prompt chaining.
  • Vendor-neutral: Works with any MCP client: ChatGPT, Claude, QBot, chatMCP. OAS + MCP + Arazzo stay portable.

How It Works

  1. Pick your API spec

    • OpenAPI, Swagger, REST—HAPI CLI works with any API specification format.
    • Supports OpenAPI 3.0+, REST APIs, OAuth 2.0 Dynamic Client Registration.

  2. Run a single command

    • One simple CLI command transforms your API into a usable MCP Server.
    • No complex setup, zero configuration, works anywhere, cross-platform.

  3. Use instantly

    • Your API is now ready as a tool, AI agent, or testing interface.
    • MCP server ready, AI agent compatible, testing interface, developer experience friendly.

Visual Pipeline

API Spec (swagger.json) → HAPI CLI → Usable Tool (AI-ready) ← MCP Clients
[ OpenAPI / Swagger ]       [ HAPI CLI ]        [ MCP Server ]       (Your API)         →   (Transform)   →   (Usable Tool)                                                 ↑          ↑                                                 |          |                                          [ ChatGPT ]  [ runMCP ]                                          [ Claude  ]  [ OrcA   ]                                          [ QBot    ]  [ chatMCP]                                          [ Agents  ]

Who Wins With HAPI

  • Executives: Ship AI initiatives without ballooning cost. Keep teams focused on outcomes, not rewrites and integration sprawl.
  • Architects & PMs: Design with OpenAPI/Arazzo, run with MCP. Clear contracts, policy inheritance, and versioned workflows keep risk low.
  • Engineers & Ops: Deploy once. HAPI Server + runMCP scale tools; QBot/chatMCP give fast feedback; OrcA keeps executions deterministic.

Your Stack, Already Wired

  • HAPI Server: Turns OpenAPI into MCP tools automatically—contracts stay in sync with your source of truth.
  • runMCP: Autoscaling execution and testing for MCP tools; cold-start fast, stay warm when workflows run long.
  • QBot: CLI TUI for power users to interact with MCP tools directly from terminal or scripts.
  • chatMCP: Conversational client that speaks MCP natively for support, ops, and internal assistants.
  • OrcA: Deterministic planning and orchestration for multi-tool tasks; no brittle prompt spaghetti.
  • Agents: Build agentic systems from standard APIs—no custom glue. Connect MCP clients across platforms.

Demos

Documentation

FAQ

  • Do we need to rewrite our services?
    No. HAPI MCP lifts your existing OpenAPI specs directly into MCP tools. Your auth, validation, and business rules remain unchanged.

  • Is this just another MCP server?
    It’s the Headless API model: your API becomes the runtime. HAPI Server reflects it as MCP; runMCP scales it; OrcA orchestrates it. No duplicate logic.

  • Which clients can consume the tools?
    Any MCP client: ChatGPT, Claude, QBot, chatMCP, bespoke orchestrators—vendor-neutral by design.

  • How do we keep control and compliance?
    Your API remains the single source of truth. Policies, RBAC, rate limits, and audit logs flow through automatically; no shadow logic.

  • What about security and privacy?
    Scoped credentials, per-tool permissions, and auditable calls are inherited from your API layer. HAPI adds guardrails and observability for regulated environments.

  • How fast can we get started?
    You can transform your first API into an MCP tool in less than five minutes. The HAPI CLI makes it quick and painless.

Get Started

  1. Install HAPI CLI from latest release: https://github.com/la-rebelion/hapimcp/releases

  2. Transform your OpenAPI spec into an MCP server with a single command:

    bash
    hapi serve path/to/your/swagger.json --headless

  3. Start using your MCP tools with any compatible client!

  4. Explore the documentation for advanced usage and best practices.

Contributing

Contributions are welcome! Open a discussion or submit a pull request on GitHub: https://github.com/la-rebelion/hapimcp

License

HAPI MCP is licensed under the MIT License. See LICENSE for details.

Source: README.md at commit 1873ff7

Tools

9

createImage

Creates an image given a prompt.

ParameterscreateImageBodyrequiredx-hapi-auth-state

createImageEdit

Creates an edited or extended image given an original image and a prompt.

Parametersx-hapi-auth-statecreateImageEditBodyrequired

createImageVariation

Creates a variation of a given image.

Parametersx-hapi-auth-statecreateImageVariationBodyrequired

createTranscription

Transcribes audio into the input language.

Parametersx-hapi-auth-statecreateTranscriptionBodyrequired

createTranslation

Translates audio into English.

Parametersx-hapi-auth-statecreateTranslationBodyrequired

listModels

Lists the currently available models, and provides basic information about each one such as the owner and availability.

Parametersx-hapi-auth-state

retrieveModel

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

Parametersmodelrequiredx-hapi-auth-state

deleteModel

Delete a fine-tuned model. You must have the Owner role in your organization.

Parametersmodelrequiredx-hapi-auth-state

createModeration

Classifies if text violates OpenAI's Content Policy

Parametersx-hapi-auth-statecreateModerationBodyrequired

Version history

1
  1. v0.6.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts