MCP tools

The APIANT MCP server at https://mcp.apiant.ai gives Claude the tools below. You do not call these tools yourself: you tell Claude what you want in plain English, and Claude picks and calls the tools.

Claude sees three tools when it connects (see How Claude reaches these tools). Through them it can find and run every tool listed on this page, and it loads APIANT's skills the same way, so there is no plugin to install.

This list is generated from the APIANT.ai source code on 2026-09-24. It leaves out tools reserved for APIANT staff, such as installation-wide settings. Tools marked Admin need an administrator account (the Switch Account permission). A listed tool can still refuse a call when your plan or permissions do not allow it; the notes under each family say which checks apply. The In the assistant column marks the tools the in-app assistant also uses.

Family	What it covers
Automations (auto_)	Build, edit, commit, turn on and off, organize and version automations.
Runs and execution history (exec_)	Test automations, read run history and per-step data, and retry, replay, restart, halt or cancel runs.
Connections (connection_)	Connect and disconnect app accounts, with an API key or through an OAuth sign-in.
App catalog (catalog_)	Search apps, triggers, actions and fields, and read dropdown choices and dynamic fields while an automation is being built.
Assemblies: connectors, actions and triggers (asm_)	Create and edit the connectors, actions, triggers, dropdowns and field lookups that automations use, and test them against a live connection.
Certifying what you build (ops_)	Record how a connector's actions and triggers should be tested, test one with inputs you supply, and record how far a connector has been built out.
Error alerts (alert_)	Read and change the rules that rewrite error-alert messages for a step or an automation, read the system-wide rules, and manage dismissed alerts.
Deploy to linked accounts (deploy_)	Copy an automation or a folder of automations into your linked child accounts, and see which version each one runs.
Publish (publish_)	Copy an automation, a folder of automations, or a connector, action or trigger from your dev environment to its prod environment.
Credentials for your own app registration (credential_)	Report how Claude can obtain credentials for an app, and return the callback URL and scopes to register on the vendor's developer portal.
Account administration (admin_)	Create and list accounts, act as another account, read usage, health, change logs and audit trails, search logs and run history across accounts, stop and restore automations in an incident, and manage stored secrets and lookup values.
Other tools	Check the connection to the MCP server, and file a bug report or feedback with APIANT.

How Claude reaches these tools

A standard connection to https://mcp.apiant.ai shows Claude these three tools. Every other tool on this page is reached through apiant_call, with the same permission checks as calling it directly.

Tool	What it does	In the assistant
`apiant_call`	Run any APIANT tool on this page by name, with its inputs.	No
`apiant_search_tools`	Find the APIANT tool that fits a task, by keyword or by family.	No
`apiant_skill_load`	Load an APIANT skill, the step-by-step procedure Claude follows for a task such as building an automation or a connector.	No

The in-app assistant calls the tools marked Yes directly, not through apiant_call.

Automations (auto_)

Build, edit, commit, turn on and off, organize and version automations. Edits happen on a draft that is committed when it is ready.

Tool	What it does	In the assistant
`auto_apply_edits`	Apply several edits to an automation draft in order, stopping at the first one that fails.	Yes
`auto_build`	Create a complete automation in one call from a name, its trigger and an ordered list of steps.	Yes
`auto_commit`	Save the draft to the automation so it becomes the version that runs, optionally with a new name, folder, description or polling schedule.	Yes
`auto_compare_versions`	Show what changed between two saved versions of an automation, step by step.	No
`auto_discard_draft`	Throw away the current draft and leave the saved automation unchanged.	Yes
`auto_edit_mapping`	Change how data is mapped into a step's fields in the draft.	Yes
`auto_edit_metadata`	Rename a step or change its display name and other descriptive details in the draft.	Yes
`auto_edit_structure`	Add, remove, move or replace a step in the draft, including conditions, loops and subroutine calls.	Yes
`auto_edit_trigger`	Add, remove or replace a trigger in the draft, or change its filter.	Yes
`auto_find_by_assembly`	Find your automations that use a given action or trigger.	No
`auto_folder`	List, create, rename and delete automation folders, and move automations between them.	Yes
`auto_get_connection_throttle`	Read the rate limit set on one of your app connections.	No
`auto_get_draft_state`	Return the current draft of the automation being edited.	Yes
`auto_get_step_details`	Return one step of the draft by its position.	Yes
`auto_get_subroutine_io`	Return the inputs a subroutine expects and the outputs it returns.	No
`auto_get_subroutine_references`	Find the automations in your account, and in its linked child accounts, that call a subroutine or use it as an error handler.	No
`auto_get_summary`	Summarize an automation: its name, whether it is on, how it is triggered, its schedule and its step types.	Yes
`auto_get_version`	Read one saved version of an automation.	No
`auto_list`	List your automations, most recently edited first, filtered by name, folder, or on and off.	Yes
`auto_list_versions`	List the saved versions of an automation, newest first.	No
`auto_load`	Open a saved automation as a draft for editing.	Yes
`auto_manage`	Finish an automation: rename it, turn it on or off, set how many of its runs may overlap, detach a deployed copy from its template, or delete it.	Yes
`auto_pending_change_requests`	Collect the step comments you left on automation diagrams in the web app, so Claude can apply them.	Yes
`auto_set_active`	Turn an automation on or off. Turning it on is refused while a required setting is empty or an app it uses is not connected.	Yes
`auto_set_connection_throttle`	Set or clear a rate limit on one of your app connections, shared by every action that uses it.	No

