Agenty MCP integration for AI agents.
Connect AI agents to Agenty through 31 structured actions, including add list rows, create agent, delete agent, and capture screenshot. Review authentication…
- ACTION CONTRACTS
- 31
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Agenty integration exposes
The Agenty Agent App exposes 31 provider-backed actions for developer tools and data work. Its current contract lets an authorized agent insert one or more rows into one agenty list, create one agenty agent with the provided configuration, and delete one agenty agent by agent identifier. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Agenty account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Agenty capabilities.
Showing 12 of 31 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
add_list_rowsREADInsert one or more rows into one Agenty list.
INPUTS: list_id / rows
create_agentWRITECreate one Agenty agent with the provided configuration.
INPUTS: name / type / config / description / icon
delete_agentHIGH IMPACTDelete one Agenty agent by agent identifier.
INPUTS: agent_id
capture_screenshotREVIEWCapture a screenshot for one web page and return a downloadable file.
INPUTS: url
clear_list_rowsREADDelete all rows from one Agenty list.
INPUTS: list_id
convert_url_to_pdfREVIEWConvert one web page into a PDF document and return a downloadable file.
INPUTS: url
copy_agentREVIEWClone one Agenty agent by agent identifier.
INPUTS: agent_id
create_listREADCreate one Agenty list.
INPUTS: name / description
delete_list_rowHIGH IMPACTDelete one Agenty list row by list and row identifiers.
INPUTS: list_id / row_id
delete_list_rowsHIGH IMPACTDelete multiple Agenty list rows by list identifier and row identifiers.
INPUTS: list_id / row_id
download_job_fileREADDownload one named Agenty job file and return a downloadable file.
INPUTS: job_id / name
download_job_resultREADDownload one Agenty job export as raw text content.
INPUTS: job_id / format / collection / modified / filename
INPUT CONTRACTS
Know what the action needs before it runs.
add_list_rows
list_idREQUIRED- The Agenty list identifier.
rowsREQUIRED- The Agenty list rows to insert.
create_agent
nameREQUIRED- The Agenty agent name.
typeREQUIRED- The Agenty agent type.
configREQUIRED- The Agenty agent configuration object.
descriptionOPTIONAL- The Agenty agent description.
iconOPTIONAL- The Agenty agent icon URL.
delete_agent
agent_idREQUIRED- The Agenty agent identifier.
capture_screenshot
urlREQUIRED- The public HTTP or HTTPS URL to process.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Add List Rows
Insert one or more rows into one Agenty list. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
add_list_rowsControl Create Agent
Create one Agenty agent with the provided configuration. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_agentVerify with Clear List Rows
Delete all rows from one Agenty list. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
clear_list_rowsSAFETY BOUNDARY
Operate Agenty with explicit limits
- Authorize Agenty with API key and grant only the provider access required by the selected actions.
- 7 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_agent`, `delete_list_row`, and `delete_list_rows` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Agenty rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Agenty task completed successfully.
CONNECTION MODEL
API key
Agenty API key used with the X-Agenty-ApiKey header. Manage it from Agenty API Keys docs: https://agenty.com/docs/api-keys/88.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 19
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 3
- REVIEW SIGNALS
- 5
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Agenty.