모델 Context Protocol (MCP) 서버는 LLM-powered IDE 통합을 활성화하기 위해 여러 OpenAPI 사양을로드하고 제공합니다. 이 서버는 Cursor 및 기타 코드 편집기와 같은 OpenAPI 사양 및 LLM 전원 개발 도구 사이의 교량 역할을합니다.

특징

• 디렉토리에서 여러 OpenAPI 사양을로드
• MCP 프로토콜을 통한 API 운영 및 스키마 노출
• LLMs를 사용하여 API를 직접 이해하고 작업할 수 있습니다.
• 완전한 API 컨텍스트를 위한 dereferenced schemas 지원
• 모든 사용 가능한 API 카탈로그 유지

ReAPI에 의해 구동

이 오픈 소스 MCP 서버는 API 설계와 테스트를 단순화하는 차세대 API 플랫폼인 ReAPI에 의해 후원됩니다. 이 서버는 개발을위한 로컬 OpenAPI 통합을 제공하지만, ReAPI는 두 강력한 모듈을 제공합니다.

## ## 뚱 베어

• 직관적인 no-code 편집기를 사용하여 API 설계
• OpenAPI 사양을 자동으로 생성 및 게시
• 실시간 팀원과 협업
• 버전 제어 및 변경 관리

API 테스트

• 대부분의 개발자 친화적 인 no-code API 테스트 솔루션
• 직관적인 인터페이스로 테스트 케이스 생성 및 관리

@reapi/mcp-openapi

A Model Context Protocol (MCP) server that loads and serves multiple OpenAPI specifications to enable LLM-powered IDE integrations. This server acts as a bridge between your OpenAPI specifications and LLM-powered development tools like Cursor and other code editors.

Features

• Loads multiple OpenAPI specifications from a directory
• Exposes API operations and schemas through MCP protocol
• Enables LLMs to understand and work with your APIs directly in your IDE
• Supports dereferenced schemas for complete API context
• Maintains a catalog of all available APIs

Powered by ReAPI

This open-source MCP server is sponsored by ReAPI, a next-generation API platform that simplifies API design and testing. While this server provides local OpenAPI integration for development, ReAPI offers two powerful modules:

🎨 API CMS

• Design APIs using an intuitive no-code editor
• Generate and publish OpenAPI specifications automatically
• Collaborate with team members in real-time
• Version control and change management

🧪 API Testing

• The most developer-friendly no-code API testing solution
• Create and manage test cases with an intuitive interface
• Powerful assertion and validation capabilities
• Serverless cloud test executor
• Perfect for both QA teams and developers
• CI/CD integration ready

Try ReAPI for free at reapi.com and experience the future of API development.

Cursor Configuration

To integrate the MCP OpenAPI server with Cursor IDE, you have two options for configuration locations:

Option 1: Project-specific Configuration (Recommended)

Create a .cursor/mcp.json file in your project directory. This option is recommended as it allows you to maintain different sets of specs for different projects

{
  "mcpServers": {
    "@reapi/mcp-openapi": {
      "command": "npx",
      "args": ["-y", "@reapi/mcp-openapi@latest", "--dir", "./specs"],
      "env": {}
    }
  }
}

Tip: Using a relative path like ./specs makes the configuration portable and easier to share across team members.

Note: We recommend using @latest tag as we frequently update the server with new features and improvements.

Important: Project-specific configuration helps manage LLM context limits. When all specifications are placed in a single folder, the combined metadata could exceed the LLM’s context window, leading to errors. Organizing specs by project keeps the context size manageable.

Option 2: Global Configuration

Create or edit ~/.cursor/mcp.json in your home directory to make the server available across all projects:

{
  "mcpServers": {
    "@reapi/mcp-openapi": {
      "command": "npx",
      "args": ["-y", "@reapi/mcp-openapi@latest", "--dir", "/path/to/your/specs"],
      "env": {}
    }
  }
}

Enable in Cursor Settings

After adding the configuration:

1. Open Cursor IDE