Runs and execution history (exec_)

Test automations, read run history and per-step data, and retry, replay, restart, halt or cancel runs.

Lists that span automations (failed runs, waiting runs, pending retries, unprocessed webhooks, history search) cover your own automations.

Tool	What it does	In the assistant
`exec_cancel_snoozed`	Cancel an automation's snoozed or waiting runs so they never resume.	No
`exec_get_branch_test_points`	List an automation's condition branches and which of them a test run covered.	Yes
`exec_get_data`	Show the input, output and error of each step for one record processed in a run, including how each field value was mapped.	Yes
`exec_get_form_link`	Return the form link for a run that is waiting for someone to submit a hosted form.	Yes
`exec_get_history`	List an automation's runs, newest first, filtered by outcome, recent days or error text.	Yes
`exec_get_retry_detail`	Show one pending retry: its attempt number, its schedule and the failed step's error.	Yes
`exec_get_step_data`	Show each step of a run with its status, output, error and duration.	Yes
`exec_halt`	Stop one run of an automation, or every run of it that is in progress.	No
`exec_list_failed_runs`	List failed runs across your automations for a date range, newest first.	Yes
`exec_list_parked`	List runs that are waiting (snoozed, awaiting a form or an approval, or waiting on other runs) and what will resume each one.	No
`exec_list_retries`	List failed steps that are waiting for an automatic retry, soonest first.	No
`exec_list_unprocessed_webhooks`	List automations that received webhooks that were never processed, for example because the automation was off or a monthly limit was reached.	No
`exec_mutate_data`	Change the recorded output of a step in a run, so the run can be restarted with corrected data.	No
`exec_replay_webhook`	Run an automation again as a new run, with a JSON payload you supply or with an earlier run's trigger data.	No
`exec_restart_from_step`	Run a run again from a chosen step, reusing the recorded output of the steps before it.	No
`exec_retry_failed`	Run failed runs again as new runs, using each one's original trigger data.	Yes
`exec_search_history`	Search the run history of your automations for text in automation names, errors, step data or outgoing requests.	No
`exec_test_automation`	Run an automation as a test and return the result when it finishes.	Yes
`exec_test_subroutine`	Run a subroutine as a test with inputs you supply and return its outputs.	No

Connections (connection_)

Connect and disconnect app accounts, with an API key or through an OAuth sign-in.

The assistant does not use the two OAuth tools. It connects OAuth apps through a full-page redirect in the browser instead.

Tool	What it does	In the assistant
`connection_connect_api_key`	Connect an app with an API key or the other credentials the app asks for.	Yes
`connection_disconnect`	Disconnect a connected app account, removing webhooks it registered with the app for your automations.	Yes
`connection_finalize_oauth`	Finish connecting an app through its OAuth sign-in and save the connection.	No
`connection_start_oauth`	Start connecting an app through its OAuth sign-in and return the app's authorization link.	No

App catalog (catalog_)

Search apps, triggers, actions and fields, and read dropdown choices and dynamic fields while an automation is being built.

Downloading an app logo needs the Assembly Developer permission.
Repairing a shared action or trigger needs a plan that allows app authoring.
The three proof tools work only with a real connection of yours, not a test connection, and record the proof for your account.

