OpenAPI Sync MCP
Generates fully-typed Axios API clients from OpenAPI specifications, enabling type-safe HTTP requests and responses.
Generates fully-typed Fetch clients for Next.js applications from OpenAPI specifications, enabling type-safe data fetching.
Generates fully-typed React Query hooks and clients from OpenAPI specifications, enabling type-safe data fetching and server-state management.
Generates fully-typed SWR hooks from OpenAPI specifications, enabling type-safe data fetching and caching.
Generates Zod schemas from OpenAPI specifications for runtime validation, preserving constraints and ensuring runtime type safety.
OpenAPI Sync
OpenAPI Sync is a powerful developer tool that automates the synchronization of your API documentation with your codebase using OpenAPI (formerly Swagger) specifications. It generates TypeScript types, fully-typed API clients (Fetch, Next.js Fetch, Axios, React Query, SWR, RTK Query), endpoint definitions, runtime validation schemas (Zod, Yup, Joi), and comprehensive documentation from your OpenAPI schemaβensuring type safety from API specification through client implementation to runtime validation.
Core Features
β‘ Zero-Config Presets - 10 pre-configured framework presets (React Query, SWR, Axios, Fetch, RTK Query, Next.js, Python) for instant setup
π Real-time API Synchronization - Automatically syncs OpenAPI specs from remote URLs with configurable intervals
π Automatic Type Generation - Generates TypeScript interfaces for all endpoints with full nested support
π Runtime Validation - Generate Zod, Yup, or Joi schemas from OpenAPI specs with all constraints preserved
π― Interactive Setup Wizard - Streamlined configuration with auto-enabled tag-based folder splitting
π‘οΈ Enterprise Ready - Error handling, validation, state persistence, and custom code preservation
π¦ Folder Splitting - Organize code by tags or custom logic with aggregator files for easy imports
π Rich Documentation - JSDoc comments with cURL examples and inline usage guides
π€ Agent-Ready Endpoints - Browse endpoints with pagination and path filtering, inspect deep endpoint details, and read generated types without reloading the spec
π©Ί Diagnostic Doctor - Diagnostic health checks for config validity, spec accessibility, peer dependencies, cache, and folder write permissions
π§Ή Stale File Purge - Manifest-based stale code detection and cleanup with dry-run support to prevent orphaned code
π Custom Code Injection - Preserve your custom code between regenerations with protected sections
Related MCP server: apifable
Installation
npm install openapi-sync
# or
npm install -g openapi-sync
# or use directly
npx openapi-syncβ οΈ macOS Big Sur Users: If you encounter an esbuild error (
Symbol not found: _SecTrustCopyCertificateChain), installesbuild@0.17.19first. See Troubleshooting for details.
π€ Using with AI Agents
All CLI commands and programmatic APIs are agent-safe β no interactive prompts, fully non-blocking. Use --json for machine-readable output and --silent to suppress logs.
Full agent reference:
llms.txtβ a structured discovery file for LLMs, Copilots, and MCP tools.
Agent Quick-Start (no prompts)
# 1. Create config (all settings as flags β no stdin required)
npx openapi-sync init --no-interactive \
--api-name petstore \
--api-url https://petstore3.swagger.io/api/v3/openapi.json \
--output-folder ./src/api \
--client-type react-query \
--validation-library zod \
--config-format typescript \
--json
# Or for protected specs, configure auth directly on init:
npx openapi-sync init --no-interactive \
--api-name backend \
--api-url https://api.example.com/openapi.json \
--auth-type bearer \
--auth-token '${env.SPEC_TOKEN}' \
--preset react-query-zod \
--json
# 2. Validate config + specs before writing any files
npx openapi-sync validate --json
# 3. Sync β generate types, endpoints, and schemas
npx openapi-sync --json
# 4. Generate a typed API client
npx openapi-sync generate-client --type react-query --jsonMachine-Readable Output (--json)
Every command emits a single, pure JSON object to stdout when --json is passed, making it safe to pipe directly into jq or consume from automated agents. All human-readable progress logs are suppressed or directed to stderr.
$ npx openapi-sync --json
{
"success": true,
"apis": ["petstore"],
"filesWritten": ["src/api/petstore/types.ts", "src/api/petstore/endpoints.ts"],
"endpointCount": 20,
"warnings": [],
"errors": [],
"phases": {
"sync": { "filesWritten": ["src/api/petstore/types.ts", "src/api/petstore/endpoints.ts"], "endpointCount": 20 },
"client": { "filesWritten": [], "endpointCount": 20 }
}
}$ npx openapi-sync validate --json
{
"valid": true,
"apis": { "petstore": { "valid": true, "endpointCount": 20 } },
"configErrors": []
}$ npx openapi-sync list-endpoints --json
{
"petstore": [
{ "name": "getPetById", "method": "GET", "path": "/pet/{petId}", "tags": ["pet"], "summary": "Find pet by ID" },
{ "name": "addPet", "method": "POST", "path": "/pet", "tags": ["pet"], "summary": "Add a new pet" }
]
}$ npx openapi-sync list-endpoints --api petstore --path-contains pet --limit 2 --offset 0 --json$ npx openapi-sync get-endpoint --api petstore --operation-id getPetById --json$ npx openapi-sync read-type --api petstore --type-name Pet --jsonDry Run (preview without writing files)
Compact, fast previews of planned files:
npx openapi-sync --dry-run --json
npx openapi-sync generate-client --type fetch --dry-run --jsonLayouts & Output Directories
Flat Mode (Default): When
folderSplitis omitted or empty ({}), files are placed directly in the API folder (endpoints.ts,types/index.ts,types/shared.ts).Tag-Split Mode: Setting
folderSplit: { byTags: true }organizes endpoints into tag subfolders (e.g.{tag}/endpoints.ts,{tag}/types.ts,shared.ts).Custom Client Directory:
clientGeneration.outputDir(or CLI--output) is fully supported in both flat and folder-split layouts. In flat mode, clients are placed directly in{outputDir}/clients.ts(orapi.ts), while in folder-split mode clients are placed in{outputDir}/{tag}/client.tsand aggregated at{outputDir}/clients.ts, with relative imports resolving back to your generated types and endpoints.
Programmatic API (TypeScript)
import {
ValidateConfig,
Init,
GenerateClient,
ListEndpoints,
GetEndpointDetails,
ReadGeneratedType,
Doctor,
Purge,
} from "openapi-sync";
// Pre-flight check β no files written
const validation = await ValidateConfig({ silent: true });
if (!validation.valid) throw new Error(JSON.stringify(validation));
// Diagnostic health check on config, specs, peer dependencies, and directories
const health = await Doctor({ silent: true });
console.log("Health check:", health.healthy ? "All checks passed" : "Issues detected");
// Inspect API surface with pagination and filtering
const endpoints = await ListEndpoints({
apiName: "petstore",
pathContains: "pet",
limit: 5,
offset: 0,
silent: true,
});
console.log(endpoints.petstore.length, "endpoints found");
// Inspect a single endpoint in full detail (4-tier fuzzy matching)
const detail = await GetEndpointDetails({ apiName: "petstore", operationId: "getPetById", silent: true });
console.log(detail.endpoint.path);
// Read an exact generated type declaration (with optional line pagination)
const typeDecl = await ReadGeneratedType({ apiName: "petstore", typeName: "Pet", silent: true });
console.log(typeDecl);
// Sync and get structured result
const syncResult = await Init({ silent: true });
if (!syncResult.success) throw new Error(JSON.stringify(syncResult));
console.log("Files written:", syncResult.filesWritten);
// Generate client
const clientResult = await GenerateClient({ type: "react-query", silent: true });
console.log(JSON.stringify(clientResult));
// Detect and purge stale files from disk
const purgeResult = await Purge({ yes: true, silent: true });
console.log("Purged files:", purgeResult.purged);Exit Codes
Code | Meaning |
| Success |
| Config error or validation failed |
| Network / spec fetch error |
| Generation / file write error |
Agent-safe vs Interactive Commands
Command | Agent-safe? | Description |
| β | Sync specs, generate types, endpoints, schemas |
| β | Validate config + specs; no files written |
| β | Diagnostic health check on config, network, peer deps, cache |
| β | List endpoints with filtering and pagination; no files written |
| β | Inspect detailed schema for one endpoint by operationId or name |
| β | Read generated TypeScript declaration block |
| β | Generate typed API client (fetch, next-fetch, axios, react-query, swr, rtk-query) |
| β | Remove stale generated files without prompting |
| β | Create config file without prompts |
| β | Interactive wizard (requires stdin) |
Quick Start
Option 1: Interactive Setup (Recommended) π―
The easiest way to get started is with the interactive setup wizard:
npx openapi-sync initThe wizard will guide you through:
π Configuration file format selection (TypeScript, JSON, or JavaScript)
π API specification source (URL or local file)
π Folder organization options (split by tags or custom logic)
π Client generation options (React Query, SWR, Fetch, Axios, RTK Query)
β Validation library setup (Zod, Yup, Joi)
π§ Custom code preservation settings
π·οΈ Type naming preferences (operationId usage, prefix)
π« Endpoint filtering (exclude by tags)
π Documentation options (cURL examples)
Option 2: Manual Setup
1. Create openapi.sync.json in your project root:
{
"refetchInterval": 5000,
"folder": "./src/api",
"api": {
"petstore": "https://petstore3.swagger.io/api/v3/openapi.json"
}
}2. Run the sync command:
npx openapi-sync3. Use generated types and endpoints:
import { getPetById } from "./src/api/petstore/endpoints";
import { IPet } from "./src/api/petstore/types";
const petUrl = getPetById("123"); // Returns: "/pet/123"View detailed quick start guide β
β‘ Presets (Zero-Config Framework Setup)
Presets bundle opinionated defaults for your framework, client library, and validation stack into a single name. Instead of configuring dozens of settings by hand, pick a preset during npx openapi-sync init or set "preset": "<name>" in your config file. Any explicit configuration values you define always override preset defaults.
Preset Name | Target Framework / HTTP Client | Validation Library | Features Configured | Recommended Dependencies |
| TanStack React Query v5 | Zod | Typed Query & Mutation hooks, Zod schemas, preserved custom code, operationId naming |
|
| TanStack React Query v5 | Yup | Typed Query & Mutation hooks, Yup validation schemas, preserved custom code |
|
| Vercel SWR | Zod | SWR hooks with mutation support ( |
|
| Vercel SWR | Yup | SWR hooks with mutation support, Yup schemas, preserved custom code |
|
| Axios Client | Zod | Standalone typed Axios client instance, Zod schemas, preserved custom code |
|
| Axios Client | Joi | Standalone typed Axios client, Joi validation schemas (great for Node.js backends) |
|
| Native Fetch API | Zod | Zero-dependency native fetch client, Zod runtime validation |
|
| Redux Toolkit Query | Zod | RTK Query API slice definitions with |
|
| Next.js (App/Pages router) | Disabled | Server Components-friendly fetch calls with caching headers, validation disabled for zero bundle bloat | (Built into Next.js) |
| Python | N/A | Generates Python dataclasses / |
|
Using a Preset
In the CLI Setup Wizard:
npx openapi-sync init
# Select your preset from the interactive menu with rich descriptionsNon-Interactive / CI:
npx openapi-sync init --preset react-query-zod --api-name petstore --api-url https://petstore3.swagger.io/api/v3/openapi.jsonIn JSON (openapi.sync.json):
{
"$schema": "./node_modules/openapi-sync/openapi.sync.schema.json",
"preset": "react-query-zod",
"api": {
"petstore": "https://petstore3.swagger.io/api/v3/openapi.json"
}
}In TypeScript (openapi.sync.ts):
import { defineConfig } from "openapi-sync";
export default defineConfig({
preset: "react-query-zod",
api: {
petstore: "https://petstore3.swagger.io/api/v3/openapi.json",
},
// User values cleanly override preset defaults:
folder: "./src/api",
});View presets guide on website β
API Client Generation
Generate fully-typed API clients with hooks for popular libraries:
Generate Fetch Client
npx openapi-sync generate-client --type fetchGenerate Axios Client
npx openapi-sync generate-client --type axiosGenerate React Query Hooks
npx openapi-sync generate-client --type react-query --api petstoreGenerate SWR Hooks
npx openapi-sync generate-client --type swrGenerate RTK Query API
npx openapi-sync generate-client --type rtk-queryGenerate Next.js Fetch Client (App Router & Server Components)
npx openapi-sync generate-client --type next-fetch
# Or use --preset next-fetch during init / syncUsage in Next.js App Router (Server Components):
// app/pets/[id]/page.tsx (Server Component β no React hooks needed)
import { getPetById, setApiConfig } from "@/api/petstore/clients";
// Set baseURL at runtime or via environment variables
setApiConfig({ baseURL: process.env.API_BASE_URL || "https://api.example.com" });
export default async function PetPage({ params }: { params: { id: string } }) {
// Built-in Next.js App Router cache and tag-based revalidation
const pet = await getPetById(
{ url: { petId: params.id } },
{
cache: "force-cache",
next: { revalidate: 3600, tags: ["pets"] },
}
);
return <div><h1>{pet.name}</h1></div>;
}Filter by Tags or Endpoints
# Filter by tags
npx openapi-sync generate-client --type fetch --tags pets,users
# Filter by specific endpoints
npx openapi-sync generate-client --type axios --endpoints getPetById,createPetUsage Example (React Query)
1. Generate the client:
npx openapi-sync generate-client --type react-query2. Use in your React components:
import { QueryClient, QueryClientProvider } from "@tanstack/react-query";
import { useGetPetById, useCreatePet } from "./api/petstore/client/hooks";
import apiClient from "./api/petstore/client/client";
// Configure API client
apiClient.updateConfig({
baseURL: "https://api.example.com",
headers: {
Authorization: "Bearer your-auth-token",
},
});
function PetDetails({ petId }: { petId: string }) {
// Query hook for GET requests with structured params
const { data, isLoading, error } = useGetPetById({
url: { petId }, // Path parameters
query: { includeOwner: true }, // Query parameters (if any)
});
// Mutation hook for POST/PUT/PATCH/DELETE requests
const createPet = useCreatePet({
onSuccess: () => {
console.log("Pet created!");
},
});
const handleCreate = () => {
createPet.mutate({
data: {
// Request body
name: "Fluffy",
species: "cat",
},
});
};
if (isLoading) return <div>Loading...</div>;
if (error) return <div>Error: {error.message}</div>;
return (
<div>
<h1>{data?.name}</h1>
<button onClick={handleCreate}>Create New Pet</button>
</div>
);
}Client Generation Options
Option | Description | Example |
| Client type to generate |
|
| Specific API from config |
|
| Filter by endpoint tags |
|
| Filter by endpoint names |
|
| Output directory |
|
| Base URL for requests |
|
Custom Code Preservation
Generated clients support custom code sections that are preserved during regeneration:
// client.ts (Generated)
// ============================================================
// π CUSTOM CODE START
// Add your custom code below this line
// This section will be preserved during regeneration
// ============================================================
// Your custom helper functions, middleware, etc.
// π CUSTOM CODE END
// ============================================================View complete client generation guide β
Configuration
Supports multiple configuration formats: openapi.sync.json, openapi.sync.ts, or openapi.sync.js
Basic Example:
{
"refetchInterval": 5000,
"folder": "./src/api",
"api": {
"petstore": "https://petstore3.swagger.io/api/v3/openapi.json"
}
}Advanced TypeScript Example:
import { IConfig } from "openapi-sync";
const config: IConfig = {
refetchInterval: 10000,
folder: "./src/api",
api: {
"main-api": "https://api.example.com/openapi.json",
},
folderSplit: { byTags: true },
types: { name: { prefix: "I", useOperationId: true } },
endpoints: {
exclude: { tags: ["deprecated"] },
doc: { showCurl: true },
},
validations: { library: "zod" },
};
export default config;π Protected Specs & Stored Authentication (auth)
Fetch OpenAPI specifications protected behind Bearer tokens, Basic auth, API keys, or custom headers.
β οΈ IMPORTANT FOR HUMANS & AI AGENTS: Referencing environment variables for credentials requires using a TypeScript (
openapi.sync.ts) or JavaScript (openapi.sync.js) configuration file. Static JSON (openapi.sync.json) does not support JavaScript runtime expressions likeprocess.env. Always useopenapi.sync.tsoropenapi.sync.jswhen dynamic environment variables are needed to keep secrets safe and prevent invalid JSON syntax errors.
TypeScript Example (openapi.sync.ts):
import { defineConfig } from "openapi-sync";
export default defineConfig({
folder: "./src/api",
api: {
// 1. Protected with Bearer token
billingApi: {
url: "https://api.example.com/billing/openapi.json",
auth: {
type: "bearer",
token: process.env.BILLING_API_TOKEN!,
},
},
// 2. Protected with Basic auth
internalApi: {
url: "https://internal.example.com/spec.json",
auth: {
type: "basic",
username: process.env.INTERNAL_USER!,
password: process.env.INTERNAL_PASSWORD!,
},
},
// 3. Protected with API Key (header or query)
analyticsApi: {
url: "https://analytics.example.com/openapi.json",
auth: {
type: "apiKey",
in: "header",
name: "X-API-Key",
value: process.env.ANALYTICS_KEY!,
},
},
},
});JavaScript Example (openapi.sync.js):
/** @type {import('openapi-sync').IConfig} */
module.exports = {
folder: "./src/api",
api: {
protectedApi: {
url: "https://api.example.com/openapi.json",
auth: {
type: "bearer",
token: process.env.MY_SPEC_TOKEN,
},
},
},
};View full configuration options β
CLI Commands
Interactive Setup
npx openapi-sync initLaunch an interactive wizard that guides you through creating your configuration file. Perfect for first-time setup or exploring available options.
Sync API Types
# Sync with default config
npx openapi-sync
# Sync with custom refetch interval
npx openapi-sync --refreshinterval 10000Synchronize your OpenAPI specifications and generate TypeScript types, endpoints, and validation schemas.
Zero-Config CLI Execution & Config Overrides
You can run openapi-sync directly from terminal scripts or CI/CD pipelines without creating a configuration file on disk. Pass any property supported by the configuration file via CLI flags:
# Zero-config sync with preset
npx openapi-sync --api-url https://petstore3.swagger.io/api/v3/openapi.json --preset react-query-zod --folder ./src/api
# Zero-config sync with protected spec
npx openapi-sync --api-url https://api.example.com/openapi.json --auth-type bearer --auth-token "$MY_TOKEN" --preset next-fetch
# Multiple APIs via CLI
npx openapi-sync --api users=https://api.example.com/users.json --api billing=https://api.example.com/billing.json --preset axios-zod
# Override existing disk config properties on-the-fly
npx openapi-sync --folder ./dist/api --validation-lib yup --no-docs
# Raw JSON configuration via CLI
npx openapi-sync --config-json '{"api":{"main":"https://api.example.com/spec.json"},"preset":"react-query-zod"}'If run without a configuration file on disk and without necessary CLI flags (e.g.--api-url, --api <name>=<url>, or --config-json), openapi-sync will display the standard ConfigNotFoundError, prompting you to run npx openapi-sync init.
Generate API Client
# Generate React Query hooks
npx openapi-sync generate-client --type react-query
# Generate for specific API
npx openapi-sync generate-client --type axios --api petstore
# Generate with filters
npx openapi-sync generate-client --type fetch --tags pets,users
# Generate for specific endpoints
npx openapi-sync generate-client --type swr --endpoints getPetById,createPetGenerate fully-typed API clients for various frameworks and libraries.
Available Commands & Options
Command | Description |
| Interactive setup wizard (or non-interactive with |
| Sync OpenAPI specs and generate types, endpoints, and validation schemas |
| Generate typed API client code ( |
| Validate configuration and remote/local specs without writing files |
| Run diagnostic health checks on config, specs, peer dependencies, and cache |
| Detect and remove stale generated files that no longer exist in specs |
| List all discovered endpoints with filtering, tags, and pagination |
| Inspect details, parameters, and generated code for a specific endpoint |
| Extract and display generated TypeScript type definitions for any schema |
| Show help information |
| Show version number |
CLI Flag Aliases
Flags are interchangeable across init, sync, validate, and generate-client:
Output folder:
--output-folderor--folder(-f) (defaults to project root"")Validation library:
--validation-libraryor--validation-lib(--validations-library)Tag folder split:
--folder-splitor--split-by-tagsType prefix:
--types-prefixor--type-prefix
Diagnostic Health Checks (doctor)
Run an automated environment audit to diagnose config syntax, specification accessibility, optional peer dependencies (zod, yup, joi), cache state, and directory write permissions:
# Run human-readable diagnostic report
npx openapi-sync doctor
# Run machine-readable health check for agents and CI
npx openapi-sync doctor --jsonOutput Example:
{
"healthy": true,
"checks": [
{ "name": "Configuration", "status": "ok", "message": "Valid openapi.sync.ts found" },
{ "name": "Spec Reachability: petstore", "status": "ok", "message": "HTTP 200 OK (20 endpoints)" },
{ "name": "Peer Dependency: zod", "status": "ok", "message": "zod v3.23.8 installed" },
{ "name": "Output Directory", "status": "ok", "message": "./src/api is writable" }
],
"recommendations": []
}Stale File Detection & Cleanup (purge)
Whenever endpoints or schemas are removed from your OpenAPI specification, previously generated files can become orphaned in your codebase. openapi-sync tracks generated artifacts via .openapi-sync/manifest.json and automatically detects stale files.
# Preview what stale files would be deleted without making changes
npx openapi-sync purge --dry-run
# Preview stale files as JSON (for CI / AI agents)
npx openapi-sync purge --dry-run --json
# Delete stale files without an interactive prompt
npx openapi-sync purge --yes
# Limit purge to a single configured API
npx openapi-sync purge --api petstore --yesInspecting Endpoints & Types (get-endpoint, read-type)
AI agents and developers can query specific endpoint metadata or read generated type declarations without loading huge files or blowing LLM context windows:
# Inspect full endpoint definition by operationId
npx openapi-sync get-endpoint --operation-id getPetById --json
# Inspect endpoint using 4-tier fuzzy matching by name or path
npx openapi-sync get-endpoint --name pet_update --json
# Read exact generated TypeScript type definition
npx openapi-sync read-type --api petstore --type-name Pet --jsonTyped Error Codes & Recovery
All CLI commands and programmatic methods throw structured error objects extending OpenApiSyncError. Each error exposes a stable code string:
Error Code | Error Class | Common Cause | Recommended Recovery Action |
|
| No | Run |
|
| Syntax or evaluation error in config file | Check config file syntax; check |
|
| Missing required fields (e.g. empty | Ensure |
|
| Network timeout, DNS failure, 401/403/404 | Verify URL; add |
|
| Local file does not exist or unreadable | Check relative file path in |
|
| Malformed OpenAPI JSON or YAML spec | Validate spec with Swagger Editor / |
|
| Filesystem write permission error | Ensure target directory has write permissions |
|
|
| Check configured API names using |
Documentation
For complete documentation including:
Configuration Options - All available settings and customization
Generated Output - Understanding generated files and structure
Custom Code Injection - Preserve your code between regenerations
Validation Schemas - Runtime validation with Zod, Yup, or Joi
Advanced Examples - Complex configurations and use cases
API Reference - Programmatic usage and type definitions
Troubleshooting - Common issues and solutions
Visit openapi-sync.com
π MCP Server (Model Context Protocol)
openapi-sync ships with a complete Model Context Protocol (MCP) server. AI agents (Claude Desktop, Cursor, Windsurf, Zed, and any MCP-compatible client) can query endpoints, inspect schemas, read generated types, and execute syncs directly via type-safe tool calls over stdio β without pasting entire 5MBβ15MB specs into prompt context.
The MCP server is published both as part of openapi-sync and as a dedicated zero-install companion package on npm: openapi-sync-mcp.
4 Ways Users & Agents Can Access OpenAPI Sync
Method | Command / Import | Best For |
1. Standalone MCP Package |
| Claude Desktop, Cursor, Windsurf, Zed configs (zero workspace install needed) |
2. Main CLI MCP Subcommand |
| When |
3. Agent-Safe CLI ( |
| Autonomous agents with bash/terminal access (Cursor Agent, Claude Code, Antigravity) |
4. Programmatic Node / ESM |
| Custom orchestration scripts, internal developer portals, and CI bots |
Starting the Server
# Option A: Via standalone companion package (recommended for agent configs)
npx openapi-sync-mcp
# Option B: Via main CLI (if openapi-sync is installed)
npx openapi-sync mcp
# Option C: If installed globally
openapi-sync-mcpTransport: The server uses stdio transport β it reads JSON-RPC from stdin and writes responses to stdout. The working directory (
cwd) of the process is used as the project root for reading and writing files.
Host Configuration Guides
1. Cursor Configuration
Create or update .cursor/mcp.json in your project root:
{
"mcpServers": {
"openapi-sync": {
"command": "npx",
"args": ["-y", "openapi-sync-mcp"],
"cwd": "${workspaceFolder}"
}
}
}Or add it globally via Cursor Settings β Features β MCP β + Add New MCP Server.
2. Claude Desktop Configuration
Edit your configuration file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"openapi-sync": {
"command": "npx",
"args": ["-y", "openapi-sync-mcp"],
"cwd": "/path/to/your/project"
}
}
}3. Windsurf (Codeium) Configuration
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"openapi-sync": {
"command": "npx",
"args": ["-y", "openapi-sync-mcp"]
}
}
}4. Zed Configuration
Add to your Zed settings.json under context_servers:
{
"context_servers": [
{
"name": "openapi-sync",
"command": {
"path": "npx",
"args": ["-y", "openapi-sync-mcp"]
}
}
]
}5. Google Antigravity Configuration
Add to your global configuration (~/.gemini/config/mcp_config.json) or project root (.agents/mcp_config.json):
{
"mcpServers": {
"openapi-sync": {
"command": "npx",
"args": ["-y", "openapi-sync-mcp"]
}
}
}Available MCP tools
Tool | Description |
| Read the current config file β start here to understand what's configured |
| Validate config + specs without writing any files (supports auth and config overrides) |
| Run full diagnostic health check on config, specs, peer dependencies, and cache |
| List endpoints with tag filtering, pagination, path matching, and optional cache reuse |
| Return the full stored endpoint definition for one endpoint by operationId or name |
| Read the exact generated TypeScript interface/type declaration from the generated types file |
| Generate types, endpoints, and validation schemas |
| Generate a typed API client (fetch, next-fetch, axios, react-query, swr, rtk-query) |
| Detect and remove stale generated files (supports dryRun and yes) |
| Create an openapi.sync config file (non-interactive, with first-class auth & runSync) |
Typical agent workflow via MCP
1. openapi_sync_read_config β check if config exists
2. openapi_sync_init β create config if needed (non-interactive, default folder "")
3. openapi_sync_doctor β verify environment, spec reachability, and peer dependencies
4. openapi_sync_validate β confirm specs are reachable and valid
5. openapi_sync_list_endpoints β inspect a paged subset of endpoints or search by path
6. openapi_sync_get_endpoint_details β inspect the full schema for one endpoint
7. openapi_sync_read_generated_type β read a specific generated TypeScript declaration
8. openapi_sync_sync β generate types + schemas
9. openapi_sync_generate_client β generate a typed client with optional cache reuse
10. openapi_sync_purge β clean up stale files when specs evolveTool input/output types
All tools return JSON-serialized versions of the same structured types used by the programmatic API:
openapi_sync_syncβSyncResultopenapi_sync_generate_clientβSyncResultopenapi_sync_validateβValidationResultopenapi_sync_doctorβDoctorResult({ healthy, checks, recommendations })openapi_sync_list_endpointsβRecord<string, EndpointSummary[]>openapi_sync_get_endpoint_detailsβ{ apiName, endpoint }openapi_sync_read_generated_typeβstringopenapi_sync_initβ{ success, configFile, message, errors }openapi_sync_read_configβ{ found, file, path, content }
Troubleshooting
macOS Big Sur (11.x) - esbuild Installation Error
Error: dyld: Symbol not found: _SecTrustCopyCertificateChain when installing openapi-sync
Cause: The default esbuild version requires macOS 12.0+ APIs that aren't available in Big Sur.
Solution: Install a compatible esbuild version before installing openapi-sync:
# Install compatible esbuild first
npm install esbuild@0.17.19
# Then install openapi-sync
npm install openapi-syncAlternatively, add an override to your package.json:
{
"overrides": {
"esbuild": "0.17.19"
}
}Note: This issue only affects macOS Big Sur (darwin 20.x). Users on macOS 12+ are not affected.
License
ISC License - see LICENSE file for details.
Contributing
Contributions welcome! Submit pull requests to our GitHub repository.
Contributors
A special thanks to the following contributors for their valuable work on this project:
Support / Donate
If you find OpenAPI Sync useful and would like to support its development, thank you β your support helps pay for hosting, CI, and ongoing maintenance.
You can support the project in any of the following ways:
Sponsor the maintainer on GitHub: https://github.com/sponsors/akintomiwa-fisayo
Back the project on Open Collective (placeholder): https://opencollective.com/fisayo-akintomiwa
Thank you for considering supporting the project β every bit helps.
This server cannot be deployed
Maintenance
Related MCP Connectors
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
MCP Spec Compliance MCP β audits any MCP server.json against the official Model Context Protocol
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yoβ¦
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
Related MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that loads multiple OpenAPI specifications and exposes them to LLM-powered IDE integrations, enabling AI to understand and work with your APIs directly in development tools like Cursor.749 npm90MIT
- AlicenseAqualityAmaintenanceMCP server that helps AI agents explore OpenAPI specs, search endpoints, and generate TypeScript types.715 npm10MIT
- FlicenseAqualityDmaintenanceA clone-and-own MCP server that exposes OpenAPI/Huma contract intelligence to AI agents by turning API specifications into deterministic endpoint metadata, schemas, validation facts, and TypeScript declarations.6-
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that standardizes tool discovery, execution, and context management for AI applications.MIT