Skip to main content
Glama
enesjakozh
orhanveli

OpenAPI Client Generator MCP

by orhanveli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

openapi-client-generator MCP サーバー

TypeScript を使用して API クライアントを生成するモデル コンテキスト プロトコル サーバー。

特徴

リソース

  • API と対話するために使用できる axios ベースの API クライアントを生成します。

  • OpenAPI / Swagger 仕様を使用してクライアントを生成します。

プロンプト

  • generate_client - 指定された OpenAPI 仕様の API クライアントを生成します。

Related MCP server: Emcee

発達

依存関係をインストールします:

npm install

サーバーを構築します。

npm run build

自動リビルドを使用した開発の場合:

npm run watch

インストール

Claude Desktop で使用するには、サーバー設定を追加します。

MacOSの場合: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows の場合: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "openapi-client-generator": {
      "command": "node",
      "args": [
        "< PATH TO >/openapi-client-generator/build/index.js"
      ]
    }
  }
}

デバッグ

MCPサーバーはstdio経由で通信するため、デバッグが困難になる場合があります。パッケージスクリプトとして提供されているMCP Inspectorの使用をお勧めします。

npm run inspector

インスペクターは、ブラウザでデバッグ ツールにアクセスするための URL を提供します。

貢献

ぜひ、問題を報告したり、プルリクエストを送信したりして、プロジェクトに貢献してください。プロジェクトの目標に沿った改善や新機能の提案は大歓迎です。

ライセンス

このプロジェクトは MIT ライセンスに基づいてライセンスされています - 詳細についてはLICENSEファイルを参照してください。

Clineで構築

Available Tools

1 tool
generate_clientB

Generate TypeScript API client from OpenAPI specification

ParametersJSON Schema
NameRequiredDescriptionDefault
inputYesURL or file path to OpenAPI specification
outputYesOutput directory for generated client
httpClientYesHTTP client to use (fetch or axios)

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden for behavioral traits. It does not disclose side effects (e.g., file creation, overwriting), dependencies (valid spec), permissions, or error conditions. This is a significant gap for a generation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, precise sentence with no wasted words. It is appropriately sized for a straightforward generation tool with three well-defined parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description is incomplete. It lacks details on what the generated client includes, whether existing files are overwritten, and any runtime behaviors. More context is needed for an AI agent to use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with parameter descriptions, satisfying the baseline. The tool description does not add any additional parameter semantics beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Generate'), the output ('TypeScript API client'), and the source ('from OpenAPI specification'). It is specific and distinguishes the tool from any potential siblings (none defined).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when or when not to use the tool. While there are no sibling tools, the description lacks context such as prerequisites (valid OpenAPI spec) or best practices for selecting the HTTP client.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedgenerate_client
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A3.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion. The tool has a clear and singular purpose.

Naming Consistency5/5

The single tool uses a clear verb_noun pattern ('generate_client'), which is consistent and descriptive.

Tool Count3/5

A single tool feels thin for an OpenAPI client generator. While it may suffice for a minimal use case, most users would expect additional capabilities like validation or endpoint listing.

Completeness2/5

The tool only generates a client from a specification. Obvious gaps include validating the spec, listing endpoints, or configuring output options, which limits its usefulness.

Resources

Related MCP Connectors

Related MCP Servers

  • MCP-OpenAPI

    rmasters
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that exposes HTTP methods defined in an OpenAPI specification as tools, enabling interaction with APIs via the Model Context Protocol.
    8
    MIT

  • OpenAPI to MCP Server

    jeweis
    A
    license
    Not graded
    quality
    D
    maintenance
    A service that converts OpenAPI specifications into MCP tools, enabling AI assistants to interact with your API endpoints through natural language.
    MIT

Appeared in Searches