VEXiON MCP server

Run your loyalty program from Claude, ChatGPT, Cursor and other AI assistants. Connect once, then look up customers, record transactions, build cards and send notifications in plain language.

The VEXiON MCP server lets an AI assistant work with your VEXiON account. You connect it once, then ask in plain language: “How many new customers did we get this month?”, “Create a stamp card for the new cafe”, “Email Anna her card”.

It uses the Model Context Protocol (MCP), an open standard that AI assistants use to talk to other software. Any MCP client can connect. VEXiON runs the server for you, so there is nothing to install.

Server URL	https://api.vexioncards.one/mcp
Transport	Streamable HTTP
Sign-in	OAuth with your VEXiON account (default) or a VEXiON API key
Who can connect	Admins of a business on VEXiON PRO
Tools	31, see the tool list

​

What an assistant can do

Answer questions

Totals, trends and comparisons for transactions, rewards and new customers, by day, week, month, card or location.

Look things up

Find a customer by email, phone or scanned pass value. Read cards, locations, products and past notifications.

Make changes

Create and edit cards, customers, products and locations. Record stamps, points and redemptions.

Reach customers

Send a push notification to wallet cards, or email one customer their card link. Always with a preview first.

​

How it works

The assistant never gets your password. It gets a sign-in for the businesses you chose, each with the access level you chose. Every call is checked against that choice, business by business, and you can revoke it at any time. A tool you did not allow is not shown to the assistant at all.

​

Requirements

• A business on VEXiON PRO. VEXiON ONE does not include AI assistants.
• You are an admin of that business. Managers and scanners cannot connect an assistant.
• An active business. A paused, locked or cancelled business cannot be used until it is active again.
• An AI client that supports remote MCP servers over Streamable HTTP. Clients that only support the older SSE transport are not supported.

Developers using an API key need an API key on a plan that includes API access. See Introduction.

​

Connect an assistant

Menus in AI apps change often. If a label differs, follow your app’s own steps for adding a remote MCP server and use the URL below.

Every client needs the same server URL:

https://api.vexioncards.one/mcp

​

Choose how to sign in

	OAuth (default)	API key
Best for	Business owners and admins	Developers, scripts, automation
How	Sign in with your VEXiON account in the browser	Send a VEXiON API key in the Authorization header
Access is chosen by	You, on the VEXiON consent screen	The scopes of the key
Revoke	Settings > Developer > AI assistants	Revoke the key in Settings > Developer
Works in	Claude, ChatGPT, Claude Code, Cursor, VS Code, Gemini CLI	Clients that let you set a request header

Use OAuth whenever your client supports it. Use an API key when there is no browser, for example in CI or a server-side agent.

An API key is a secret. Never paste it into a chat, commit it, or hard-code it in a shared file. Put it in an environment variable, as the examples below do.

​

Connect with OAuth

Claude.ai and Claude Desktop

Custom connectors work in Claude on the web and in Claude Desktop.

1. Open Connectors

   Go to Customize > Connectors. Click + Add, then Add custom connector.

2. Add the server

   Name it VEXiON, paste https://api.vexioncards.one/mcp and click Continue. Keep the default sign-in settings and click Add.

3. Sign in and choose access

   Click Connect. A VEXiON page opens. Sign in, choose the businesses and choose what Claude may do. See Permissions.

4. Turn it on in a chat

   In a conversation, click + at the lower left, choose Connectors and switch VEXiON on.

On Team and Enterprise plans an owner adds the connector first, under Organization settings > Connectors > Add > Custom > Web. Members then open Customize > Connectors and click Connect. Free accounts can add one custom connector.

ChatGPT

ChatGPT connects to remote MCP servers as a custom app. The menu names have changed several times, so follow this outline and OpenAI’s own page for the current labels: Connect a custom MCP server in ChatGPT.

1. Add a custom MCP server

   Open ChatGPT Plugins at chatgpt.com/plugins, click the plus button and choose Add custom MCP server.

2. Enter the details

   Give it a name such as VEXiON. Under Connection, choose the public endpoint and enter https://api.vexioncards.one/mcp. Set authentication to OAuth.

3. Accept the warning

   Read the risk notice, click I understand and want to continue, then click Create as a plugin.

4. Sign in

   ChatGPT opens a VEXiON page. Sign in, choose the businesses and the access level. See Permissions. Start a new chat, type @ and pick the VEXiON app.

On Business, Enterprise and Edu workspaces an admin may have to allow custom MCP servers before you can add one. Whether you can use tools that change data depends on your ChatGPT plan and workspace settings. VEXiON does not control this.

Claude Code

Add the server, then sign in from inside Claude Code.

terminal

claude mcp add --transport http vexion https://api.vexioncards.one/mcp

Start Claude Code and run /mcp, choose vexion and follow the browser steps to sign in and choose access.

To share the server with a team, add --scope project. It is written to .mcp.json in the project, and each person signs in on their own:

terminal

claude mcp add --transport http --scope project vexion https://api.vexioncards.one/mcp

Check the connection with claude mcp list.

Cursor

Add the server to ~/.cursor/mcp.json for all projects, or to .cursor/mcp.json in one project:

mcp.json

{
  "mcpServers": {
    "vexion": {
      "url": "https://api.vexioncards.one/mcp"
    }
  }
}

Cursor lists the server under its MCP settings. When it asks you to sign in, sign in with your VEXiON account and choose the access in the browser.

