by apimatic
Validates OpenAPI 2.0 and 3.0 specifications in JSON or YAML by leveraging APIMatic's API through a Model Context Protocol (MCP) server.
Apimatic Validator MCP Server provides a lightweight service that receives OpenAPI files, forwards them to APIMatic’s validation API, and returns a concise validation summary. It integrates with Claude Desktop (or any MCP‑compatible client) to enable on‑demand spec checking.
npm install.npm run build.claude_desktop_config.json (or similar MCP client) using the configuration below, supplying your APIMatic API key.Q: Do I need an APIMatic account? A: Yes, an APIMatic API key is required; obtain it from the APIMatic website.
Q: Which Node.js versions are supported? A: Node.js v18 or newer.
Q: Can I run the server locally without Claude Desktop?
A: Yes, you can invoke the built index.js directly with Node and feed it OpenAPI files via standard input or a custom client.
Q: How are validation results formatted? A: The server returns a summary object containing errors, warnings, and informational messages produced by APIMatic.
Q: Is there any cost to use the APIMatic validation API? A: APIMatic may have usage limits or pricing; check your APIMatic plan for details.
This repository provides a Model Context Protocol (MCP) Server for validating OpenAPI specifications using APIMatic. The server processes OpenAPI files and returns validation summaries by leveraging APIMatic’s API.
Ensure that Node.js v18+ is installed.
git clone https://github.com/apimatic/apimatic-validator-mcp.git
cd apimatic-validator-mcp
npm install
npm run build
To use the server, an APIMatic API key is required. Sign up at APIMatic and obtain the API key.
Modify the claude_desktop_config.json file to integrate the MCP server. If the file does not exist, create one in the following location:
code $env:AppData\Claude\claude_desktop_config.json
code ~/Library/Application\ Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"APIMatic": {
"command": "node",
"args": [
"C:\\PATH\\TO\\PARENT\\FOLDER\\build\\index.js"
],
"env": {
"APIMATIC_API_KEY": "<Add your APIMatic token here>"
}
}
}
}
Once configured, a hammer icon should appear in Claude Desktop. Open it to verify that the validate-openapi-using-apimatic tool is successfully integrated.
Please log in to share your review and rating for this MCP.
Explore related MCPs that share similar capabilities and solve comparable challenges
by headroomlabs-ai
Compress tool outputs, logs, files, RAG chunks, and conversation history before they reach the LLM, keeping answers identical while saving up to 95% of tokens for JSON payloads.
by modelcontextprotocol
A Model Context Protocol server for Git repository interaction and automation.
by zed-industries
A high‑performance, multiplayer code editor designed for speed and collaboration.
by modelcontextprotocol
Model Context Protocol Servers
by modelcontextprotocol
A Model Context Protocol server that provides time and timezone conversion capabilities.
by cline
An autonomous coding assistant that can create and edit files, execute terminal commands, and interact with a browser directly from your IDE, operating step‑by‑step with explicit user permission.
by upstash
Provides up-to-date, version‑specific library documentation and code examples directly inside LLM prompts, eliminating outdated information and hallucinated APIs.
by daytonaio
Provides a secure, elastic infrastructure that creates isolated sandboxes for running AI‑generated code with sub‑90 ms startup, unlimited persistence, and OCI/Docker compatibility.
by continuedev
Enables faster shipping of code by integrating continuous AI agents across IDEs, terminals, and CI pipelines, offering chat, edit, autocomplete, and customizable agent workflows.
{
"mcpServers": {
"apimatic-validator": {
"command": "node",
"args": [
"C:\\PATH\\TO\\PARENT\\FOLDER\\build\\index.js"
],
"env": {
"APIMATIC_API_KEY": "<YOUR_API_KEY>"
}
}
}
}claude mcp add apimatic-validator node C:\PATH\TO\PARENT\FOLDER\build\index.js