What clients can I use with this MCP?

You can use this with any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.

How does it handle accessibility?

The capability incorporates accessibility needs into the visit sequence to ensure the plan is feasible for the group.

Can it help with group meetups?

Yes, it uses a specific capability to define meeting protocols, including where and when the group should gather.

Does it account for venue hours?

Yes, the planning logic respects venue opening hours and ticket constraints when building sequences.

Do I need to host the MCP myself?

No, Vinkius hosts and manages the MCP for you, so it is ready to use once you connect.

Download PDF Markdown Version

Connect Local Culture Plan Engine to ChatGPT and Claude

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Turn cultural interests into actionable, timed visit sequences.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

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

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

How Vinkius works: one connection, every tool, in any AI

V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Complete set · 4 capabilities

The complete Local Culture Plan Engine capability set.

These are the exact actions your AI can choose when you ask it to work with Local Culture Plan Engine.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Local Culture Plan Engine.

01
Get advance actions
This capability identifies the specific prep work your group needs to finish before heading out.
02
Get feasible sequence
Use this to find a valid order of visits that fits your specific time and accessibility constraints.
03
Get meeting protocol
This capability defines exactly how and where your group should gather for a visit.
04
Get transition plan
This capability establishes the specific movement commitments required to get from one stop to the next.

One connector, every AI

Local Culture Plan Engine works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Local Culture Plan Engine to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 4 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Local Culture Plan Engine, so you can see the experience inside your AI.

It does not authenticate your account with Local Culture Plan Engine. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Local Culture Plan Engine Connector

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

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

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — Local Culture Plan Engine capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "local-culture-plan-engine-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_4eHLfVE4otO9YcV3funUXqdbWhBVlkEJeQsDKG36/mcp"
    }
  }
}

Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? How to give Claude access to Local Culture Plan Engine

See all the AI clients this connector works with ↑

Who it's for

Built for the work Local Culture Plan Engine owners hand off.

This MCP is built for anyone coordinating group travel or cultural itineraries who needs to move past vague plans into real logistics.

01
Travel Coordinators
They hand off the task of calculating feasible visit orders and timing to the AI.
02
Event Organizers
They use the capability to define meeting protocols and transition plans for attendees.
03
Accessibility Consultants
They rely on the capability to ensure all planned sequences respect specific mobility needs.

FAQ

Questions Local Culture Plan Engine owners ask.

01
What clients can I use with this MCP?
You can use this with any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.
02
How does it handle accessibility?
The capability incorporates accessibility needs into the visit sequence to ensure the plan is feasible for the group.
03
Can it help with group meetups?
Yes, it uses a specific capability to define meeting protocols, including where and when the group should gather.
04
Does it account for venue hours?
Yes, the planning logic respects venue opening hours and ticket constraints when building sequences.
05
Do I need to host the MCP myself?
No, Vinkius hosts and manages the MCP for you, so it is ready to use once you connect.

Explore

More in Logistics

Connect Local Culture Plan Engine to Claude, Cursor, ChatGPT & more

Connect Local Culture Plan Engine to ChatGPT and Claude

Your AI does the work. We keep it safe and sound.