Compatible with every major AI agent and IDE
What is the Stigg MCP Server?
Connect your Stigg account to any AI agent to take full control of your pricing and packaging workflows. Manage the entire customer lifecycle from provisioning to usage reporting through natural conversation.
What you can do
- Customer Lifecycle — Create, update, and retrieve customer profiles using REST or GraphQL tools.
- Subscription Management — Provision new subscriptions, fetch active plan details, or cancel them when needed.
- Usage Reporting — Report metered feature usage in real-time to ensure accurate billing and entitlement enforcement.
- Hybrid API Access — Choose between REST and GraphQL actions for flexible integration with your billing data.
How it works
- Subscribe to this server
- Enter your Stigg API Key
- Start managing your SaaS billing from Claude, Cursor, or any MCP-compatible client
No more jumping between dashboards to check a customer's entitlement or manually reporting usage. Your AI acts as a billing operations assistant.
Who is this for?
- Product Managers — instantly check customer plan statuses and feature entitlements without opening the Stigg console.
- Customer Success — provision trials or update customer details directly during support interactions.
- Developers — test billing flows and report usage for metered features straight from the terminal or IDE.
Built-in capabilities (12)
Get customer details via GraphQL
Get entitlements state via GraphQL
Provision a customer and optional subscription via GraphQL
Provision a subscription via GraphQL
Report usage via GraphQL
Cancel a subscription via REST API
Create a new customer via REST API
Create a subscription via REST API
Retrieve a customer via REST API
Retrieve a subscription via REST API
Report usage for metered features via REST API
Update a customer via REST API
Why Claude Desktop?
Claude Desktop is the definitive way to connect Stigg to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Stigg in Claude Desktop
Stigg and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Stigg to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Stigg in Claude Desktop
The Stigg MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Stigg for Claude Desktop
Every tool call from Claude Desktop to the Stigg MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I provision a customer and a subscription in one go?
Yes! Use the gql_provision_customer tool. It allows you to create the customer entity and optionally provide a planId to start their subscription immediately in a single GraphQL call.
How do I report usage for a metered feature?
You can use either rest_report_usage or gql_report_usage. Simply provide the customerId, the featureId, and the numeric value to update their metered usage in Stigg.
Is it possible to cancel an active subscription via the agent?
Yes, use the rest_cancel_subscription tool by providing the specific subscription ID. The agent will process the cancellation through Stigg's REST API.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Flickr
12 toolsBrowse, search, and manage photo collections on Flickr with access to one of the largest creative photography communities online.

Strapi
9 toolsConnect your AI to Strapi. Fully orchestrate your headless CMS — create entries, manage content types, and upload media assets naturally.

Mux
11 toolsManage video assets and live streams via Mux — create assets and track performance directly from your AI agent.

Directus
16 toolsTurn any SQL database into a powerful headless CMS with instant REST and GraphQL APIs for your custom content models.
