One MCP connection to your apps.

Set it up

1. Copy the address

   Open Connect your AI client from the account menu in APIANT.ai. The address and a ready-made Claude Code terminal command are there.

2. Add it to your AI client

   Paste the address as a remote MCP server, or run the Claude Code command. Step by step for Claude Code.

3. Sign in once

   Your browser opens APIANT's sign-in, including multi-factor authentication if you use it. The client gets its own OAuth token; your password never reaches it. Authentication and permissions.

What your agent can do over MCP

• Find and connect apps

  Search the catalog, see each app's triggers and actions, and connect your accounts.

• Build a missing connector

  Given an app's name, the agent reads the vendor's API documentation, builds the connector and its authentication, and tests each operation against the live API. How connector building works.

• Build and test automations

  Describe an automation; the agent builds it, tests every scenario, fixes failures and turns it on.

• Run and diagnose

  Read execution history, find what failed today, retry runs and restart them from a step.

• Publish and deploy

  Publish from a dev environment to production, or deploy an automation into other accounts.

• Expose automations as tools

  Turn an automation into a tool your AI client can call, so a workflow becomes one step in a larger agent task.

Any API, not a fixed list

The catalog is where your agent starts, not where it stops. It can extend the catalog for your account: point it at the API documentation and it builds the operations it needs, at whatever depth the API allows. If the documentation cannot be read, it stops and says so rather than guessing endpoints.

Or add the Claude plugin

In Claude Code, the APIANT plugin sets up the same connection: add the marketplace with /plugin marketplace add APIANT/apiant-plugins, then /plugin install apiant@apiant, and sign in with your APIANT account. The plugin and its manifest are public on GitHub.

Listed in the MCP Registry

The server is published in the official MCP Registry as ai.apiant/apiant, verified against the apiant.ai domain: see the registry entry. It is also listed on Glama. Its server card is at /.well-known/mcp/server-card.json.

Skills travel with the connection

The procedures your agent follows, for building connectors, testing automations or diagnosing a failed run, are delivered over the MCP connection itself, so every client that connects gets the current version. See the skills and the MCP tools. The server's OAuth scopes and the public app catalog feed are also described in an OpenAPI spec.