Skip to content
Talk to sales Start building
Vouchery logo

Vouchery MCP server

Vouchery is a voucher and gift card management platform.

Vouchery is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Start building See the Vouchery integration
Tools
4
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
September 2026

About the Vouchery MCP server

Connect Vouchery once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Vouchery and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Vouchery tools your AI can run

Once connected, your assistant can call any of these Vouchery actions by asking in plain language.

  • Create a voucher

    Create a new voucher in a campaign

    6 fields

  • Create Customer

    Create a new customer

    8 fields

  • Find Voucher

    Find a voucher by campaign metadata. At least one metadata must be provided

    5 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Give your assistant Vouchery

Connect Vouchery once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Get your server URLTalk to sales

Vouchery MCP, answered.

No. That is the point of it. One Activepieces server exposes Vouchery alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Vouchery in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 4 tools, including Create a voucher, Create Customer, Find Voucher, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.