Correios API MCP for AI. Track Brazilian shipments & quote costs instantly.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Correios API provides direct access to Brazilian postal services data. You can track any object using its tracking code or calculate accurate shipping costs and estimated delivery deadlines for various services like SEDEX and PAC.
What your AI can do
Calculate price deadline
Estimates both the cost and delivery timeline for a package between two Brazilian zip codes, given weight and dimensions.
Track object
Fetches the complete status history and current location details for any specific postal tracking code.
Retrieves the full history of events and current location for any valid postal tracking code.
Calculates the precise monetary price for various services based on package dimensions, weight, and destination codes.
Provides an estimated number of business days until the package is expected to arrive at its destination.
Runs simulated shipping price and deadline calculations for e-commerce checkout processes or support chats.
Ask an AI about this
Waiting for input…
Correios API (REST) with 2 Tools
These tools allow you to get real-time logistics data for Brazil: run a package tracking query or calculate shipping price and deadlines.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Correios API (REST) on VinkiusCalculate Price Deadline
Estimates both the cost and delivery timeline for a package between two Brazilian zip codes, given weight and dimensions.
Track Object
Fetches the complete status history and current location details for any specific...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Correios API (REST), then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Correios. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 2 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Dealing with shipment data usually means copy/pasting between three or four tabs.
Today, when a customer asks about an order, you grab the tracking number and switch to the postal carrier's website. Next, if they ask how much another item will cost to ship, you open a separate calculator page, manually enter the dimensions, and wait for the quote. This process takes time and requires juggling multiple browser tabs just to answer one simple question.
With this MCP, your agent handles it all automatically. You tell the system what data point is needed—be it status or price—and it performs the lookup internally. The result appears in the conversation instantly, letting you keep the user engaged without the manual effort.
Getting accurate pricing and tracking using `calculate_price_deadline`
The system eliminates the need to manually check compatibility between services. Instead of looking up if a service like SEDEX requires specific dimensions, you pass all the parameters to the tool. It handles the complex logic behind the pricing structure.
Now, calculating accurate shipping rates is just a function call. You get the price and deadline back in one go. That's how much faster your support team can answer questions.
What your AI can actually do with this
Need to handle logistics queries in Brazil? This MCP connects your agent directly to the official Correios REST infrastructure, letting you automate tasks that used to require multiple website visits. Instead of switching between tabs to check status or calculate quotes, your AI client handles it all within the chat interface.
For instance, if a customer asks for a tracking update, your agent can fetch the history instantly. If they ask how much an item will cost to ship, the system simulates the price and deadline using weight and zip code details. This keeps conversations flowing and provides instant answers without manual lookups.
By connecting this service via Vinkius, you get reliable access to Brazilian logistics data right where your workflow is happening.
019e387d-ef8d-738f-b61a-a87e43dc5c24 Here's how it actually works
The bottom line is, you tell your agent what data you need, and it executes the logistics query using the live API credentials provided.
Subscribe to this MCP on Vinkius and enter your specific Correios API credentials (User and Password).
Your AI client uses those stored credentials to authenticate the connection with the official Correios system.
The agent then sends a structured request, either asking for an object's status or providing shipping parameters for calculation.
Who is this actually for?
Anyone who deals with shipping in Brazil needs this. If you're a support rep tired of copy-pasting tracking numbers into external websites, or an e-commerce owner needing instant cost estimates during checkout, this MCP is for you.
Checks delivery statuses on demand to provide proactive updates to customers without leaving the storefront chat.
Provides instant, accurate tracking details or calculates a quick shipping quote within an AI-powered support chat interface.
Automates the process of estimating complex regional shipping costs and deadlines directly from terminal applications or internal workflows.
What Changes When You Connect
Eliminate manual lookups. Instead of opening a browser and pasting tracking numbers, your agent runs the track_object tool to give you instant status updates right in the conversation.
Improve customer experience by providing real-time quotes. You can run calculate_price_deadline to estimate shipping costs and deadlines immediately when a customer asks about postage.
Streamline e-commerce operations. Support teams use this MCP to gather full shipment history, so they never have to promise a status update they can't verify instantly.
Gain efficiency with complex calculations. The calculate_price_deadline tool handles the geometry: weight, dimensions, and origin/destination zip codes—you just feed it the variables.
Reduce support time. By giving agents access to this data, you drastically cut down on the back-and-forth required when a customer simply needs to know where their package is.
See it in action
A client asks for tracking status.
The Support Agent uses track_object with the provided code. The agent instantly replies, stating the item's current location and its last recorded event (e.g., 'In Transit to São Paulo').
A customer needs a shipping quote.
The E-commerce system calls calculate_price_deadline, passing the product dimensions, weight, and zip codes. The response is structured data confirming the exact price and estimated delivery window.
Logistics team plans regional shipments.
A Logistics Manager uses the MCP to test multiple scenarios via calculate_price_deadline. This allows them to compare costs for SEDEX vs. PAC services across different regions before confirming a quote.
Batch update of delivery status.
The agent processes several codes using track_object in quick succession, compiling a summary report that lists the current state and last known location for all items.
The honest tradeoffs
Using general knowledge.
Telling your agent, 'What is the status of my package?' without providing a code. The agent doesn't know what to search for.
Always provide the tracking number and ask the tool to run track_object with that specific code. This gives the system everything it needs.
Forgetting dimensions.
Trying to calculate a price, but only providing weight and zip codes. The resulting quote will be wrong because shipping services need box size.
When calculating costs, you must pass all three variables: the origin ZIP, destination ZIP, and detailed measurements (length x width x height) for calculate_price_deadline.
Confusing tracking with pricing.
Asking, 'How much does it cost to get this package where it is?' The system needs the start and end points, not just the current status.
If you need a price, use calculate_price_deadline. If you only need location history, stick with track_object.
When It Fits, When It Doesn't
Use this MCP if your workflow requires real-time, official Brazilian logistics data for quoting or status checking. It's perfect for support chat automation and e-commerce checkout flows. Don't use it if you only need general shipping estimates that don't require specific zip codes; those are better handled by generic spreadsheet models. If you need to compare multiple different carriers (e.g., FedEx vs. Correios), this MCP is too narrow, and you should look at a multi-carrier comparison tool instead.
Questions you might have
Can I track an object using the `track_object` tool? +
Yes, you can use track_object to fetch the full history and current status of any package. Just provide a valid Brazilian tracking code.
How do I calculate shipping costs with `calculate_price_deadline`? +
You must pass three things: the origin zip, the destination zip, and the full dimensions/weight of the package. This ensures an accurate quote for any service.
Does this MCP handle international tracking? +
No, this MCP is designed specifically for Brazilian postal services (Correios). For international shipments, you'll need a different API tool.
What if I change the dimensions? Do I run `calculate_price_deadline` again? +
Yep. Because shipping rates are highly sensitive to package size, always re-run calculate_price_deadline whenever you adjust any dimension or weight.
What credentials are required before running `track_object`? +
You must provide your registered Correios User and Password to connect. You'll enter these details during the initial setup phase on Vinkius. This ensures your AI client can authenticate with the official API endpoints.
If I run `track_object` with an invalid or non-existent postal code, what response should I expect? +
The tool will return a structured error message indicating that the tracking number is invalid. This prevents guesswork and gives your agent a clear status to report back to the user.
Are there any limits on how often I can run the `calculate_price_deadline` tool in a single day? +
Yes, like all official APIs, there are rate limits. If you send too many requests quickly, you'll receive an API throttle error. It’s best practice to batch similar calculations or implement a short delay between calls.
When using `calculate_price_deadline`, must I specify the shipping service (like SEDEX or PAC)? +
Absolutely, you must name the specific service type. The price and deadline change drastically depending on whether it's a standard PAC shipment or an express SEDEX package.
What information do I need to calculate a shipping price? +
You need to provide the origin and destination ZIP codes (CEP), the service code (e.g., 04014 for SEDEX), weight, package format, and dimensions (length, height, width) using the calculate_price_deadline tool.
Can I track multiple objects at once? +
The track_object tool currently processes one tracking code per request to ensure detailed event history for that specific item.
What is the 'idLote' field in the shipping calculation? +
The idLote (Batch ID) is a required identifier for the Correios API request. It can be any string or number used to identify your specific calculation request in their logs.
We've already built the connector for Correios API. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 2 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.