Bring Correios
to CrewAI
Learn how to connect Correios API (REST) to CrewAI and start using 2 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Correios API (REST) MCP Server?
Connect your AI agent to the Correios infrastructure to automate logistics queries in Brazil. This server provides direct access to the official REST API for real-time tracking and shipping simulations.
What you can do
- Object Tracking — Get the full history of events and current status for any valid tracking code (e.g., AA123456789BR) using the
track_objecttool. - Shipping Calculation — Simulate prices and delivery deadlines for various services like SEDEX and PAC based on weight, dimensions, and zip codes with
calculate_price_deadline. - Logistics Automation — Integrate shipping data into your e-commerce or support workflows without manual lookups.
How it works
- Subscribe to this server
- Enter your Correios API credentials (User and Password)
- Start querying logistics data from Claude, Cursor, or any MCP client
Who is this for?
- E-commerce Owners — quickly check delivery statuses for customers and provide proactive updates.
- Logistics Managers — automate shipping cost estimations for different regions in Brazil directly from the terminal or chat.
- Support Teams — provide instant tracking updates within AI-powered chat interfaces without leaving the conversation.
Built-in capabilities (2)
Uses POST but acts as a query. Calculate shipping price and deadline
Track a postal object
Why CrewAI?
When paired with CrewAI, Correios API (REST) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Correios API (REST) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Correios API (REST) in CrewAI
Correios API (REST) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Correios API (REST) to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Correios API (REST) in CrewAI
The Correios API (REST) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 2 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Correios API (REST) for CrewAI
Every tool call from CrewAI to the Correios API (REST) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
BIMobject
10 toolsAccess BIMobject marketplace — search building products, download technical files, and manage manufacturer data directly from any AI agent.
Mav
9 toolsLet AI text your leads automatically with human-like conversations that schedule appointments and qualify prospects by SMS.
Dime.Scheduler
7 toolsPlan field service teams visually with drag-and-drop scheduling that connects to your ERP for real-time resource allocation.
Imagine.io
10 toolsCreate 3D product visualizations and room renders from photos using AI that turns concepts into photorealistic images.