Lovable

How to give Lovable access to Itinerary Day Count

Set up in seconds, once. From then on, Lovable gets things done for you: Itinerary Day Count becomes one of its chat connectors, ready while it builds.

Ask AI about this guide

Itinerary Day Count Connector

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

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

Connecting Itinerary Day Count to Lovable

About a minute, in the Connectors catalog

  1. 1Open Connectors, select the + button in the top right of the catalog, and choose MCP server.
  2. 2Name the server and paste your Itinerary Day Count link as the Server URL. The link above is the URL.
  3. 3Choose No authentication and click Add server, then ask Lovable something real. Itinerary Day Count is now part of Lovable.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "itinerary-day-count-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_yGvJUyE6hVroNhjlfur6kLEQsXn4srlb1xqw9dAB/mcp"
    }
  }
}

Lovable + Itinerary Day Count

One chat. Your Itinerary Day Count, live inside Lovable.

Real prompts, answered with live data. This is the kind of conversation you will have in Lovable once the connector is in.

Waiting for input…

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

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

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

The full capability set, the prompts and the observed latency live on the Itinerary Day Count Connector page.

Mission Control

See everything your Lovable agents do in Itinerary Day Count.

When Lovable runs a tool in Itinerary Day Count, it happens on Lovable's side: you see the result in the chat, 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
0
Total in this period
Avg Latency
0
API 88ms · Overhead 54ms
Vinkius Reliability
0
Agent 280 · Upstream 47 · Vinkius 15
Tokens
0
AI tokens processed
DLP Protected
0
Sensitive data redacted
Cost Saved
0
FinOps truncations applied

AI Agents Activities

last 30 days
30d agotoday

Request Volume & Latency

requests latency

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

What sets us apart

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

Connecting Itinerary Day Count to your AI is step one. But an open line between your agents and Itinerary Day Count 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.

01

Tamper Proof Activity Log

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

02

Automatic Key Rotation

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

03

Spending Protection

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

04

Isolated Sandbox

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

05

Security Event Streaming

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

06

Instant Resume

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

07

Malicious File Protection

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

08

Credential Validation

We test your Itinerary Day Count credentials before saving them. Invalid credentials are rejected instead of being stored.

09

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 Itinerary Day Count connection runs on. Read how our infrastructure protects everything your Lovable agents do, end to end.

Inside Vinkius

Get Itinerary Day Count ready for your AI. It's easy.

You choose Itinerary Day Count from the Vinkius Catalog and get one connection link. That's it.

  1. You choose Itinerary Day Count

    You find Itinerary Day Count in the Catalog and install the Connector with one click.

    Itinerary Day Count

    Active

    Enable Connector
    Activating…

  2. You add the link in Lovable

    Vinkius gives you one connection link. In Lovable, you add a custom MCP server in the Connectors catalog with the link as the Server URL.

    Token generated successfully

    MCP Connection URL

    https://edge.vinkius.com/vk_preview_yGvJUyE6hVroNhjlfur6kLEQsXn4srlb1xqw9dAB/mcp

    Connection Token

    vk_live_••••••••
    Go to Dashboard

Set it up once. Use Itinerary Day Count with the AI you already use.

FAQ

Lovable access questions.

  • 01

    Does this work in my published apps?

    No. Custom MCP connectors are personal chat connectors: they work in your Lovable chat while it builds for you, but visitors can't reach the tool through your published app.

  • 02

    If I connect Itinerary Day Count to Lovable, can I use the same connection in Claude or ChatGPT later?

    Yes, and that's the point: the connection is yours, not Lovable'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 Itinerary Day Count is already there.

  • 03

    What does Lovable need to connect to Itinerary Day Count?

    Just the link. Choose No authentication as the auth option, because the hosted Connector handles access on our side. If you prefer OAuth, pick it and you'll be prompted to authorize.

  • 04

    What can I actually ask Lovable to do with Itinerary Day Count?

    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

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

    Make sure the Server URL was pasted exactly as copied and the connector is authorized, then confirm the Connector is active in your Vinkius account. A deactivated Connector stops responding.

  • 06

    Can I remove the access later?

    Remove the connector in Connectors and it's out of your chats. Your Vinkius account keeps the connection and its history either way, ready for the next AI.

  • More questions about Itinerary Day Count? The Connector page answers them. See everything the Itinerary Day Count Connector can do

About the Connector

What Itinerary Day Count adds to your AI.

Once you connect it, your AI gains 4 capabilities: the exact actions it can take in Itinerary Day Count 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 Itinerary Day Count Connector can do