Model Context Protocol (MCP)

The Vignetim Partner API provides a full Model Context Protocol (MCP) server, enabling your AI assistant to directly interact with the API — browse products, create orders, manage webhooks, and search documentation — all without leaving your IDE.

What is MCP?

MCP is an open protocol that standardizes how AI applications connect to external tools and data sources. With Vignetim's MCP server, your AI coding assistant becomes a Vignetim API client.

Capabilities

Category	Tools	Auth Required
Products	`list_tickets`, `get_ticket`, `list_esim_packages`, `list_insurance_products`, `get_insurance_product`, `list_vehicle_categories`, `list_vehicle_categories_by_type`, `list_geo_checkpoints`	Yes
Orders	`create_order`, `list_orders`, `get_order`, `get_order_documents`, `get_order_status`	Yes
Webhooks	`create_webhook`, `list_webhooks`, `update_webhook`, `delete_webhook`, `test_webhook`	Yes
Wallet	`get_wallet_balance`	Yes
Documentation	`list_docs`, `get_doc`, `search_docs`, `get_openapi_spec`	No

MCP Endpoint

text

https://vignetim.com/api/mcp

Authentication

API operation tools require your Partner API credentials via HTTP headers:

Header	Description
`X-API-Key`	Your organization API key
`X-API-Secret`	Your organization API secret
`X-Environment`	Optional. `production` (default) or `staging` — see below

Sandbox vs live mode is determined by the API key itself: vgn_test_ keys run in sandbox mode with simulated payments, vgn_live_ keys run against live data.

Which deployment the call reaches is a separate thing. API keys live in the database of the deployment that issued them, so a key created in the staging dashboard only authenticates against the staging API. Send X-Environment: staging for those keys:

bash

claude mcp add vignetim-staging --transport http https://vignetim.com/api/mcp \
  --header "X-API-Key: YOUR_STAGING_KEY" \
  --header "X-API-Secret: YOUR_STAGING_SECRET" \
  --header "X-Environment: staging"

A staging.vignetim.com/api/mcp endpoint also exists and serves the same tools; the header works from either host, so there is no need to switch hosts. Omitting the header with a staging-issued key returns 401 Authentication failed, because the call is made against production.

Documentation tools (list_docs, get_doc, search_docs, get_openapi_spec) work without authentication.

How It Works

Your AI assistant connects to https://vignetim.com/api/mcp
It discovers available tools (products, orders, webhooks, docs)
When you ask "list Austrian vignettes", the assistant calls list_tickets with countryIsocode: "AT"
The MCP server signs the request with HMAC-SHA256 and proxies it to the Partner API
Results are returned directly to your assistant

The MCP server handles all authentication complexity — HMAC signing, timestamps, nonces — so your AI agent just calls tools with simple parameters.

Platform Support

Platform	Transport	Setup Guide
Claude Code	Streamable HTTP	Vignetim Claude MCP →
Claude Desktop	Streamable HTTP	Vignetim Claude MCP →
Cursor	Streamable HTTP	Vignetim OpenAI MCP →
Windsurf	Streamable HTTP	Vignetim OpenAI MCP →
OpenAI Agents SDK	Streamable HTTP	Vignetim OpenAI MCP →
Continue	Streamable HTTP	Vignetim OpenAI MCP →

Additional Resources

OpenAPI Spec: https://vignetim.com/api/partner-openapi
LLMs.txt: https://vignetim.com/llms.txt
AI Plugin: https://vignetim.com/.well-known/ai-plugin.json