AppDrag MCP integration for AI agents.
Connect AI agents to AppDrag through 1 structured actions, including execute function. Review authentication, inputs, workflows, and safety guidance.
- ACTION CONTRACTS
- 1
- 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 AppDrag integration exposes
The AppDrag Agent App exposes 1 provider-backed actions for developer tools and data work. Its current contract lets an authorized agent execute one appdrag cloud backend api function by folder, function name, http method, and optional parameters. 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 AppDrag account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real AppDrag capabilities.
Showing 1 of 1 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
execute_functionWRITEExecute one AppDrag Cloud Backend API function by folder, function name, HTTP method, and optional parameters.
INPUTS: folder / functionName / method / environment / parameters
INPUT CONTRACTS
Know what the action needs before it runs.
execute_function
folderREQUIRED- The AppDrag function folder name used in the route.
functionNameREQUIRED- The AppDrag function name used in the route.
methodOPTIONAL- The HTTP method configured for the AppDrag API function.
environmentOPTIONAL- The AppDrag environment segment to call when using an environment-specific route.
parametersOPTIONAL- Key-value pairs forwarded to the AppDrag function as request parameters.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Execute Function
Execute one AppDrag Cloud Backend API function by folder, function name, HTTP method, and optional parameters. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
execute_functionControl Execute Function
Execute one AppDrag Cloud Backend API function by folder, function name, HTTP method, and optional parameters. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
execute_functionVerify with Execute Function
Execute one AppDrag Cloud Backend API function by folder, function name, HTTP method, and optional parameters. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
execute_functionSAFETY BOUNDARY
Operate AppDrag with explicit limits
- Authorize AppDrag with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in AppDrag rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the AppDrag task completed successfully.
CONNECTION MODEL
API key
AppDrag project API key forwarded as the APIKey request parameter. Open the official AppDrag dashboard, then use the "API" or "Databases" dashboard to copy or regenerate the shared project API key described here: https://support.appdrag.com/doc/Authentication-and-Access-Control.
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
- 0
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
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 AppDrag.