Tool	What it does	In the assistant
`catalog_arm_write_lane`	Arrange for the next run of your automation to prove a write action works on your own connected account, without making an extra call to your account.	No
`catalog_classify_operation`	Check whether an app and operation you asked for are ready to use or need to be built or tried first, so Claude knows how to proceed.	No
`catalog_download_app_logo`	Fetch an app's logo by its web domain and set it as the connector's icon.	No
`catalog_field_prove_operation`	Run a read action once on your own connected account and, if it succeeds, record that it works.	No
`catalog_get_app_operations`	List the actions or triggers of one app.	Yes
`catalog_get_dropdown_options`	Return the choices for a dropdown field, read from the app with your connection.	Yes
`catalog_get_dynamic_fields`	Return the fields an action or trigger offers for your connected account, such as custom fields.	Yes
`catalog_get_operation_fields`	Return the input and output fields of an action or trigger.	Yes
`catalog_list_apps`	List the apps in the catalog, including connectors your account built, and whether you have connected each one.	Yes
`catalog_record_field_proof`	Record that an action worked on your own connected account, from a run that shows it succeeding.	No
`catalog_repair_operation`	Give your account a private copy of a shared action or trigger that is broken, move your automation onto the copy so it can be fixed, and send the diagnosis to APIANT.	No
`catalog_reveal_operation`	Return the details of a newer action or trigger that the app picker does not show yet, so an automation can use it with your connection.	No
`catalog_search_apps`	Search the app catalog.	Yes
`catalog_search_fields`	Search the input and output fields of actions and triggers by name, label or help text.	Yes
`catalog_search_operations`	Search actions and triggers across the catalog.	Yes

Assemblies: connectors, actions and triggers (asm_)

Create and edit the connectors, actions, triggers, dropdowns and field lookups that automations use, and test them against a live connection.

Creating an action, trigger or connector, planning or building one out, and finishing or repairing one, need a plan that allows app authoring.
Creating an API-key or no-auth connector, and setting an app icon, also need the Assembly Developer permission.
Creating an OAuth connector needs the OAuth App Registration permission or a plan that allows app registration.
You can change only the actions, triggers and connectors you built.

