"Overview of Command Line Interface Usage" matching MCP servers:

A Model Context Protocol server that allows AI development tools like Cursor and Claude Desktop to retrieve detailed YAPI interface information by interface ID.

This server automatically validates consistency between AI-generated frontend and backend code by enforcing OpenAPI 3.0 specifications. It injects smart constraints into AI prompts to ensure that generated data structures and API calls remain synchronized across the entire stack.

MCP server for the Clash of Clans API. Can get player, clan information, analyze ongoing wars, as well as war logs (provided they are public).

An MCP server for the YAPI interface management platform that enables users to manage projects, categories, and API interfaces. It supports querying project details, listing interfaces, and creating or modifying API documentation through natural language.

Enables users to search, compare, and retrieve detailed information about World of Warships ships using the official Wargaming.net API. Supports filtering by nation, type, and tier with multi-language support and intelligent caching.

Enables LLMs to make HTTP requests with OAuth2, session cookies, retry logic, and cURL command generation, while providing security features like SSRF protection and TLS enforcement.

Parses Swagger 2.0 and OpenAPI 3.x specifications, exposing API endpoints, schemas, and authentication through MCP tools with local caching to reduce token usage.

Optimizes REST API calls for AI agents by returning compact schemas instead of full responses, allowing agents to fetch only needed fields via jq masks, reducing token consumption by up to 50x.

An MCP server for Tern that enables the generation, verification, and management of webhook handlers across over 16 platforms and various frameworks. It provides tools to create verified endpoints, debug signature failures, and manage failed event replays via dead letter queues.

Enables AI assistants to interact with Fastly's CDN API through the Model Context Protocol, allowing secure management of CDN services, caching, security settings, and performance monitoring without exposing API keys.

Enables testing and validation of APIs for AI agent compatibility, providing scores, grades, and actionable recommendations.

A Model Context Protocol (MCP) server for authenticated REST APIs. Drop it into any project, point it at your API, and let AI agents call endpoints — with auto-login, 2FA support, Swagger spec fetch, and fuzzy endpoint search — all without writing a single line of auth code.

Turn any OpenAPI spec into MCP tools for Claude — instantly. Point mcp-openapi at any OpenAPI 3.x spec and Claude can call every endpoint through natural language. No custom integration code. No manual tool definitions. One line of config.

Enables searching YApi interfaces by keyword and retrieving detailed interface schemas, including request/response, for project-level tokens.

A comprehensive suite of HTTP and API testing tools that enables AI agents to perform requests, check endpoint health, and decode JWTs. It also provides utilities for URL parsing and detailed security analysis of HTTP response headers.

Discovers, inspects, and executes requests against OpenAPI or Swagger APIs directly from documentation URLs or specification files. It enables users to trace parameter usage across an API and perform authenticated HTTP requests through a structured toolset.

A server that enables management of ApiPost API documentation and team collaboration through the Model Context Protocol, supporting complete interface management directly from compatible editors.

Create Hooks: Create new webhooks or MQTTHOOKS directly from your agent. List Hooks: Retrieve a list of your configured webhooks. Inspect Events: View

Enables AI assistants to access and search RAP2 API documentation, allowing users to query interface details, search APIs by keywords, and retrieve repository interfaces through natural language.

A Model Context Protocol server that creates tools from API configurations defined in YAML files, allowing easy integration of external APIs into an MCP ecosystem without coding.