.AIAPIANT over MCP
The APIANT MCP server at https://mcp.apiant.ai/mcp exposes your APIANT.ai account as tools for Claude Code, over Streamable HTTP with OAuth sign-in and no credits.
The APIANT MCP server at https://mcp.apiant.ai/mcp exposes your APIANT.ai account as tools Claude Code can call. You direct Claude in plain English, Claude calls the tools, and the tools build, test and inspect automations on your account. Using the server costs no assistant credits, on every plan including Free.
Connection details
| Property | Value |
|---|---|
| Server URL | https://mcp.apiant.ai/mcp |
| Transport | Streamable HTTP |
| Authentication | OAuth 2.1 authorization code with PKCE (S256) |
| Client registration | Dynamic client registration |
| Authorization server | https://app.apiant.ai |
| Scopes | mcp:tools, mcp:automation_builder |
| Server name used by the Claude Code install | apiant-ai |
You do not paste an API key. Claude Code signs in with OAuth as one APIANT user, and every tool call acts on that user's account. Details are in Authentication and permissions.
Clients
- Claude Code is the supported client. The Connect to Claude Code item in your account menu installs the APIANT skills and registers the server in one command. See Connect Claude Code.
The skills are what teach Claude APIANT's procedures: how to build, test, edit and diagnose an automation, step by step. The Claude Code install includes them.
What Claude can do through the server
| Area | Examples of what to ask |
|---|---|
| Find apps and operations | "Which Shopify triggers fire on a new order?" |
| Connect apps | "Connect my account on this app with this API key." |
| Build and edit automations | "Build an automation that posts new Stripe payments to Slack." "Change the channel to #payments." |
| Organize | "Move these three automations to a folder called Billing." |
| Test | "Test it with a sample payment of $20." "Replay yesterday's webhook." |
| Diagnose and recover runs | "Why did the last run fail?" "Retry the failed runs from this morning." |
| Versions | "What changed between the last two versions?" |
| Diagram comments | "Apply my comments." |
| Error alerts and retries | "Stop emailing me about this timeout error." |
| Connectors, triggers and actions | "Add a List invoices action to the Acme connector." Requires a plan that allows app authoring. |
| Publish and deploy | "Deploy this automation to all linked accounts." Enterprise, with the matching permissions. |
| Report a problem | "Report to APIANT that this screen is confusing." |
Working with Claude describes each of these. The full tool list is in MCP tools.
What decides which tools work for you
Tools respect the same permissions and plan as the app:
- Signing in requires the MCP Tools permission on your account's role. The default role has it.
- Building or changing connectors requires a plan that allows app authoring.
- Publishing and deploying to other accounts are Enterprise features and need the matching permissions on your role.
A tool you are not permitted to use returns a permission error instead of acting.
Cost
Calls to the MCP server use no assistant credits. Automations still use the tasks on your plan when they run, however you built them. See Plans, usage and billing.
The assistant uses the same server
The in-app assistant calls this same server with a smaller set of tools chosen for building, testing and diagnosing automations. It cannot use the connector, publishing, deploy or alert-policy tools. See The APIANT assistant.
Next steps
In this section
Connect Claude Code
Install the APIANT skills and register the APIANT MCP server in a Claude Code project with the command from Connect to Claude Code, sign in, update and uninstall.
Authentication and permissions
How Claude Code signs in to APIANT with OAuth and PKCE, which account Claude acts as, the scopes and MCP Tools permission, token lifetimes, and how to reconnect or switch accounts.
Working with Claude
What to ask Claude in Claude Code to build, edit, test, diagnose, connect, extend and deploy APIANT automations, and how Claude behaves while it does.
Review a diagram and send comments to Claude
Leave comments on individual steps of an automation's diagram in APIANT.ai, then have Claude or the assistant apply every pending comment across your automations in one pass.
Troubleshooting MCP
Fixes for common problems connecting Claude Code to APIANT, including missing tools, 401 errors, the MCP Tools permission, outdated skills and locked drafts.