MCP tools reference

An assistant sees only the tools its token’s scopes allow.

In the course

• SRThe exact tools Claude calls to build Arjun's workflow. Lesson 5: Build by talking to Claude →

Read

Tool	Scope	What it does
autoappy_list_workflows	read	Lists the workflows you can access.
autoappy_get_workflow	read	One workflow: summary, notes, revision, steps (app, action, status, account name), inputs with secrets hidden, missing required fields, last test.
autoappy_run_history	read	Recent runs, or one run with each step’s result and error.
autoappy_app_catalog	read or write	Searches published apps, or lists one app’s actions and their exact input fields.
autoappy_list_accounts	read or write	Names of your saved accounts that a step or action can use (never credentials).
autoappy_get_trigger_setup	read or write	A workflow’s trigger, webhook URL, capture status, sample fields and any extra triggers.
autoappy_list_mapping_fields	read or write	Ready-to-use placeholders (such as {{workflow.phone}}) with sample values.
autoappy_get_dynamic_fields	read or write	Child fields of a field that depends on another choice, such as a sheet’s columns.
autoappy_get_field_options	read or write	Dropdown choices loaded from the chosen account.

Build and edit

Tool	Scope	What it does
autoappy_create_workflow	write	Creates a Draft workflow with any catalog trigger (default: the MCP trigger) and a one-line summary.
autoappy_add_node	write	Adds a step after a parent step.
autoappy_configure_node	write	Sets a step’s inputs (merge with existing values, dynamic fields).
autoappy_set_account	write	Chooses which saved account a step uses.
autoappy_update_graph	write	Changes connections, conditions and positions.
autoappy_delete_nodes	write	Deletes steps.
autoappy_send_test_data	write	Saves one sample submission to a webhook trigger (nothing runs), so later steps can map its fields.
autoappy_update_workflow	write	Renames, edits the summary and display name, and writes sticky notes.
autoappy_set_status	write	Sets a workflow or step to Live, Pause or Draft.

Run

Tool	Scope	What it does
autoappy_test_step	execute	Runs one step for real with sample data.
autoappy_run_workflow	execute	Runs a workflow now (like Run once).
autoappy_run_action	execute	Runs a single app action with a saved account, without building a workflow (for example, send one WhatsApp message).
run_<workflow>	execute	One tool per workflow you’ve exposed in Settings → MCP connections → Workflows.
autoappy_get_request	any	Checks whether a request waiting for approval was approved, and its result.

How an assistant builds a workflow

This is the order Auto Appy recommends to assistants (it’s in the server’s instructions):

1. Ask only what can’t be inferred: the channel and wording, which saved account if there are several, and the field names the form sends.
2. Pick the trigger. Website forms and anything that can call a URL use the Webhook trigger; app events use that app’s trigger from the catalog.
3. Create the workflow with autoappy_create_workflow.
4. For a webhook, call autoappy_get_trigger_setup, give the person the URL, then autoappy_send_test_data with one realistic submission.
5. Add steps with autoappy_add_node (the trigger’s ID equals the workflow ID).
6. Map with autoappy_list_mapping_fields, then autoappy_configure_node.
7. Attach accounts with autoappy_list_accounts and autoappy_set_account.
8. Test each step with autoappy_test_step, then set it Live with autoappy_set_status.

Note

Tools that change things are marked as such, so assistants like Claude ask before calling them. Runs of exposed workflows also respect your Approval required setting in Auto Appy.