Connect Local History Project Manager 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. Organize community research from initial planning to final presentation.

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.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

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 · 5 capabilities

The complete Local History Project Manager capability set.

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

Capability set01 / 02

01-03

3 capabilities in this set.

Part of 5 available through Local History Project Manager.

  1. 01

    Create evidence log entry

    Use this to record new historical evidence or specific interactions with research participants.

  2. 02

    Generate research plan

    This capability builds a structured roadmap for your project based on the initial details you provide.

  3. 03

    Schedule presentation

    This capability helps you organize the final steps for sharing your research findings with the public.

Capability set02 / 02

04-05

2 capabilities in this set.

Part of 5 available through Local History Project Manager.

  1. 04

    Validate consent status

    This capability checks if a specific contributor or location has granted the required permissions for your work.

  2. 05

    Compose outreach message

    This capability drafts professional messages for you to send to potential research participants or site managers.

One connector, every AI

Local History Project Manager 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 Project Manager 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.

Observed, not estimated

1281ms average. Fast in production.

Local History Project Manager is checked daily against the live service.

Daily averagePeak 1281ms
Sep 25Today
Fastest day
1281ms
Slowest day
1281ms
14-day trend
Stable0%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 5 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 Project Manager, so you can see the experience inside your AI.

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

Local History Project Manager Connector

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

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

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Local History Project Manager capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "local-history-project-manager-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_eO1ejIVksS3hRskGuobADqjnhf76TwJapgtPAHAM/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 Project Manager

See all the AI clients this connector works with ↑

Who it's for

Built for the work Local History Project Manager owners hand off.

This MCP is designed for people conducting structured community-based historical investigations.

  • 01

    Local Historians

    They hand off the task of organizing research roadmaps and logging evidence to the AI.

  • 02

    Community Researchers

    They use the MCP to manage ethical consent and participant outreach.

  • 03

    Archivists

    They use the capability to document findings and schedule public presentations.

FAQ

Questions Local History Project Manager owners ask.

  • 01

    What can this MCP do for my research project?

    It manages the full research lifecycle, including planning, participant outreach, evidence logging, consent verification, and presentation scheduling.

  • 02

    Which AI clients can I use with this MCP?

    You can use this MCP with any compatible client like Claude, Cursor, or Windsurf.

  • 03

    How does the MCP help with ethical research?

    It includes a capability to validate consent status, ensuring you have the necessary permissions from contributors and sites.

  • 04

    Can I use this to contact people for interviews?

    Yes, the MCP has a capability to compose professional outreach messages for potential participants or site managers.

  • 05

    Do I need to host the MCP myself?

    No, Vinkius hosts and manages the MCP for you, so it is ready to use immediately after you connect your client.

  • 06

    How do I start a new research project?

    You can start by using the generate_research_plan capability, which creates a structured roadmap based on your topic, locations, and timeline.

  • 07

    How does the server handle participant consent?

    The server enforces strict ethical compliance. You must use validate_consent_status to verify that a contributor has provided explicit permission before recording any evidence.

  • 08

    Can I use this to organize public presentations?

    Yes, the schedule_presentation capability allows you to organize the final dissemination of your findings to audiences like community boards or libraries.

Connect Local History Project Manager to Claude, Cursor, ChatGPT & more