Does this work in the Gemini web and mobile apps?

Not yet. The Gemini apps use built-in Connected Apps that you toggle on and off, and they don't accept custom Connector links today. The supported path is the free Gemini CLI, where the same link runs OpenRouteService in your terminal.

If I connect OpenRouteService to Gemini, can I use the same connection in Claude or ChatGPT later?

Yes, and that's the point: the connection is yours, not Gemini's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and OpenRouteService is already there.

Do I need to hand my OpenRouteService password to Gemini?

Never. You sign in once at Vinkius, and we keep your logins encrypted and away from your AI. Gemini only ever sees the link, and you can remove it whenever you want.

What can I actually ask Gemini to do with OpenRouteService?

Whatever the Connector covers: check data, run actions and bring answers back. The Connector page lists every capability your AI gains, with real examples you can copy.

Gemini doesn't show the Connector. What do I check?

Run gemini mcp list and check that the status shows CONNECTED, confirm the Connector is active in your Vinkius account, then run the add command again if needed. A deactivated Connector stops responding.

Can I remove the access later?

Anytime. Run gemini mcp remove and it's out of your terminal. Your Vinkius account keeps the connection and its history either way, ready for the next AI.

How to give Gemini access to OpenRouteService

Set up in seconds, once. From then on, Gemini gets things done for you: run one command, and the Gemini CLI uses OpenRouteService live in your terminal.

Ask AI about this guide

OpenRouteService Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_PSUHMhycOvqpomQ4KyrnDt17AfCQwXu8mm8OMYhJ/mcp

Connecting OpenRouteService to Gemini

About a minute, right in your terminal

1Open the Gemini CLI in your terminal.
2Run: gemini mcp add --transport http OpenRouteService <your link>. Your OpenRouteService link above is the HTTP URL.
3Run /mcp and confirm the status shows CONNECTED. OpenRouteService is now part of your Gemini.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "openrouteservice-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_PSUHMhycOvqpomQ4KyrnDt17AfCQwXu8mm8OMYhJ/mcp"
    }
  }
}

Gemini + OpenRouteService

One chat. Your OpenRouteService, live inside Gemini.

Real prompts, answered with live data. This is the kind of conversation you will have in the Gemini CLI once the link is in.

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

These prompts ship with the OpenRouteService Connector. Once yours is connected, they work in your sessions.

The full capability set, the prompts and the observed latency live on the OpenRouteService Connector page.

Mission Control

See everything your Gemini agents do in OpenRouteService.

When Gemini runs a tool in OpenRouteService, it happens in the terminal: you see the result, but not the request itself, what data it carried, or whether a rule was broken.

Now every move lands on your screen.

Every execution is recorded, enforced, and shown to you: what ran, what it returned, what was blocked, and why.

AI Briefing

Upgrade to unlock

Know exactly what needs your attention before you even look at the charts. One briefing. The full picture. The next move.

Requests

Total in this period

Avg Latency

API 88ms · Overhead 54ms

Vinkius Reliability

Agent 280 · Upstream 47 · Vinkius 15

Tokens

AI tokens processed

DLP Protected

Sensitive data redacted

Cost Saved

FinOps truncations applied

AI Agents Activities

last 30 days

30d agotoday

Request Volume & Latency

requests latency

Every request your Gemini agents make through OpenRouteService is logged, enforced and auditable. See how AI Governance turns agent activity into accountability, and what it means for your OpenRouteService workflows.

What sets us apart

It's not just the Connector that stays safe. Everything your agents do through it is.

Connecting OpenRouteService to your AI is step one. But an open line between your agents and OpenRouteService is only half the story: without protection, every action they take runs unguarded.

That's why protection doesn't stop at the door.

Every action your agents take through the Connector runs inside our infrastructure: signed activity logs, automatic key rotation, spending limits that pause instead of surprise, and a sandbox that isolates every execution.

Tamper Proof Activity Log

Every request your agents make in OpenRouteService is recorded and signed, so any change to the history becomes detectable.

Automatic Key Rotation

We rotate security keys every 24 hours. Your OpenRouteService connection stays protected without any manual work.

