An astronaut overseeing a futuristic data hub

Connect Brushfire to ChatGPT, Claude and Gemini

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. Run registrations and check-ins through your AI agent.

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

We ship only the actions that matter.

Capability set01 / 04

01-04

4 capabilities in this set.

Part of 16 available through Brushfire.

  1. 01

    Cancel attendee

    Administrative only: it does not move money, so handle refunds elsewhere. The attendee disappears from check-in lists, and it cannot be undone from this capability. Cancel one attendee registration by attendee ID. No financial change is made. it only marks the registration cancelled

  2. 02

    Get attendee

    This capability fetches the profile for a single registered guest.

  3. 03

    Get event

    This capability retrieves the metadata and details for a specific event.

  4. 04

    Get order

    Use this to grab specific details for a single transaction.

Capability set02 / 04

05-08

4 capabilities in this set.

Part of 16 available through Brushfire.

  1. 05

    List attendees

    This capability generates a list of all guests registered for an event.

  2. 06

    List ticket types

    Retrieve the different registration and ticket options available for an event.

  3. 07

    Set attendee completed

    Takes the attendee ID and completed ("true"/"false"). This is not check-in: check_in_attendee records arrival, this records that the person finished (a course, a shift, a station). Mark one attendee as completed (finished the event) or not completed, by attendee ID

  4. 08

    Archive event

    Brushfire is the soft-delete here. It is asynchronous: the request returns queued, and an email is sent once it is done. Hard to reverse. confirm the event name with the user first, and only archive events that are already over. Archive one event by ID. The event is queued for archiving and an email is sent on completion

Capability set03 / 04

09-12

4 capabilities in this set.

Part of 16 available through Brushfire.

  1. 09

    Check in attendee

    Mark a specific person as present at your event.

  2. 10

    Checkout attendee

    Takes the session ID and the ticket code, like check_in_attendee. Use it when someone was checked in by mistake or into the wrong session. Only works on attendees currently checked in. Reverse a check-in: check one attendee back out of a session using their ticket code

  3. 11

    Find attendee by email

    The fastest way to resolve "who is this person" when a guest only knows their email, and it yields the attendee ID that get_attendee, update_attendee and cancel_attendee need. Nothing back means the email is not registered. check the spelling or ask for the email used at purchase. Find attendees across all events by their email address, returning each match with name, event and attendee ID

  4. 12

    List events

    Use this to see all the events you currently manage.

Capability set04 / 04

13-16

4 capabilities in this set.

Part of 16 available through Brushfire.

  1. 13

    List orders

    Get a full list of all event orders and transactions.

  2. 14

    List sessions

    Always call this before list_attendees or check_in_attendee: in Brushfire, attendees belong to a session, not to the event, so those capabilities take a session ID, not an event ID. One event may hold many sessions (e.g. one per day). If several, pick the one the user means from its name and start time. List the check-in sessions of an event, with each session name, ID, start time and attendance counts. Sessions are the scope for listing and checking in attendees

  3. 15

    Resend order confirmation

    The answer to "I never got my tickets". resend instead of reading the order out. If you only know the buyer's email, find the order ID with list_orders first. The email goes to the address on the order, not to any other address. Resend the purchase confirmation email for one order, by order ID

  4. 16

    Update attendee

    This capability lets you modify existing attendee information.

Real work

What teams actually run

01

Rapid Guest Check-in

Staff members use the agent to mark attendees as present as they walk through the door.

02

Registration Audits

Organizers verify ticket types and registration counts to ensure event setup is correct.

03

Financial Monitoring

Finance teams check order histories and transaction statuses without logging into the full portal.

04

Attendee Data Updates

Users update guest profiles and contact information through simple text commands.

Automate a task

Put Brushfire to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Brushfire 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 Brushfire 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

955ms average. Fast in production.

Brushfire is checked daily against the live service.

Daily averagePeak 1235ms
Oct 3Today
Fastest day
835ms
Slowest day
1235ms
14-day trend
Stable+3%

Connect your client

One URL. Every client.

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

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

Brushfire Connector

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

Connector linkhttps://edge.vinkius.com/vk_preview_CXjX6UF6zbd07QPDVOdWhDMn3tbhjXSmrmtHk5Wn/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 — Brushfire capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "brushfire-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_CXjX6UF6zbd07QPDVOdWhDMn3tbhjXSmrmtHk5Wn/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 Brushfire in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Brushfire owners hand off.

This MCP is built for professionals who need to manage event logistics without staying glued to a dashboard.

  • 01

    Event Organizers

    They use the agent to check registration counts and attendee details quickly.

  • 02

    On-site Staff

    They perform guest check-ins and verify info via a mobile agent.

  • 03

    Finance Teams

    They monitor transaction statuses and event orders using natural language.

FAQ

Questions Brushfire owners ask.

  • 01

    How do I connect Brushfire to my AI client?

    You subscribe to the MCP on Vinkius and enter your Brushfire API Key and Client Version. Once connected, you can use it in any MCP-compatible client like Claude or Cursor.

  • 02

    Can I use this for on-site event check-ins?

    Yes. You can use the check_in_attendee capability to mark guests as present in real-time from your agent.

  • 03

    What information can my agent access?

    Your agent can access event metadata, attendee profiles, registration types, order histories, and account information.

  • 04

    Do I need to use the Brushfire dashboard for everything?

    No. This MCP allows you to perform most management tasks, like listing attendees or updating profiles, directly through your AI agent.

  • 05

    Which AI capabilities are compatible with this MCP?

    This MCP works with any client that supports the Model Context Protocol, including Claude, Cursor, and Windsurf.

  • 06

    Can I check-in an attendee using the agent?

    Yes! Use the check_in_attendee capability with the Attendee ID. Your agent will update the status in Brushfire instantly to mark the guest as present.

  • 07

    How do I see the list of all attendees for my event?

    Simply ask the agent to list_attendees and provide the Event ID. It will retrieve all the registered guests, including names and statuses, from your Brushfire account.

  • 08

    Does the integration allow updating attendee details?

    Yes. Use the update_attendee action and provide the Attendee ID along with the new name or email. The information will be synchronized with Brushfire immediately.

Connect Brushfire to Claude, Cursor, ChatGPT & more