Tool	What it does	In the assistant
`asm_amend_connector_scopes`	Add OAuth 2.0 scopes to a connector that is already set up, when an action needs a scope it does not ask for yet.	No
`asm_compare_versions`	Show which parts of an action, trigger or connector changed between two saved versions.	No
`asm_convert_connector_api_key_to_no_auth`	Change a connector that asks for an API key into one that needs no credentials, when the app turns out not to need one.	No
`asm_convert_connector_no_auth_to_api_key`	Change a connector that needs no credentials into one that asks for an API key, with evidence that the app requires one.	No
`asm_create_action_input_fields`	Set the input fields of an action: names, data types, required flags and help text.	No
`asm_create_action_or_trigger`	Create an action or trigger on a connector from an HTTP request and a mapping of the response.	No
`asm_create_connector`	Create a connector for an app that uses an API key or no credentials.	No
`asm_create_field_discovery`	Create a lookup that reads an app's field list from its API, and attach it to an action or trigger.	No
`asm_create_oauth1a_connector`	Create a connector for an app that signs in with OAuth 1.0a.	No
`asm_create_oauth_connector`	Create a connector for an app that signs in with OAuth 2.0.	No
`asm_create_populated_dropdown`	Create a dropdown whose choices come from the app's API, and attach it to an action or trigger.	No
`asm_delete_connector`	Delete a connector you built, once nothing else uses it.	No
`asm_delete_operation`	Delete an action or trigger you built.	No
`asm_document_fields`	Edit the label, help text and required flag of existing fields on an action or trigger, one field at a time.	No
`asm_edit_connector_params`	Admin. Change the credential fields a connector asks for when someone connects an account.	No
`asm_execute`	Run an action or trigger you are building against a connection and return its output.	No
`asm_find_referencers`	Find the automations that use a given action, trigger or connection.	No
`asm_get_action_throttle`	Read the rate limit set on an action.	No
`asm_get_app_icon`	Check whether a connector, action or trigger has an icon, and return it.	No
`asm_get_connection_credentials`	Check whether a connection has stored credentials and list the credential names an action can use. Values are never returned.	No
`asm_get_connector_throttle`	Read the default rate limit set on a connector.	No
`asm_get_version`	Read one saved version of an action, trigger or connector.	No
`asm_get_webhook_handler`	Read the script a connector uses to route incoming webhooks to the right connected account.	No
`asm_implement_stub`	Build out a planned action or trigger that has a name and description but no request yet.	No
`asm_inject_dynamic_fields`	Attach an existing field lookup to an action or trigger, so its fields come from the app's API.	No
`asm_inject_settings`	Set the configurable settings of an action or trigger, such as text boxes and dropdowns.	No
`asm_list_existing_operations`	List the actions and triggers already built on a connector.	No
`asm_list_unimplemented_ops`	List the planned actions and triggers on a connector that are not built yet.	No
`asm_list_versions`	List the saved versions of an action, trigger or connector, newest first.	No
`asm_load`	Load the full definition of an action, trigger or connector.	No
`asm_manage`	Finish an action, trigger or connector you built: check that it loads, and rename it or change its description.	No
`asm_read_assembly_logic`	Read the full logic of an action or trigger: its request, response mapping, fields, settings and pagination.	No
`asm_read_oauth_scopes`	Read the OAuth scopes declared on one of your connections.	No
`asm_replace_connector`	Move an action or trigger you built onto a different connector.	No
`asm_reset_settings`	Remove every setting from an action or trigger.	No
`asm_set_action_throttle`	Set or clear the rate limit on an action.	No
`asm_set_app_icon`	Set the icon of a connector, action or trigger from an image.	No
`asm_set_app_meta`	Admin. Record a connector's reference links and access notes, such as its API docs, pricing and support pages.	No
`asm_set_body`	Turn an action or trigger into a sequence of steps (requests, scripts, conditions, loops and calls to other actions) instead of a single request.	No
`asm_set_clear_encoding`	Declare how an app empties a field, so an automation can clear that field on purpose.	No
`asm_set_connector_auth`	Set or change how a connector sends an API key or other credential with each request.	No
`asm_set_connector_hmac_auth`	Set a connector to sign each request with an HMAC signature.	No
`asm_set_connector_modes`	Give a connector more than one way to sign in, such as OAuth or an API key, for the user to choose from when connecting.	No
`asm_set_connector_no_auth`	Declare that a connector's app needs no credentials at all.	No
`asm_set_connector_sigv4_auth`	Set a connector to sign each request with AWS Signature Version 4.	No
`asm_set_connector_throttle`	Set or clear the default rate limit on a connector.	No
`asm_set_connector_token_mint_auth`	Set a connector to exchange the account's credentials for a short-lived token, and get a new one when it expires.	No
`asm_set_connector_validation`	Set the check a connector runs when someone connects an account, so wrong or expired credentials are refused instead of saved.	No
`asm_set_connector_wsse_auth`	Set a connector to sign each request with a WSSE username token.	No
`asm_set_field_catalog`	Let an action look up custom field IDs by name for each connected account when it runs.	No
`asm_set_induction`	Set how a webhook trigger is tested: the setup steps and the action that makes the app send the event.	No
`asm_set_oauth1a_connector_auth`	Fill in the OAuth 1.0a sign-in of an existing connector.	No
`asm_set_oauth_connect_enrichment`	Set a call a connector makes right after an OAuth sign-in, to fetch account details it needs later.	No
`asm_set_oauth_connector_auth`	Fill in the OAuth 2.0 sign-in of an existing connector that has none yet.	No
`asm_set_oauth_context_exchange`	Set a call a connector makes before each request to swap its OAuth token for one scoped to that request.	No
`asm_set_oauth_persist_extras`	Choose which extra values from an OAuth sign-in a connector keeps for each account, such as an instance URL or company ID.	No
`asm_set_oauth_revocation`	Set where a connector revokes its OAuth token when an account is disconnected.	No
`asm_set_output_fields`	Set the output fields an action or trigger returns.	No
`asm_set_pagination`	Set how an action or trigger pages through results, so one call collects every page.	No
`asm_set_polling_identity`	Set how a polling trigger recognizes records it has already seen.	No
`asm_set_request`	Admin. Set or replace the single HTTP request an action or trigger makes, and how its response is read.	No
`asm_set_require_one_of`	Declare a group of inputs of which at least one must be filled in.	No
`asm_set_required_scopes`	Declare the OAuth scopes an action or trigger needs.	No
`asm_set_response_errors`	Set how an action or trigger handles each kind of error response, such as retrying or failing.	No
`asm_set_webhook_handler`	Set or clear the script a connector uses to route incoming webhooks to the right connected account.	No
`asm_set_webhook_registration`	Make a trigger register its webhook with the app when an automation turns on, and remove it when the automation turns off.	No
`asm_set_writable_fields`	Record which fields from a field lookup the app accepts when writing.	No
`asm_stub_operation`	Plan one new action or trigger on a connector by name and description, to be built later.	No
`asm_stub_operations`	Plan several new actions or triggers on a connector in one call, to be built later.	No
`asm_test_api_connection`	Send a test request with a connection's credentials and report whether it succeeded.	No
`asm_test_api_endpoint`	Send an HTTP request, written as a curl command, with a connection's credentials and return the response.	No
`asm_test_webhook_handler`	Try a connector's webhook routing script on a sample payload without running any automation.	No

