A registry of 2,577 OpenAPI specifications for use with the mint CLI. Mint converts OpenAPI specs into MCP (Model Context Protocol) servers, and this registry provides a catalog of API specs ready for generation.
The registry is a single registry.json file sorted alphabetically by name. Each entry contains:
- name -- unique kebab-case identifier (e.g.,
stripe,google-gmail) - description -- brief summary of what the API does
- spec_url -- direct URL to the OpenAPI/Swagger spec (JSON or YAML)
- auth_type -- authentication method (
api_key,oauth2,bearer) - auth_env_var -- environment variable name for the API credential
- tags -- categorization labels for search and filtering
- min_mint_version -- minimum mint version required
# Search the registry
mint registry search gmail
# List APIs filtered by tag
mint registry list --tags payments
# Install a spec locally and generate an MCP server
mint registry install stripe
mint mcp generate openapi.yamlWhen you run mint registry install <name>, mint looks up the entry, downloads the OpenAPI spec from spec_url, and saves it locally. You then generate a fully functional MCP server with mint mcp generate.
The registry covers integrations from platforms like Make.com, n8n, and Zapier, sourced from the APIs.guru directory, official vendor OpenAPI repos, and community-maintained specs.
| Tag | APIs | Tag | APIs |
|---|---|---|---|
| data | 1,094 | communication | 309 |
| cloud | 993 | e-commerce | 301 |
| video | 484 | project-management | 193 |
| security | 458 | payments | 159 |
| analytics | 457 | storage | 158 |
| dev-tools | 364 | support | 142 |
| infrastructure | 358 | messaging | 139 |
| hr | 292 | monitoring | 115 |
| productivity | 223 | finance | 96 |
| Auth Type | APIs |
|---|---|
| api_key | 2,101 |
| oauth2 | 423 |
| bearer | 56 |
Google -- Gmail, Sheets, Drive, Calendar, Docs, BigQuery, GKE, Cloud Functions, Vision AI, and 300+ more googleapis entries.
Microsoft -- Graph API (Teams, OneDrive, Outlook), Azure (400+ services), Cognitive Services.
Twilio -- 25 individual APIs: Messaging, Voice, Video, Verify, Flex, Studio, TaskRouter, Serverless, and more.
Vonage/Nexmo -- SMS, Voice, Verify, Messages, Conversations, and 10+ more.
Payments -- Stripe, PayPal, Square, Adyen, Klarna, Brex, Checkout.com, Dwolla.
CRM/Marketing -- HubSpot (9 APIs), Salesforce, Pipedrive, Mailchimp, Brevo, ActiveCampaign.
Dev Tools -- GitHub, GitLab, Bitbucket, CircleCI, Sentry, Snyk, LaunchDarkly, Postman.
Infrastructure -- AWS, Azure, GCP, DigitalOcean, Cloudflare, Fastly, Hetzner, Linode, Netlify.
The registry is validated against schema.json (JSON Schema draft 2020-12). The top-level object has two required fields:
| Field | Type | Description |
|---|---|---|
schema_version |
integer | Must be 1 |
apis |
array | Array of API entry objects |
Each object in the apis array must include all of the following fields:
| Field | Type | Constraints | Description |
|---|---|---|---|
name |
string | Pattern: ^[a-z][a-z0-9-]*$ |
Unique kebab-case identifier |
description |
string | Min 10 characters | Human-readable summary of the API |
tags |
string[] | 1--5 items | Categorization labels |
spec_url |
string | Valid URI | Direct URL to the OpenAPI spec |
auth_type |
string | bearer, api_key, oauth2, or none |
Authentication mechanism |
auth_env_var |
string | Pattern: ^[A-Z][A-Z0-9_]*$ |
Environment variable for the credential |
min_mint_version |
string | Pattern: ^\d+\.\d+\.\d+$ |
Minimum mint CLI version required |
No additional properties are allowed on either the root object or individual entries.
New submissions are reviewed using a Sire workflow template that automates validation and requires human approval before merge. The workflow:
- Validates the new entry against
schema.json - Verifies the
spec_urlis reachable - Pauses at a human-in-the-loop approval gate
- Posts an approval comment on the PR
See CONTRIBUTING.md for how to add a new API entry.
Apache 2.0 -- see LICENSE.