広告掲載
MCP.so
ログイン
O

OpenAPI Slice MCP Server

@vvarp

リポジトリ

基本情報

カテゴリ

その他

トランスポート

stdio

作者

vvarp

投稿者

Maciek Szczesniak

OpenAPI Slice MCP Server について

An MCP (Model Context Protocol) server that helps you work with large OpenAPI specifications by extracting only the relevant portions for specific endpoints. This is particularly useful when working with LLMs that have context limitations - instead of loading an entire large Open

#openapi

OpenAPI Slice MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "openapi-slice-mcp": {
      "command": "uvx",
      "args": [
        "openapi-slice-mcp"
      ]
    }
  }
}

OpenAPI Slice MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is OpenAPI Slice MCP?

OpenAPI Slice MCP is a Model Context Protocol server that extracts only the relevant portions of large OpenAPI specifications for specific endpoints. It helps developers and LLMs work with large specs by reducing context size through automatic dependency resolution, supporting both local files and remote URLs.

How to use OpenAPI Slice MCP?

Run the server with uvx openapi-slice-mcp. It communicates via STDIO and provides tools to load specs (from file or URL), list endpoints, extract endpoint slices, and check server status.

Key features of OpenAPI Slice MCP

  • Endpoint-specific extraction with automatic dependency resolution
  • Supports local YAML/JSON files and remote URLs (HTTP/HTTPS)
  • Output in YAML or JSON format
  • Discovery tool to list all endpoints in a loaded spec
  • Recursively includes all referenced components (schemas, parameters, etc.)

Use cases of OpenAPI Slice MCP

  • Extracting a minimal spec for a single API endpoint to fit within LLM context limits
  • Reducing token usage when sending OpenAPI definitions to AI assistants
  • Isolating endpoint definitions for testing or documentation generation

よくある質問

1

What makes OpenAPI Slice MCP different from loading the full spec?

It extracts only the requested endpoint and its dependencies, unlike loading the entire OpenAPI specification. This is especially useful when working with LLMs that have context limitations.

2

What are the runtime requirements?

The server is run via `uvx` (from the uv package manager) and requires Python. No additional dependencies are listed beyond those bundled in the package.

3

Where does the data live?

Specifications can be loaded from local files (YAML/JSON) or fetched from remote URLs. No data is persisted on the server beyond the currently loaded spec.

4

What transport and authentication does it use?

The server uses STDIO transport and does not mention any authentication mechanism. It is designed for local or trusted setups.

5

Can I get the output in different formats?

Yes, the `extract_endpoint_slice` tool accepts an `output_format` parameter that can be set to `"yaml"` (default) or `"json"`.

コメント

「その他」の他のコンテンツ

Klarix Intelligence Engine

Klarix

B2B competitive intelligence, live sales battlecards, 5-axis ICP prospect fit scoring, and tech stack teardowns over MCP and REST with cited public-web evidence.

Awesome Mlops

visenger

A curated list of references for MLOps

14.0K

Handl

Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.

Lemon.io

lemon-io

Request dedicated senior developers to work on your project, write job descriptions, and prep technical interviews — all without leaving your Claude chat. Just describe what you need, and Lemon.io MCP does the rest. 1–3

Sequential Thinking

modelcontextprotocol

Model Context Protocol Servers

88.2K
広告掲載