Add any API from its spec

Paste a spec URL or upload the file. MCPAPI reads the name, the address and how it signs in, then indexes every operation so your agents can find it.

Start for free
MCPAPI’s Add an API page, with example data.
Add an APIpaid|4,812 credits

Add an API

A REST API described by an OpenAPI spec. MCPAPI calls it over HTTP with your credential; each operation becomes a tool named slug.operationId.

Connected APIs

The OpenAPI 3 or Swagger 2.0 document listing its operations. Each operation becomes one tool. Its name, address and sign-in fill the fields below.

What you and your team see in the dashboard and in logs.

What your agents see: its tools are named billing.operationId. Filled in from the name; lowercase letters, digits, - or _. Can't be a name from the public catalog.

Where requests go. Each operation's path is added to it.

Sent as Authorization: Bearer <key>. You paste the key on its page after the import.

What happens next
Import

MCPAPI reads the spec and makes each operation a tool your agents can search. Costs 1 credit per 10 new or changed operations.

Credential

Add your key for the API on its page. Until then, calls to it fail.

Agents

Connected agents find its tools with search_tools at once. Nothing to reinstall.

Any spec
OpenAPI 3.x and Swagger 2.0, one file or many, and Postman collections.
Sign-in read for you
API keys, bearer tokens, HTTP Basic and OAuth 2.0, from the spec’s own security section.
Re-import any time
Only new or changed operations cost credits; the rest are kept as they were.

Try it on your own APIs

Free with 100 credits a month. No card needed.