Diffy MCP integration for AI agents.
Connect AI agents to Diffy through 6 structured actions, including get diff, get project, and get screenshot. Review authentication, inputs, workflows, and s…
- ACTION CONTRACTS
- 6
- 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 Diffy integration exposes
The Diffy Agent App exposes 6 provider-backed actions for developer tools and design & media work. Its current contract lets an authorized agent get the current status and visual change result for a diffy comparison, get the current settings and environments for a diffy project, and get the current status and result details for a diffy screenshot set. 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 Diffy account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Diffy capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_diffREADGet the current status and visual change result for a Diffy comparison.
INPUTS: diffId
get_projectREADGet the current settings and environments for a Diffy project.
INPUTS: projectId
get_screenshotREADGet the current status and result details for a Diffy screenshot set.
INPUTS: screenshotId
list_diffsREADList visual comparison results for a Diffy project.
INPUTS: projectId / page
list_projectsREADList the Diffy visual testing projects available to the connected account.
list_screenshotsREADList screenshot sets captured for a Diffy project.
INPUTS: projectId
INPUT CONTRACTS
Know what the action needs before it runs.
get_diff
diffIdOPTIONAL- The Diffy comparison identifier.
get_project
projectIdOPTIONAL- The Diffy project identifier.
get_screenshot
screenshotIdOPTIONAL- The Diffy screenshot set identifier.
list_diffs
projectIdREQUIRED- The Diffy project identifier.
pageOPTIONAL- The zero-based Diffy results page to return.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Diff
Get the current status and visual change result for a Diffy comparison. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_diffVerify with Get Project
Get the current settings and environments for a Diffy project. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_projectSAFETY BOUNDARY
Operate Diffy with explicit limits
- Authorize Diffy with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Diffy data may still be sensitive and should be minimized before it enters model context.
- 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 Diffy rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Diffy task completed successfully.
CONNECTION MODEL
API key
Diffy API key exchanged for an API bearer token. Generate a key from https://app.diffy.website/#/keys.
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
- 6
- WRITE SIGNALS
- 0
- 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 Diffy.