MCP-APIKit: Automates API Extraction, Real-Time Precision

MCP-APIKit automates seamless API doc extraction from MCP servers, boosting developer efficiency with precise, real-time data—no guesswork, just clarity.

Visit Repository

✨ Developer Tools

4.1(166 reviews)

249 saves

116 comments

Ranked in the top 1% of all AI tools in its category

About MCP-APIKit

What is MCP-APIKit: Automates API Extraction, Real-Time Precision?

MCP-APIKit is a specialized microservice designed to streamline API integration within development workflows. At its core, it acts as a bridge between Eolink OpenAPI and the Windsurf IDE, automating the extraction of API specs and exposing them as MCP resources. Think of it as a "live API hub" that keeps your IDE in sync with real-time updates from Eolink. The kicker? It does this while maintaining precision through the Model Context Protocol (MCP), ensuring seamless communication with any compliant tooling.

How to Use MCP-APIKit: Automates API Extraction, Real-Time Precision?

Getting started is straightforward:

Setup: Clone the repo, install dependencies with pnpm, and build the project (see code snippets below for exact commands).
Configure: Drop your Eolink API key and project IDs into a .env file. No rocket science here—just basic credential setup.
Run: Spin up the server and connect to Windsurf IDE using the provided mcpServers configuration. Within minutes, you'll see APIs auto-populate in your workspace.
Debug: Use the built-in inspector tool to trace API calls and troubleshoot issues on the fly. Ideal for when things "just don't work" and you need to see what's breaking.

Pro tip: Always run pnpm build before testing to ensure the latest changes are reflected.

MCP-APIKit Features

Key Features of MCP-APIKit: Automates API Extraction, Real-Time Precision?

Eolink Integration: Automatically pulls API specs from Eolink, eliminating manual entry. This is a game-changer for teams managing dozens of APIs.
MCP Standardization: Uses the Model Context Protocol to ensure compatibility with any MCP-compliant tool, not just Windsurf. Future-proofing done right.
Real-Time Exploration: The search-apis

 tool lets you filter APIs by project, method, or endpoint—no more digging through docs.
    Test-Driven Development: The test-api utility allows parameter tweaking directly in the IDE, making iterative testing a breeze.
    Self-Hosting Flexibility: Runs as a standalone server, so you're not locked into a SaaS model. Perfect for on-prem or private cloud setups.



  Use Cases of MCP-APIKit: Automates API Extraction, Real-Time Precision?
  Here's where this tool shines:
  1. Team Collaboration: Sync all API definitions across a development team's IDEs. No more "it works on my machine" arguments when API specs are centrally managed.
  2. Rapid Prototyping: Import third-party APIs via import-api and start building integrations immediately. Ideal for hackathons or MVP development.
  3. CI/CD Pipelines: Use as a source of truth for API validation during deployments. Ensure staging/production environments match documented specs.
  4. Legacy System Modernization:

`MCP-APIKit FAQ`

`FAQ from MCP-APIKit: Automates API Extraction, Real-Time Precision?`


  Q: Does this work with other IDEs besides Windsurf?

  A: While Windsurf is the primary target, the MCP protocol means any tool supporting it can connect. We're actively working on integrations with VS Code extensions.
  
  Q: How does it handle API versioning?

  A: Eolink's version control is passed through directly. You can specify versions in API resource URIs like api://projects/123/apis/v2.
  
  Q: What happens if Eolink's API goes down?

  A: MCP-APIKit caches the last successful sync. Your IDE will show cached data with a "stale" indicator until connectivity is restored.
  
  Q: Is there a GUI for configuration?

  A: Not yet, but we're prioritizing a web-based admin panel in the next release. For now, it's CLI/config file only.
  
  Q: Is this free to use?

  A: Absolutely! The MIT license lets you use, modify, and distribute MCP-APIKit however you like. Contributions are welcome via GitHub.

`Content`

`MCP-APIKit`


MCP-APIKit is a microservice control plane (MCP) server designed specifically for Windsurf IDE integration. It fetches API information from Eolink OpenAPI and provides it to the IDE's MCP client, enabling seamless API integration and management within your development environment.
Features

Connects to Eolink OpenAPI to retrieve API specifications
Exposes API information as MCP resources
Provides tools for API discovery and exploration
Supports API testing and integration within Windsurf IDE
Implements the Model Context Protocol (MCP) for standardized communication

Installation
# Clone the repository
git clone https://github.com/yourusername/mcp-apikit.git
cd mcp-apikit

# Install dependencies
pnpm install

# Build the project
pnpm run build

Configuration
Create a .env file in the root directory with the following variables:
EOLINK_API_KEY=your_eolink_api_key
EOLINK_BASE_URL=https://api.eolink.com
SPACE_ID=your_space_id
PROJECT_ID=your_project_id

Usage
Starting the Server
pnpm start

The server will start on the port specified in your .env file (default: 3000).
Debug
npx @modelcontextprotocol/inspector node dist/index.js

Connecting from Windsurf IDE
pnpm build

In your Windsurf IDE settings, add a new MCP server with the following configuration:
    "mcpServers": {
      "apikit": {
        "command": "node",
        "args": [
          "/Users/{userName}/Documents/mcp-apikit/dist/index.js"
        ],
        "env": {}
      }
    }

API Resources
The MCP-APIKit server exposes the following resources:

api://projects - List all API projects
api://projects/{projectId} - Get details for a specific project
api://projects/{projectId}/apis - List all APIs in a project
api://projects/{projectId}/apis/{apiId} - Get details for a specific API

Tools
The server provides the following tools:

search-apis - Search for APIs across all projects
test-api - Test an API endpoint with custom parameters
import-api - Import an API specification from Eolink to your project

Development
# Run in development mode with hot reloading
npm run dev

License
MIT

`Related MCP Servers & Clients`

`MCP Categories`

Developer Tools