What kind of data does this MCP need?

It works best when you provide site names, operating hours, and specific areas of interest like architecture or military history.

Can I use this with Claude or Cursor?

Yes, you can connect this MCP to any MCP-compatible client including Claude, Cursor, and Windsurf.

Does it help with accessibility needs?

Yes, the capability can identify specific preparation actions, such as verifying ramp locations or booking accessible tours.

How does it help me observe things better?

The engagement guide capability provides specific prompts to help you notice details like stone carvings or structural techniques during your visit.

Is the hosting handled by Vinkius?

Yes, Vinkius hosts the MCP and manages the connection so it is ready to use immediately.

Download PDF Markdown Version

Connect Local History Experience Planner to your AI

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 raw historical data into structured, actionable visit plans.

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 History Experience Plan capability set.

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

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Local History Experience Plan.

01
Generate preparation actions
This capability identifies the specific tasks you need to finish to ensure your visit goes smoothly. It handles things like checking accessibility requirements or booking timed entries.
02
Create engagement guide
This capability generates personalized prompts for your visit. It tells you exactly what to observe or interact with based on your specific interests.
03
Plan itinerary
This capability builds the optimal chronological sequence for your historical sites. It organizes your stops into a logical order for your trip.
04
Suggest followup plan
This capability provides ways to extend your learning after the physical tour is finished. It suggests paths to deepen your understanding of what you just saw.

One connector, every AI

Local History Experience Plan 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 History Experience Plan 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 History Experience Plan, so you can see the experience inside your AI.

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

Local History Experience Plan Connector

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

Connector linkhttps://edge.vinkius.com/vk_preview_ySDhzTyOZIaB8WPPPsuMlQ7ohIULFZLedPYZZ2Zh/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 History Experience Plan capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "local-history-experience-planner-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_ySDhzTyOZIaB8WPPPsuMlQ7ohIULFZLedPYZZ2Zh/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 History Experience Plan

See all the AI clients this connector works with ↑

Who it's for

Built for the work Local History Experience Plan owners hand off.

This MCP is built for anyone who needs to turn raw historical data into a structured experience. It's ideal for professionals and enthusiasts who want to move from data to a finished plan quickly.

01
Tour Operators
Hand off site data and client interests to the AI to generate structured itineraries and engagement guides.
02
History Educators
Use the capability to create detailed observation prompts and follow-up learning paths for students.
03
Travel Planners
Delegate the task of sequencing site visits and checking accessibility requirements to your agent.

FAQ

Questions Local History Experience Plan owners ask.

01
What kind of data does this MCP need?
It works best when you provide site names, operating hours, and specific areas of interest like architecture or military history.
02
Can I use this with Claude or Cursor?
Yes, you can connect this MCP to any MCP-compatible client including Claude, Cursor, and Windsurf.
03
Does it help with accessibility needs?
Yes, the capability can identify specific preparation actions, such as verifying ramp locations or booking accessible tours.
04
How does it help me observe things better?
The engagement guide capability provides specific prompts to help you notice details like stone carvings or structural techniques during your visit.
05
Is the hosting handled by Vinkius?
Yes, Vinkius hosts the MCP and manages the connection so it is ready to use immediately.

Explore

More in Productivity

Connect Local History Experience Plan to Claude, Cursor, ChatGPT & more

Connect Local History Experience Planner to your AI

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