Vignetim Claude MCP

Connect the Vignetim Partner API directly to Claude Code or Claude Desktop. Your assistant will be able to browse products, create orders, manage webhooks, and search documentation.

Quick Setup

Claude Code (CLI)

bash

claude mcp add vignetim --transport http https://vignetim.com/api/mcp \
  --header "X-API-Key: YOUR_API_KEY" \
  --header "X-API-Secret: YOUR_API_SECRET"

For sandbox testing, use a sandbox API key (prefixed vgn_test_) — no extra header is needed:

bash

claude mcp add vignetim-sandbox --transport http https://vignetim.com/api/mcp \
  --header "X-API-Key: YOUR_SANDBOX_KEY" \
  --header "X-API-Secret: YOUR_SANDBOX_SECRET"

Claude Desktop

Add to your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

json

{
	"mcpServers": {
		"vignetim": {
			"url": "https://vignetim.com/api/mcp",
			"headers": {
				"X-API-Key": "YOUR_API_KEY",
				"X-API-Secret": "YOUR_API_SECRET"
			}
		}
	}
}

Restart Claude Desktop after saving.

Available Tools

Products

Tool	Description	Example
`list_tickets`	Browse vignette tickets	"Show me Austrian vignettes for cars"
`get_ticket`	Get ticket details	"Get details for ticket abc-123"
`list_esim_packages`	Browse eSIM packages	"What eSIM packages are available for Turkey?"
`list_insurance_products`	Browse insurance	"List all insurance products"
`get_insurance_product`	Get insurance details	"Tell me about green card insurance"
`list_vehicle_categories`	Browse vehicle types	"What vehicle categories exist?"

Orders

Tool	Description	Example
`create_order`	Create an order	"Create a vignette order for Austria"
`list_orders`	List your orders	"Show my recent orders"
`get_order`	Get order details	"What's the status of order xyz?"
`get_order_status`	Check order status	"Is order xyz completed?"

Webhooks

Tool	Description	Example
`create_webhook`	Register endpoint	"Set up a webhook for order.completed events"
`list_webhooks`	List webhooks	"Show my registered webhooks"
`update_webhook`	Update webhook	"Disable webhook abc"
`delete_webhook`	Delete webhook	"Remove webhook abc"
`test_webhook`	Send test event	"Send a test event to webhook abc"

Wallet

Tool	Description	Example
`get_wallet_balance`	Get your wallet balance	"What's my EUR balance?"

Documentation

Tool	Description	Example
`list_docs`	Browse docs	"What API docs are available?"
`get_doc`	Read a section	"Show me the authentication docs"
`search_docs`	Search docs	"How do I handle errors?"
`get_openapi_spec`	Get OpenAPI spec URL	"Where's the OpenAPI spec?"

Usage Examples

Browsing Products

text

You: What vignettes are available for Hungary?

Claude: [calls list_tickets with countryIsocode: "HU"]
        Found 12 vignette options for Hungary:
        - 10-day highway vignette (Category D1) — €14.90
        - Monthly highway vignette (Category D1) — €19.90
        ...

Managing Webhooks

text

You: Set up a webhook at https://myapp.com/webhooks/vignetim
     for order completed and failed events.

Claude: [calls create_webhook with url, events]
        Webhook registered successfully!
        ID: 7f3a...
        Signing Secret: abc123...  (save this — it's only shown once)

Checking Order Status

text

You: Show me all failed orders from this week.

Claude: [calls list_orders with status filter and date range]
        Found 2 failed orders:
        1. Order #abc - Failed at 2026-03-18 (vignette, AT)
        2. Order #def - Failed at 2026-03-19 (eSIM, global)

Team Configuration

Add to your project's .mcp.json for team-wide access.

Do not commit your API secret. .mcp.json usually lives in version control, so a literal secret there ends up in your git history and in every clone. Reference environment variables instead — "X-API-Secret": "${VIGNETIM_API_SECRET}" — and keep the values in each developer's shell or secret manager. If a secret has already been committed, rotate the key in the Partner Dashboard; removing the line does not undo the exposure.

json

{
	"mcpServers": {
		"vignetim": {
			"url": "https://vignetim.com/api/mcp",
			"headers": {
				"X-API-Key": "YOUR_API_KEY",
				"X-API-Secret": "YOUR_API_SECRET"
			}
		}
	}
}

Troubleshooting

"API credentials required"

This error appears when using API tools without credentials. Ensure both X-API-Key and X-API-Secret headers are configured.

"Authentication failed"

Verify your API key and secret are correct
Check that your key is active in the Vignetim Partner Dashboard
If IP restrictions are enabled for your key, disable them for MCP usage — requests reach the API from the Vignetim MCP server, not from your own IP, so an IP allowlist will block them

Sandbox vs Production

The environment is determined by your API key: keys prefixed vgn_test_ run in sandbox mode with simulated payments and test data, while vgn_live_ keys run against production. No extra header is required.