MCP for aviation customs preparation
Customs MCP Server for AI Agents
“Customs MCP server” names the workflow context, not a filer. The public interface is one extraction tool plus upload, result and usage helpers, not a duty engine.
Connect an MCP-compatible agent to that EASA Form 1 workflow. Require extract_easa_form1 by name after OAuth. tools/list is the acceptance test, not a URL that happens to contain the word server.
Public catalog as of 12 September 2026: extract_easa_form1 only.
One extraction tool, not a filer
The public surface is one document extraction operation plus the tools needed to upload, retrieve and monitor usage. “Customs” describes why aviation teams connect: they are preparing files. The public interface does not submit declarations, calculate binding duties or clear shipments for an operator.
If an RFP asks for a customs MCP that files, this product is the wrong line item. Point that RFP at your broker platform. Use Doana for Form 1 fields that a reviewer will accept or reject. Keep origin, valuation and procedure in the application that is actually allowed to transmit.
Listed MCP tools
After OAuth, list tools and require those names. Expect get_usage, create_mcp_upload, extract_easa_form1 and get_extraction_result. That set is the customs MCP surface today. There is no REST POST /extract sitting beside it. OpenAPI is discovery, not a second public mutation API.
Call get_usage before a document. For small non-ChatGPT files, content_base64 up to 64 KiB is enough. Otherwise fill an upload slot. Poll with job_id while status is dispatch_pending, queued, running or outcome_unknown. documentType unknown is usually a succeeded job with no Form 1 — stop reconstructing a Form 1 in prose.
Customs work it does not do
It does not classify goods, validate origin, compute duty, or transmit to a customs system of record. MCP’s Streamable HTTP specification describes transport only. It does not turn tool availability into filing authority. Keep those decisions in your application roles.
Do not send invoices, AWBs or FAA-only 8130-3 files to extract_easa_form1 and expect a customs-ready record. Classify the packet first. Dual-release cases need a human before choosing a tool. A succeeded MCP call is still not an accepted customs fact until uncertainFields are reviewed against the PDF.
Connect a compatible client
ChatGPT custom MCP apps, Claude remote connectors, Codex and Cursor document remote MCP support. Actual access depends on the client’s features, OAuth configuration and workspace policy. Protocol support is not proof that every configuration has been tested with Doana MCP.
Add https://doana.ca/api/mcp, complete Doana authorization, and verify extract_easa_form1 in the session. Then follow the client guide for attachments. Quota: five files per UTC week; confidence is an estimate; extraction is not compliance. Keep serial arrays intact when you paste fields into a review table.