OpenAI Tools MCP Server

ai.com.mcp由 mcp.com.ai 發布官方發布者v0.6.0更新於 Oct 24, 2026

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

已驗證Streamable HTTP可網頁執行媒體與設計AI 與機器學習

概覽

AI 產生的概覽

遠端 MCP 伺服器,將 OpenAI 的影像、音訊、模型與審核端點包裝成工具,供助理呼叫。

可以做什麼
依提示詞產生影像、編輯或延伸既有影像,並產生影像變體。將音訊轉錄為原始語言,或把音訊翻譯成英文。列出並查詢可用模型,刪除微調模型。以審核工具判斷文字是否違反 OpenAI 內容政策。
適用情境
適合想讓助理產生或編輯影像、轉錄或翻譯音訊、檢查文字是否符合 OpenAI 內容政策,或檢視與管理 OpenAI 模型,而不必自行撰寫 API 呼叫的情境。
執行需求
透過 streamable HTTP 存取的遠端端點。需在 Authorization 標頭提供 bearer 權杖,即從 OpenAI 主控台取得的 OpenAI API 金鑰。需要能連線至該端點與 OpenAI 的網路。
安裝前請注意
Authorization 標頭攜帶 OpenAI API 金鑰,依用量計費;影像、音訊與審核呼叫會消耗付費額度。deleteModel 會永久刪除微調模型,且需要組織內的 Owner 角色。提示詞、影像與音訊會傳送給 OpenAI 以及遠端端點的營運方。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 OpenAI Tools MCP Server,將其新增到工作區。
  2. 連接 Authorization token 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/ai.com.mcp%2Fopenai-tools/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "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.

來源:README.md,提交 1873ff7

工具

9

createImage

Creates an image given a prompt.

輸入參數createImageBody必填x-hapi-auth-state

createImageEdit

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

輸入參數x-hapi-auth-statecreateImageEditBody必填

createImageVariation

Creates a variation of a given image.

輸入參數x-hapi-auth-statecreateImageVariationBody必填

createTranscription

Transcribes audio into the input language.

輸入參數x-hapi-auth-statecreateTranscriptionBody必填

createTranslation

Translates audio into English.

輸入參數x-hapi-auth-statecreateTranslationBody必填

listModels

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

輸入參數x-hapi-auth-state

retrieveModel

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

輸入參數model必填x-hapi-auth-state

deleteModel

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

輸入參數model必填x-hapi-auth-state

createModeration

Classifies if text violates OpenAI's Content Policy

輸入參數x-hapi-auth-statecreateModerationBody必填

版本歷史

1
  1. v0.6.0最新Sep 16, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分