PluginBench
MCP Server
Active
MIT

OpenAI Tools MCP Server MCP Server

ai.com.mcp/openai-tools

Transform OpenAPI specs into MCP tools instantly—no rewrites, no parallel codebases.

RepositoryRegistry
How to choose

What this kind of tool is for

  • Hand your agent a structured way to call a model or an inference API.
  • Compare outputs from two different providers on the same prompt.
  • Wire retrieval, embeddings, or generation into an existing agent workflow.

How to compare servers like this

Provider coverage:
Match the tool's supported providers and models to the ones your project uses.
Cost exposure:
Model-backed tools spend real API budget; check how usage and limits are configured.
Maintenance signal:
The provider landscape shifts weekly; prefer tools updated within the last few months.
Config surface:
Prefer tools whose environment-variable or config keys are documented plainly.

This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.

What is the OpenAI Tools MCP Server MCP server?

HAPI MCP is a Headless API framework that automatically converts OpenAPI specifications into Model Context Protocol (MCP) tools, enabling AI agents to call your existing APIs without code changes. It keeps your API logic as the single source of truth while exposing tools to MCP clients like Claude and ChatGPT.

HAPI MCP bridges your REST APIs and OpenAPI specs directly to MCP clients by lifting API definitions into agent-ready tools. Instead of rewriting services or building sidecar servers, you point HAPI at your OpenAPI spec and get an MCP server that inherits your API's auth, validation, rate limits, and audit trails. Use it to make internal or third-party APIs accessible to AI agents and orchestration platforms.

How to install OpenAI Tools MCP Server

Copy-paste configuration for popular MCP clients.

transport: http
Config generated by PluginBench — verify against the source before use.
Environment / auth
  • Authorization
    required
    secret

    Bearer token for authenticating with the OpenAI API. Obtain via the OpenAI dashboard. https://platform.openai.com/api-keys

~/.cursor/mcp.json
JSON config
{
  "mcpServers": {
    "openai-tools": {
      "url": "https://openai-tools.run.mcp.com.ai/mcp"
    }
  }
}

Tools & capabilities

Tools this server exposes to the agent.

  • OpenAPI-to-MCP transformation — Automatically converts OpenAPI 3.0+ specifications into MCP tools with no code changes
  • Multi-client compatibility — Exposes tools to any MCP client: ChatGPT, Claude, QBot, chatMCP, and custom orchestrators
  • OrcA orchestration integration — Deterministic multi-tool task planning and execution without prompt chaining
  • runMCP serverless execution — Autoscaling MCP tool execution with cold-start speed and long-running support
  • OAuth 2.0 and credential management — Supports OAuth 2.0 Dynamic Client Registration and scoped credentials per tool

Use cases

  • Expose internal REST APIs to Claude and ChatGPT without building custom integrations
  • Turn Swagger/OpenAPI specs into AI-ready tools in under five minutes
  • Build agentic systems that call multiple APIs with deterministic orchestration via OrcA
  • Maintain a single API source of truth while serving both traditional clients and AI agents
  • Inherit API-layer security, rate limits, and audit logs automatically in MCP tools

OpenAI Tools MCP Server MCP server FAQ

What is the OpenAI Tools MCP Server?

It is a HAPI MCP instance focused on wrapping OpenAI's image and audio generation endpoints via the HAPI CLI, making them available as MCP tools to AI agents and clients.

Do I need to rewrite my API to use HAPI MCP?

No. HAPI MCP lifts your existing OpenAPI specs directly into MCP tools. Your auth, validation, and business rules remain unchanged.

Which MCP clients can use these tools?

Any MCP client: ChatGPT, Claude, QBot, chatMCP, and custom orchestrators. The tools are vendor-neutral by design.

How do I install and use it?

Install the HAPI CLI from the GitHub releases, point it at your OpenAPI spec with `hapi serve path/to/swagger.json --headless`, and connect any MCP client to the resulting server.

Is there a cost to use HAPI MCP?

HAPI MCP is open-source under the MIT License. The remote instance is available at https://openai-tools.run.mcp.com.ai/mcp; check runMCP for serverless execution pricing.

How does security and compliance work?

Your API remains the single source of truth. Policies, RBAC, rate limits, and audit logs flow through automatically; HAPI adds guardrails and observability for regulated environments.

README (reference)

Source of truth, from the repository.

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:

    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.

Related MCP servers

Transform OpenAPI specs into MCP tools instantly—no rewrites, no sidecar servers.

9
HTML
MIT
View repository →

Official MCP Registry: publish and discover MCP servers like an app store for AI agents.

7.3k
Go
View repository →

Search and discover Agent Skills — reusable AI agent capability packages — from the skills.sh registry.

21k
Python
Apache-2.0
View repository →

Turn Strava APIs into AI-ready MCP tools instantly with HAPI—no rewrites, just OpenAPI specs.

9
HTML
MIT
View repository →

One inbox for SMS and email: read threads, search, manage contacts, and send texts and emails.

COCompeller logo

Compeller

Maintained

Create and track AI music videos and audio-reactive visuals from songs.

1
MIT
View repository →