Plate Recognizer MCP server
4 operations0 webhooks
Read license plates (with optional make, model and color) and text identifiers such as VINs, trailer ids and odometers from images, and check usage. Requests send Authorization Token.
Try Plate Recognizer with your agent
Connect Plate Recognizer, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in Plate Recognizer on my account, then run one read-only example and show me the result.
Plate Recognizer tools and triggers
Tools are what your agent can do in Plate Recognizer through Corsair's MCP server. Triggers are the Plate Recognizer events a routine can start from.
Ocr
- Get UsageRead-only
Read the OCR calls used this period and the plan limit.
ocr.getUsage
- ReadRead-only
Read a VIN, trailer id, odometer, shipping container, boat registration or C-TPAT seal from an image. Uses one OCR call; takes 20 to 30 s.
ocr.read
Plates
- ReadRead-only
Read license plates (and optionally make, model and color) from an image. Uses one Snapshot lookup. Plate text is not stored.
plates.read
Usage
- GetRead-only
Read the current Snapshot usage period.
usage.get
Connect Plate Recognizer to Claude, ChatGPT or Cursor
- 1
Connect Plate Recognizer in Corsair
Add your Plate Recognizer API key once in Corsair. Corsair stores the credential encrypted and makes the Plate Recognizer API calls for your agent, so it never goes into a prompt or a config file. Connect Plate Recognizer
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Plate Recognizer. On a ChatGPT personal plan, connect Plate Recognizer here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. Every Plate Recognizer operation only reads data, so it runs right away in every mode.
FAQ
Install corsair and @corsair-dev/platerecognizer, add the Plate Recognizer plugin, and connect with an API key. Then call methods like corsair.platerecognizer.api.ocr.getUsage() from your app. Corsair syncs data per tenant.
Yes. Plate Recognizer requires an API key from your Plate Recognizer account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit Plate Recognizer, GitHub, Notion, Stripe, and the rest. Trigger Plate Recognizer from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for read license plates (with optional make, model and color) and text identifiers such as VINs, trailer ids and odometers from images, and check usage. Requests send Authorization Token. Common builds include sync jobs, admin tooling, and agents that call Plate Recognizer APIs from your backend. Local DB entities let you query synced Plate Recognizer records without hitting the API on every read.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Plate Recognizer API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/platerecognizer in the open repo. When Plate Recognizer ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your Plate Recognizer data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Plate Recognizer data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put Plate Recognizer on a link in Strict mode and every write waits for your approval, while destructive actions are refused. Every Plate Recognizer operation only reads data, so there are no changes to approve today. You can change a link's mode at hub.corsair.dev/me.