An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Conversation State Machine 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. Keep your AI agents on a strict, logical path.

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.

A futuristic MCP client docking bay
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.

Curated set · 3 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-03

3 capabilities in this set.

Part of 3 available through Conversation State Machine.

  1. 01

    Get current context

    This capability provides a snapshot of the current conversational flow. It lets your agent see exactly which state it is in right now.

  2. 02

    Initialize fsm

    This capability sets up and validates a new conversation state machine. You use it to define your starting states and the rules for moving between them.

  3. 03

    Process turn

    This capability advances the conversation by evaluating the latest user interaction. It checks the input against your defined triggers to decide the next state.

Real work

What teams actually run

01

Guided Data Collection

Force an agent to ask a specific sequence of questions to gather user information without skipping steps.

02

Customer Support Routing

Move a user through a troubleshooting flow before allowing them to request a human agent.

03

Onboarding Flows

Ensure new users complete every necessary setup step in a logical order.

04

Deterministic Task Execution

Control an agent's progression through a multi-stage technical process.

One connector, every AI

Conversation State Machine 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.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

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

You don't need a client to put Conversation State Machine 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

839ms average. Fast in production.

Conversation State Machine is checked daily against the live service.

Daily averagePeak 1112ms
Oct 3Today
Fastest day
711ms
Slowest day
1112ms
14-day trend
Improving-9%

Connect your client

One URL. Every client.

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

It does not authenticate your account with Conversation State Machine. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Conversation State Machine Connector

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

Connector linkhttps://edge.vinkius.com/vk_preview_hJFcajDv8B5dbsu57MATXz9NIRSdBOFA3iCHEoGr/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 — Conversation State Machine capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "conversation-state-machine-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_hJFcajDv8B5dbsu57MATXz9NIRSdBOFA3iCHEoGr/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? Set up Conversation State Machine in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Conversation State Machine owners hand off.

This MCP is built for developers and engineers building autonomous agents that need to follow strict business logic.

  • 01

    AI Engineers

    Building agents that require predictable, multi-step reasoning paths.

  • 02

    Product Developers

    Creating conversational interfaces that must follow specific user journeys.

  • 03

    Automation Specialists

    Designing workflows where an agent must collect specific data before proceeding.

FAQ

Questions Conversation State Machine owners ask.

  • 01

    How does this MCP prevent AI drift?

    It uses a finite state machine to ensure the agent only moves between valid, predefined states based on specific triggers.

  • 02

    What triggers can I use to change states?

    You can use keyword matches, intent classification, or a turn count threshold to trigger a transition.

  • 03

    Which AI clients can use this MCP?

    Any MCP-compatible client like Claude, Cursor, or Windsurf can use this capability.

  • 04

    Do I need to host the state machine myself?

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

  • 05

    Can I use this for simple one-off questions?

    While possible, this MCP is specifically designed for multi-turn, structured conversations that require state management.

  • 06

    How does the state machine prevent conversation drift?

    It uses deterministic transitions. A transition only occurs when a specific trigger condition, such as a keyword_match, is met, ensuring the agent follows a predefined path.

  • 07

    Can I trigger transitions based on capability results?

    Yes, you can use the tool_result_status trigger to move to a new state based on whether the last capability execution was a success or a failure.

  • 08

    What happens if no transition condition is met?

    If no trigger conditions match the current input, the agent remains in its current state.

Explore

More in Logic

Suggestions

Connect Conversation State Machine to Claude, Cursor, ChatGPT & more