Latchshot MCP integration for AI agents.
Connect AI agents to Latchshot through 2 structured actions, including get usage and capture page. Review authentication, inputs, workflows, and safety guida…
- ACTION CONTRACTS
- 2
- 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 Latchshot integration exposes
The Latchshot Agent App exposes 2 provider-backed actions for developer tools and design & media work. Its current contract lets an authorized agent read the current latchshot plan, successful-render quota, reset time, upgrade-request status, and owner-managed paid-plan links. this action never initiates payment or an upgrade and render a public web page as a png, jpeg, or pdf and store the bounded artifact in local transit storage. 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 Latchshot account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Latchshot capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_usageREADRead the current Latchshot plan, successful-render quota, reset time, upgrade-request status, and owner-managed paid-plan links. This action never initiates payment or an upgrade.
capture_pageREVIEWRender a public web page as a PNG, JPEG, or PDF and store the bounded artifact in local transit storage.
INPUTS: url / kind / format / width / height
INPUT CONTRACTS
Know what the action needs before it runs.
capture_page
urlREQUIRED- The public HTTP or HTTPS page URL. Private, loopback, link-local, credential-bearing, and non-web-port targets are rejected.
kindOPTIONAL- The artifact family to render.
formatOPTIONAL- The image format for screenshots. PDF renders always return PDF.
widthOPTIONAL- The browser viewport width in CSS pixels.
heightOPTIONAL- The browser viewport height in CSS pixels.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Usage
Read the current Latchshot plan, successful-render quota, reset time, upgrade-request status, and owner-managed paid-plan links. This action never initiates payment or an upgrade. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_usageVerify with Capture Page
Render a public web page as a PNG, JPEG, or PDF and store the bounded artifact in local transit storage. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
capture_pageSAFETY BOUNDARY
Operate Latchshot with explicit limits
- Authorize Latchshot with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Latchshot 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 Latchshot rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Latchshot task completed successfully.
CONNECTION MODEL
API key
Latchshot API key sent as a Bearer token. Get a recurring Free-plan key from https://latchshot.fly.dev/?intent=openconnector#trial.
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
- 1
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
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 Latchshot.