Skip to main content
Glama
APIMatic Validator MCP Server

APIMatic Validator MCP Server

Official
by apimatic

APIMatic Validator MCP Server

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.

Features

  • Validates OpenAPI 2.0 and 3.0 files

  • Uses APIMatic’s API for comprehensive validation

  • Supports both JSON and YAML formats

  • Implements Model Context Protocol (MCP) for seamless integration

Related MCP server: MCP Gatekeeper

Installation

Ensure that Node.js v18+ is installed.

Clone the Repository

git clone https://github.com/apimatic/apimatic-validator-mcp.git
cd apimatic-validator-mcp

Install Dependencies

npm install

Build the Project

npm run build

Configuration

To use the server, an APIMatic API key is required. Sign up at APIMatic and obtain the API key.

image

Integration with Claude Desktop

Modify the claude_desktop_config.json file to integrate the MCP server. If the file does not exist, create one in the following location:

Windows

code $env:AppData\Claude\claude_desktop_config.json

macOS/Linux

code ~/Library/Application\ Support/Claude/claude_desktop_config.json

Add the MCP Server to the Configuration

{
    "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.

Usage

  1. Add an OpenAPI file.

  2. Provide a prompt to validate it.

  3. The validation results will be returned.

APIMatic MCP Server For OpenAPI Validation.webm

Available Tools

1 tool
validate-openapi-using-apimaticC

Get validation summary for your OpenAPI spec using APIMatic

Inputs: openApiFile (required), isYaml (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name follows a clear verb-noun pattern (validate-openapi-using-apimatic).

    Tool Count2/5

    A single tool is too few for a server focused on OpenAPI validation, as it lacks coverage for related operations like detailed error reporting, schema linting, or batch validation. This minimal set limits agent workflows and feels incomplete for the domain.

    Completeness2/5

    The tool surface is severely incomplete for OpenAPI validation. It only provides a summary validation, missing essential functions such as retrieving detailed validation errors, checking specific API endpoints, or supporting different OpenAPI versions, which are common needs in this domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers