4,000+ servers built on MCP Fusion
Vinkius
CrewAIFramework
Why use OpenCage MCP Server with CrewAI?

Bring Geocoding
to CrewAI

Create your Vinkius account to connect OpenCage to CrewAI and start using all 10 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.

MCP Inspector GDPR Free for Subscribers
Geocode All Duplicate ResultsGeocode BasicGeocode Bounding BoxGeocode Country FilterGeocode High ConfidenceGeocode Language BiasGeocode No Record PrivacyReverse BasicReverse Fast No AnnotationsReverse Fetch Time Annotations
ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
OpenCage

What is the OpenCage MCP Server?

Give your AI agent precise geolocation superpowers with OpenCage Geocoding. Convert any address into coordinates, reverse-geocode GPS pins into readable addresses, and apply advanced filters — all through natural conversation.

What you can do

  • Forward Geocoding — Convert any address or place name into exact latitude/longitude coordinates
  • Reverse Geocoding — Turn GPS coordinates into structured street addresses with timezone and sun data
  • Country Filtering — Restrict results to a specific country (ISO 3166-1 Alpha-2) to avoid ambiguous city matches
  • Language Bias — Request results localized in any IETF language code (e.g., pt-BR, fr-FR)
  • Confidence Scoring — Filter geocoding results by minimum confidence level (1–10) for delivery-grade accuracy
  • Bounding Box — Constrain results to a geographic rectangle for targeted regional searches
  • Privacy Mode — Run geocoding queries without OpenCage logging them, for sensitive addresses
  • Duplicate Control — Return or suppress duplicate results for data validation workflows

How it works

  1. Subscribe to this server
  2. Enter your OpenCage API Key
  3. Start geocoding from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Logistics teams — validate delivery addresses before dispatching drivers to avoid failed deliveries
  • Data engineers — enrich datasets with lat/lng coordinates and timezone metadata at scale
  • Privacy-conscious apps — geocode sensitive addresses without leaving a trace in third-party logs

Built-in capabilities (10)

geocode_all_duplicate_results

Retrieve the exact structural matching verifying Delivery alternatives

geocode_basic

Identify bounded routing spaces inside the Headless OpenCage Engine

geocode_bounding_box

Inspect deep internal arrays mitigating specific Polygon domains

geocode_country_filter

Perform structural extraction of properties driving active Country nodes

geocode_high_confidence

Dispatch an automated validation check routing explicit Score limits

geocode_language_bias

Retrieve explicit Cloud logging tracing explicit Payload locales

geocode_no_record_privacy

Provision a highly-available JSON Payload generating secure mappings

reverse_basic

Enumerate explicitly attached structured rules exporting active GPS pins

reverse_fast_no_annotations

Identify precise active arrays spanning native Location limits faster

reverse_fetch_time_annotations

Irreversibly vaporize explicit validation limits extracting UTC logic

Why CrewAI?

When paired with CrewAI, OpenCage becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call OpenCage 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 mcps parameter 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

See it in action

OpenCage in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Enterprise Security

Why run OpenCage with Vinkius?

The OpenCage connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 10 tools are ready to work instantly without any complex setup.

You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

OpenCage
Fully ManagedNo server setup
Plug & PlayNo coding needed
SecurePrivacy protected
PrivateYour data is safe
Cost ControlBudget limits
Control1-click disconnect
Auto-UpdatesMaintenance free
High SpeedOptimized for AI
Reliable99.9% uptime
Your credentials and connection tokens are fully encrypted

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure

01 / Catalog

Over 4,000 integrations ready for AI agents

Explore a vast library of pre-built integrations, optimized and ready to deploy.

02 / Credentials

Connect securely in under 30 seconds

Generate tokens to authenticate and link external services in a single step.

03 / Guardian

Complete visibility into every agent action

Audit live requests, latency, success rates, and active security compliance policies.

04 / FinOps

Optimize spending and track token ROI

Analyze real-time token consumption and cost metrics detailed by connection.

Over 4,000 integrations ready for AI agents
Connect securely in under 30 seconds
Complete visibility into every agent action
Optimize spending and track token ROI

Explore our live AI Agents Analytics dashboard to see it all working

This dashboard is included when you connect OpenCage using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.

Why Vinkius

OpenCage and 4,000+ other AI tools. No hosting, no code, ready to use.

Professionals who connect OpenCage to CrewAI through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.

4,000+MCP Integrations
<40msResponse time
100%Fully managed
Raw MCP
Vinkius
Ready-to-use MCPsFind and configure each manually4,000+ MCPs ready to use
Connection SetupManual coding & server setup1-click instant connection
Server HostingYou host it yourself (needs 24/7 uptime)100% hosted & managed by Vinkius
Security & PrivacyStored in plaintext config filesBank-grade encrypted vault
Activity VisibilityBlind execution (no logs or tracking)Live dashboard with real-time logs
Cost ControlRunaway AI token spend riskAutomatic budget limits
Revoking AccessMust delete files or code to stop1-click disconnect button
The Vinkius Advantage

How Vinkius secures OpenCage for CrewAI

Every request between CrewAI and OpenCage is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How accurate is the geocoding — can I use it for delivery routing?

OpenCage returns a confidence score from 1 to 10 for each result. Use the high-confidence filter (min_confidence=8 or higher) to get delivery-grade accuracy. Combined with country filtering, you can eliminate ambiguous matches and get coordinates reliable enough for last-mile dispatch.

02

What does privacy mode actually do?

When you enable no_record=1, OpenCage processes your query but doesn't log it in their cache or analytics. The result is identical, but the query leaves no trace on their servers. Ideal for geocoding patient addresses, legal documents, or any PII-sensitive data.

03

Can I geocode in multiple languages — like getting results in Portuguese for a Brazilian address?

Yes. Use the language bias tool with any IETF language code (pt-BR, es-MX, fr-FR, etc.) and OpenCage returns the address components translated to that locale. Perfect for building multilingual apps or standardizing address formats across regions.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

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 →