Plate Recognizer MCP integration for AI agents.
Connect AI agents to Plate Recognizer through 2 structured actions, including get statistics and read number plates. Review authentication, inputs, workflows…
- 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 Plate Recognizer integration exposes
The Plate Recognizer Agent App exposes 2 provider-backed actions for ai and security work. Its current contract lets an authorized agent retrieve current-month plate recognizer snapshot cloud usage and reset information and read number plates from one image by calling plate recognizer snapshot cloud and returning normalized detections. 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 Plate Recognizer account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Plate Recognizer capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_statisticsREADRetrieve current-month Plate Recognizer Snapshot Cloud usage and reset information.
read_number_platesREADRead number plates from one image by calling Plate Recognizer Snapshot Cloud and returning normalized detections.
INPUTS: uploadUrl / uploadBase64 / file / regions / cameraId
INPUT CONTRACTS
Know what the action needs before it runs.
read_number_plates
uploadUrlOPTIONAL- The public image URL to process instead of uploading raw bytes.
uploadBase64OPTIONAL- The Base64-encoded image content to send as the upload field.
fileOPTIONAL- Image file uploaded through POST /api/files.
regionsOPTIONAL- Optional list of country or state codes used to bias recognition.
cameraIdOPTIONAL- Optional camera identifier sent to Plate Recognizer.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Statistics
Retrieve current-month Plate Recognizer Snapshot Cloud usage and reset information. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_statisticsVerify with Read Number Plates
Read number plates from one image by calling Plate Recognizer Snapshot Cloud and returning normalized detections. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
read_number_platesSAFETY BOUNDARY
Operate Plate Recognizer with explicit limits
- Authorize Plate Recognizer with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Plate Recognizer 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 Plate Recognizer rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Plate Recognizer task completed successfully.
CONNECTION MODEL
API key
Plate Recognizer Snapshot Cloud API token used with the Authorization: Token header. Get it from the Snapshot Cloud dashboard: https://app.platerecognizer.com/service/snapshot-cloud/
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
- 2
- 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 Plate Recognizer.