Certifying what you build (ops_)

Record how a connector's actions and triggers should be tested, test one with inputs you supply, and record how far a connector has been built out.

These work on the connectors, actions and triggers you built, and recording build-out progress needs a plan that allows app authoring.

Tool	What it does	In the assistant
`ops_certify_with_subject`	Test an action or trigger you built by running it once with inputs you supply, and record the result.	No
`ops_set_cert_subject`	Record the inputs, and any setup steps, that testing an action must use.	No
`ops_set_ops_discovery`	Record how far a connector has been built out against the app's API documentation.	No

Error alerts (alert_)

Read and change the rules that rewrite error-alert messages for a step or an automation, read the system-wide rules, and manage dismissed alerts.

Rules for an automation or its steps can be changed by the automation's owner.
The retry and 401 lists apply to the whole installation and are read-only here.

Tool	What it does	In the assistant
`alert_get_automation_mappings`	Read the rules that rewrite error-alert messages for one automation.	No
`alert_get_error_policy`	Read which errors are retried and which app domains are exempt from turning an automation off after a 401 error.	No
`alert_get_mapping_trace`	Show, rule by rule, how an automation's alert rules rewrote the error from a given run.	No
`alert_get_step_mappings`	Read the alert-message rules on one step of an automation.	No
`alert_get_system_mappings`	Read the system-wide alert-message rules that apply to every automation.	No
`alert_list_suppressed`	List the alert messages that are dismissed for an automation.	No
`alert_set_automation_mappings`	Replace the alert-message rules for one automation, after showing a preview.	No
`alert_set_step_mappings`	Replace the alert-message rules on one step, after showing a preview.	No
`alert_set_system_mappings`	Admin. Replace the system-wide alert-message rules that apply to every automation, after showing a preview.	No
`alert_suppress`	Dismiss an alert for an automation, so alerts with exactly that first line are no longer sent.	No
`alert_unsuppress`	Remove a dismissed alert, so that alert is sent again.	No

Deploy to linked accounts (deploy_)

Copy an automation or a folder of automations into your linked child accounts, and see which version each one runs.

All three need an administrator account (the Switch Account permission). See Publish and deploy.

Tool	What it does	In the assistant
`deploy_automation_to_accounts`	Admin. Copy one automation into your linked child accounts, all of them or the ones you name.	No
`deploy_list_child_accounts`	Admin. List your active linked child accounts and the version each one is on, before you deploy.	No
`deploy_to_accounts`	Admin. Copy every automation in a folder into your linked child accounts.	No

Publish (publish_)

Copy an automation, a folder of automations, or a connector, action or trigger from your dev environment to its prod environment.

Plan: Enterprise

Publishing works only from a dev environment, for what you own. Published copies land inactive in the prod environment's Automation Templates account. See Publish and deploy.

Tool	What it does	In the assistant
`publish_assembly`	Publish a connector, action or trigger you built from your dev environment to prod.	No
`publish_automation`	Publish an automation, with the subroutines and private connectors it depends on, from your dev environment to prod.	No
`publish_folder`	Publish every automation in a folder from your dev environment to prod, stopping at the first one that is rejected or skipped.	No

Credentials for your own app registration (credential_)

Report how Claude can obtain credentials for an app, and return the callback URL and scopes to register on the vendor's developer portal.

Tool	What it does	In the assistant
`credential_capabilities`	Report what your session can do to obtain credentials for an app, which decides how Claude goes about it.	No
`credential_registration_kit`	Return what you need to register your own app on a vendor's developer portal, including the callback URL and the scopes.	No

Account administration (admin_)

Create and list accounts, act as another account, read usage, health, change logs and audit trails, search logs and run history across accounts, stop and restore automations in an incident, and manage stored secrets and lookup values.