VS Code

Add the server to .vscode/mcp.json in your workspace, or run MCP: Open User Configuration to add it for every workspace:

.vscode/mcp.json

{
  "servers": {
    "vexion": {
      "type": "http",
      "url": "https://api.vexioncards.one/mcp"
    }
  }
}

Run MCP: List Servers, choose vexion and start it. VS Code opens the VEXiON sign-in. Then open the Chat view in Agent mode and use the tools.

Gemini CLI

Add the server to ~/.gemini/settings.json. Gemini CLI uses httpUrl for Streamable HTTP servers:

settings.json

{
  "mcpServers": {
    "vexion": {
      "httpUrl": "https://api.vexioncards.one/mcp"
    }
  }
}

Start Gemini CLI and run /mcp auth vexion to sign in. OAuth needs a browser on the same machine, so use an API key over SSH or in CI.

Any MCP client

Use the server URL https://api.vexioncards.one/mcp with the Streamable HTTP transport.

The server follows the standard MCP authorization flow. A client that supports it finds the sign-in details on its own: an unauthenticated request returns 401 with a WWW-Authenticate header that points to the protected resource document at https://api.vexioncards.one/.well-known/oauth-protected-resource/mcp.

If your client has no OAuth support, use an API key (below).

​

Connect with an API key

Create a key in Settings > Developer and give it only the scopes the agent needs. See Introduction for who can create keys. Send the key as a bearer token:

Authorization: Bearer vxn_sk_...

Claude Code

terminal

export VEXION_API_KEY=vxn_sk_...
claude mcp add --transport http vexion https://api.vexioncards.one/mcp \
  --header "Authorization: Bearer $VEXION_API_KEY"

For a shared project file, use an environment variable so the key is not committed:

.mcp.json

{
  "mcpServers": {
    "vexion": {
      "type": "http",
      "url": "https://api.vexioncards.one/mcp",
      "headers": {
        "Authorization": "Bearer ${VEXION_API_KEY}"
      }
    }
  }
}

Cursor

mcp.json

{
  "mcpServers": {
    "vexion": {
      "url": "https://api.vexioncards.one/mcp",
      "headers": {
        "Authorization": "Bearer ${env:VEXION_API_KEY}"
      }
    }
  }
}

VS Code

VS Code asks for the key the first time the server starts and stores it for you:

.vscode/mcp.json

{
  "inputs": [
    {
      "type": "promptString",
      "id": "vexion-api-key",
      "description": "VEXiON API key",
      "password": true
    }
  ],
  "servers": {
    "vexion": {
      "type": "http",
      "url": "https://api.vexioncards.one/mcp",
      "headers": {
        "Authorization": "Bearer ${input:vexion-api-key}"
      }
    }
  }
}

Gemini CLI

terminal

gemini mcp add --transport http \
  --header "Authorization: Bearer $VEXION_API_KEY" \
  vexion https://api.vexioncards.one/mcp

Or in ~/.gemini/settings.json:

settings.json

{
  "mcpServers": {
    "vexion": {
      "httpUrl": "https://api.vexioncards.one/mcp",
      "headers": {
        "Authorization": "Bearer your-api-key"
      }
    }
  }
}

Prefer the gemini mcp add command with an environment variable over writing the key into the file.

An API key reaches the business it belongs to. The tools the agent sees follow the key’s scopes: a key without notifications:send never shows the notification tools. See the tool list for the scope each tool needs.

​

Check that it works

Ask the assistant: “Give me an overview of my VEXiON account.” It should answer with your business name, plan, locations and cards. If it does not, see MCP server errors.

​

Example prompts

You do not need to name a tool. Describe what you want and the assistant picks the right ones. What it can do depends on the access you granted.

You say	What happens
”Give me an overview of my VEXiON account.”	Reads your business, locations and cards. A good first message.
”How many new customers did we get each week in September, and how many installed the card?”	Runs a sign-up report and returns counts by week.
”Compare transactions this month to last month at the Main Street location.”	Runs a transaction report for both ranges and compares the totals.
”Find the customer with email [e-mail] and tell me how many stamps she has.”	Looks up the customer and reads the card balance and recent transactions.
”Anna just bought a coffee. Add one stamp to her card.”	Records a transaction for her. Needs write access.
”Create a stamp card for my cafe: 8 stamps, free coffee on the ninth, brown design.”	Drafts the card, shows you the design and creates it after you agree. Needs write access.
”Send a notification to everyone with the coffee card: ‘Double stamps this Friday!’”	Shows a preview of the text and the audience filters, then sends only after you confirm. Needs notification access.
”Email Tomas his card link so he can add it to his wallet.”	Shows a preview, then emails the link after you confirm. Needs write access.

Name the card, location or date range when you can. “Transactions at the Old Town location last week” gives a more exact answer than “recent transactions”.

​

Where to read next

Permissions and security

The access levels, what an assistant can never do, and how to revoke an app.

Tools

All 31 tools, the confirmation steps and the notification and report limits.

MCP server errors

Sign-in errors, missing tools and what to do about them.

Rate limits

Request and notification limits for the MCP server.

Not a developer? The Knowledge Base has a plain-language guide for business owners: AI assistants (MCP).

Looking for the REST API instead? Start with the Quickstart. The MCP server uses the same data and the same rules as the REST API, so a key, a plan or an account state that is refused there is refused here too.