Connect Accessible Ticketing Decision Plan 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. Ensure every ticket meets physical needs and budget limits.

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

The complete Accessible Ticketing Decision Plan capability set.

These are the exact actions your AI can choose when you ask it to work with Accessible Ticketing Decision Plan.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Accessible Ticketing Decision Plan.

  1. 01

    Determine fallback option

    This capability identifies a secondary ticket choice if your first option is unavailable or unsuitable.

  2. 02

    Analyze ticket feasibility

    This capability checks if a specific ticket type satisfies both your budget and accessibility requirements.

  3. 03

    Generate purchase checklist

    This capability creates a list of logistical steps you need to take to complete the purchase.

  4. 04

    Validate compliance terms

    This capability extracts and formats legal terms and specific venue features for your review.

One connector, every AI

Accessible Ticketing Decision 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 Accessible Ticketing Decision 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.

Observed, not estimated

1040ms average. Fast in production.

Accessible Ticketing Decision Plan is checked daily against the live service.

Daily averagePeak 1234ms
Sep 24Today
Fastest day
1009ms
Slowest day
1234ms
14-day trend
Slowing+12%

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 Accessible Ticketing Decision Plan, so you can see the experience inside your AI.

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

Accessible Ticketing Decision Plan Connector

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

Connector linkhttps://edge.vinkius.com/vk_preview_qsPFWN6CmxCJUfpGq7JkHwV5rzNjVsUNCMamRDXo/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 — Accessible Ticketing Decision Plan capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "accessible-ticketing-decision-plan-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_qsPFWN6CmxCJUfpGq7JkHwV5rzNjVsUNCMamRDXo/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 Accessible Ticketing Decision Plan

See all the AI clients this connector works with ↑

Who it's for

Built for the work Accessible Ticketing Decision Plan owners hand off.

This MCP is built for anyone managing event logistics where accessibility is a primary concern. It helps users move from searching for tickets to having a verified plan.

  • 01

    Event Coordinators

    They hand off accessibility requirements and budget limits to the agent to find compliant seating.

  • 02

    Accessibility Advocates

    They use the capability to verify that venue features like ramps or hearing loops meet specific user needs.

  • 03

    Personal Assistants

    They rely on the generated checklists to manage purchase deadlines and companion policies.

FAQ

Questions Accessible Ticketing Decision Plan owners ask.

  • 01

    How does this MCP handle accessibility needs?

    It treats accessibility requirements, such as wheelchair access or sensory accommodations, as non-negotiable constraints that take priority over other preferences.

  • 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

    What happens if my first ticket choice is too expensive?

    The MCP uses the determine_fallback_option capability to find a secondary choice that meets your requirements.

  • 04

    Does it help with venue rules?

    Yes, it uses the validate_compliance_terms capability to extract and format legal terms and venue features for you.

  • 05

    Will it help me remember to buy tickets on time?

    The generate_purchase_checklist capability produces a list of logistical actions, including deadlines, to help you complete the purchase.

  • 06

    How does the engine handle accessibility needs?

    The engine uses analyze_ticket_feasibility to ensure that mandatory accessibility requirements are satisfied before considering any other preferences or budget factors.

  • 07

    What happens if my first choice of ticket is unavailable?

    You can use the determine_fallback_option capability to find an alternative ticket that still respects your mandatory accessibility needs and budget ceiling.

  • 08

    Does the capability account for companion tickets?

    Yes, the feasibility analysis includes the cost of companion tickets if they are required by the venue's companion policy.

Connect Accessible Ticketing Decision Plan to Claude, Cursor, ChatGPT & more