Every tool here needs an administrator account (the Switch Account permission), except admin_revalidate_connections, which the owner of a connector can also run.
The tools that stop, restore, delete or dismiss show a preview first and change nothing until the call is confirmed.

Tool	What it does	In the assistant
`admin_account_changelog`	Admin. Read an account's change log, newest first.	No
`admin_account_task_totals`	Admin. Show one account's task totals by day or by month.	No
`admin_acct_group_disable`	Admin. In an incident, turn off every active automation in a parent account and its linked accounts, saving a snapshot so they can be turned back on. Shows a preview first.	No
`admin_acct_group_list_snapshots`	Admin. List the incident snapshots, with how many automations in each are still off and how many were restored.	No
`admin_acct_group_purge_tag`	Admin. Delete an incident snapshot's records after archiving what it covered. The automations themselves are not changed. Shows a preview first.	No
`admin_acct_group_restore`	Admin. Turn back on every automation in an incident snapshot. Shows a preview first.	No
`admin_action_audit`	Admin. Read the record of administrator actions taken against your installation: who did what, when, to which account, and the value before the change.	No
`admin_auto_search_by_app`	Admin. Find every automation, across all accounts, that uses a given app or action.	No
`admin_auto_search_exec_history`	Admin. Start a search of run history across accounts for text in trigger data, outputs or errors.	No
`admin_auto_search_exec_history_cancel`	Admin. Cancel a running run-history search.	No
`admin_auto_search_exec_history_status`	Admin. Check a run-history search's progress and get its results when it finishes.	No
`admin_create_account`	Admin. Create a new account with a name, email, starting password and optional plan.	No
`admin_delete_keyvault_entry`	Admin. Permanently delete a stored secret for an app, after showing what would be removed.	No
`admin_get_lookup_value`	Admin. Read a stored lookup value for an account.	No
`admin_list_accounts`	Admin. List the accounts in your installation, with their linked parent, plan and whether each is active.	No
`admin_list_keyvault_entries`	Admin. List the names of the secrets stored for an app. Values are never returned.	No
`admin_list_subscription_plans`	Admin. List the subscription plans set up for your installation.	No
`admin_list_suppressed_alerts`	Admin. List the alerts an administrator has dismissed for an automation, alongside the ones its owner dismissed.	No
`admin_revalidate_connections`	Re-check every active connection for a connector against the app, and report the ones whose credentials the app now rejects.	No
`admin_save_keyvault_entry`	Admin. Store a secret for an app, such as an API client secret, encrypted.	No
`admin_search_logs_cancel`	Admin. Cancel a running log search.	No
`admin_search_logs_start`	Admin. Start a search of the webhook, webhook-routing or sent-email logs.	No
`admin_search_logs_status`	Admin. Check a log search's progress and get its results when it finishes.	No
`admin_set_lookup_value`	Admin. Write a lookup value for an account, optionally encrypted and with an expiry.	No
`admin_suppress_alert`	Admin. Dismiss an alert for an automation on the administrator's list, which the account owner cannot see or undo. Shows a preview first.	No
`admin_switch_account`	Admin. Act as another account for the rest of the conversation, so later tools work on that account.	No
`admin_switch_back`	Admin. Stop acting as another account and return to your own.	No
`admin_tenant_health`	Admin. Show automation health across accounts: active and inactive counts, errors, successes, error rate and last run.	No
`admin_tenant_usage`	Admin. Show task use against plan limits across accounts, for the current billing period or a date range.	No
`admin_unsuppress_alert`	Admin. Remove an alert from the administrator's dismissed list, so it is sent again. Shows a preview first.	No

Other tools

Check the connection to the MCP server, and file a bug report or feedback with APIANT.

Claude files a feedback report only after you approve the draft. Reports about the MCP server itself are filed without asking.

Tool	What it does	In the assistant
`deploy_get_plugin_version`	Answer an older client that asks for a plugin version with the notice that the plugin is retired and there is nothing to install. It reports no version.	No
`ping`	Check that Claude is connected and signed in to APIANT, and report which account it is acting as.	Yes
`report_mcp_issue`	File a bug report or feedback with APIANT.	Yes

Next steps

Connect your AI client to use these tools from your terminal.
Authentication and permissions explains the sign-in and the permissions the tools check.
Skills lists what you can ask Claude to do with them.
The APIANT assistant uses the tools marked above.

Related docs