Spending Protection

We enforce the spending limit you choose and pause actions that exceed it until approval is received. Your OpenRouteService actions never surprise you.

Isolated Sandbox

Every execution through OpenRouteService runs isolated, with 34+ security rules covering memory, CPU, network access, file handling and execution.

Security Event Streaming

Security events flow to Splunk, Datadog or your own webhook, so OpenRouteService activity lands in the tools you already rely on.

Instant Resume

Idle connections resume in 3 to 5 ms while preserving their state, keeping your Gemini sessions responsive.

Malicious File Protection

We detect compressed files designed to exhaust system resources and block them before they ever reach OpenRouteService.

Credential Validation

We test your OpenRouteService credentials before saving them. Invalid credentials are rejected instead of being stored.

Separate Usage Limits

Usage stays isolated per account, so activity in one connection never consumes another account's allowance.

One Connector, one link, and the whole operation is protected. Not just the connection: everything your agents do through it.

These guarantees are not add-ons: they are the infrastructure every OpenRouteService connection runs on. Read how our infrastructure protects everything your Gemini agents do, end to end.

Inside Vinkius

Get OpenRouteService ready for your AI. It's easy.

You choose OpenRouteService from the Vinkius Catalog, sign in to your OpenRouteService account, and get one connection link. That's it.

You choose OpenRouteService
You find OpenRouteService in the Catalog and install the Connector with one click.
OpenRouteService
Active
Enable Connector
Activating…
You sign in
You connect your OpenRouteService account and choose what you want your AI to access. Your credentials stay encrypted and separate from your AI.
Configure Credentials
Configure credentials for {{connectorName}}
OpenRouteService sign-inRequiredEncrypted
Save & Continue
Encrypted Storage
Your credentials are encrypted at rest and in transit.
Never Shared
Your credentials are never shared with third parties.
Full Control
Revoke or update credentials at any time.
You add the link in the Gemini CLI
Vinkius gives you one connection link. In the Gemini CLI, you run one gemini mcp add command with the link as the HTTP URL, and the connection is ready.
Token generated successfully
MCP Connection URL
https://edge.vinkius.com/vk_preview_PSUHMhycOvqpomQ4KyrnDt17AfCQwXu8mm8OMYhJ/mcp
Connection Token
vk_live_••••••••
Go to Dashboard

Set it up once. Use OpenRouteService with the AI you already use.

FAQ

Gemini access questions.

01
Does this work in the Gemini web and mobile apps?
Not yet. The Gemini apps use built-in Connected Apps that you toggle on and off, and they don't accept custom Connector links today. The supported path is the free Gemini CLI, where the same link runs OpenRouteService in your terminal.
02
If I connect OpenRouteService to Gemini, can I use the same connection in Claude or ChatGPT later?
Yes, and that's the point: the connection is yours, not Gemini's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and OpenRouteService is already there.
03
Do I need to hand my OpenRouteService password to Gemini?
Never. You sign in once at Vinkius, and we keep your logins encrypted and away from your AI. Gemini only ever sees the link, and you can remove it whenever you want.
04
What can I actually ask Gemini to do with OpenRouteService?
Whatever the Connector covers: check data, run actions and bring answers back. The Connector page lists every capability your AI gains, with real examples you can copy.
05
Gemini doesn't show the Connector. What do I check?
Run gemini mcp list and check that the status shows CONNECTED, confirm the Connector is active in your Vinkius account, then run the add command again if needed. A deactivated Connector stops responding.
06
Can I remove the access later?
Anytime. Run gemini mcp remove and it's out of your terminal. Your Vinkius account keeps the connection and its history either way, ready for the next AI.
More questions about OpenRouteService? The Connector page answers them. See everything the OpenRouteService Connector can do

About the Connector

What OpenRouteService adds to your AI.

Once you connect it, your AI gains 10 capabilities: the exact actions it can take in OpenRouteService when you ask. The Connector page lists every one of them in detail, alongside the latency we measure in production and prompts worth trying first.

See everything the OpenRouteService Connector can do