loaditout.ai
SkillsPacksTrendingLeaderboardAPI DocsBlogSubmitRequestsCompareAgentsXPrivacyDisclaimer
{}loaditout.ai
Skills & MCPPacksBlog

apifable

MCP Tool

ycs77/apifable

MCP server that helps AI agents explore OpenAPI specs, search endpoints, and generate TypeScript types.

Install

$ npx loaditout add ycs77/apifable

Platform-specific configuration:

.claude/settings.json
{
  "mcpServers": {
    "apifable": {
      "command": "npx",
      "args": [
        "-y",
        "apifable"
      ]
    }
  }
}

Add the config above to .claude/settings.json under the mcpServers key.

About

<div align="center">

apifable

Read the spec. Understand the API. Integrate with confidence.

[![NPM version][ico-version]][link-npm] [![Software License][ico-license]](LICENSE) [![Total Downloads][ico-downloads]][link-downloads]

English | 繁體中文

</div>

---

Overview

apifable is an MCP server that helps AI integrate APIs more smoothly into TypeScript frontend projects. It makes it easy to explore API structure, search endpoints, and generate TypeScript types, giving your AI agent the context it needs to write accurate integration code.

✨ Features
  • 📦 AI-ready API context — give AI the structure it needs to understand and work with your API
  • 📘 OpenAPI 3.0 / 3.1 support — works with standard specs as a reliable source of truth
  • 🤖 MCP server for AI agents — plug into Claude, Cursor, and Windsurf
  • 🔍 API exploration tools — browse endpoints, search by keyword, and inspect full request/response details
  • 🏷️ TypeScript type generation — generate TypeScript type definitions ready to use in frontend code
Getting Started
Installation

Run apifable init to set up your project configuration:

npx apifable@latest init

This creates apifable.config.json in your project root. The config file should be committed to version control so the spec path is shared with your team.

After the command starts, you can choose between Manual file and Remote URL.

1. Manual file

Use this mode if your OpenAPI spec already lives in the project, or if you want to manage spec updates yourself.

init will ask for the local file path, such as openapi.yaml.

You then need to place your OpenAPI spec at that path manually. When the backend API changes, you also need to update that file manually.

2. Remote URL

Use this mode if your OpenAPI spec is available from a stable remote URL, such as the OpenAPI spec end

Tags

apiclaude-codemcpmcp-serveropenapiswaggertypescript

Reviews

Loading reviews...

Quality Signals

Quality Score5000
9
Stars
0
Installs
Last updated27 days ago
Security: AREADME

Safety

Risk Levelmedium
Data Access
read
Network Accessnone

Details

Sourcegithub-crawl
Last commit3/18/2026
View on GitHub→

Embed Badge

[![Loaditout](https://loaditout.ai/api/badge/ycs77/apifable)](https://loaditout.ai/skills/ycs77/apifable)