Stigg MCP. Manage billing, usage, and subscriptions via conversation.
Stigg brings billing and subscription management directly into your AI workflow. Use this MCP to provision new customers, manage active plans, or report usage metrics without leaving your client. You can handle the entire customer lifecycle—from initial account creation using rest_create_customer to tracking metered feature usage via gql_report_usage—all through natural conversation.
Give Claude and any AI agent real-world access
Create new accounts or fetch existing customer details using both REST and GraphQL endpoints.
Set up a new subscription for a customer or retrieve the current state of their active plans.
Cancel an existing subscription or update basic customer information when necessary.
Report metered feature usage to ensure billing accuracy and enforce entitlements in real time.
Ask an AI about this
Waiting for input…
What AI agents can do with Stigg: 12 Tools for Billing Operations
These tools allow you to execute every core function of customer management, subscription control, and usage reporting via the Stigg API.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Stigg MCPRest Cancel Subscription
Cancels a customer's subscription account using the REST API.
Rest Create Customer
Creates an entirely new customer profile using the REST API.
Rest Create Subscription
Sets up a brand new subscription for a customer via the REST API.
Rest Get Customer
Retrieves all available details about an existing customer profile using the REST...
Rest Get Subscription
Fetches all specific information regarding a given subscription plan via the REST...
Gql Get Customer
Retrieves customer details using the flexible GraphQL query language.
Gql Get Entitlements State
Checks the current state of a user's feature entitlements via GraphQL.
Gql Provision Customer
Creates and optionally provisions a subscription for a customer using GraphQL.
Gql Provision Subscription
Sets up a new subscription plan directly via the GraphQL endpoint.
Gql Report Usage
Reports metered feature usage data using the structured GraphQL query language.
Rest Report Usage
Records metered usage for billing purposes through a dedicated REST API call.
Rest Update Customer
Modifies existing details for a customer using the REST API.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Stigg, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Stigg. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The Pain of Switching Contexts to Check Billing Status
Right now, checking a customer's status means opening your billing dashboard. You pull up their profile, click into 'Subscriptions' to see the plan, and then maybe jump over to a usage tab just to check if they hit their limit. It takes five clicks, three tabs, and you risk losing track of which data point came from where.
With this MCP, those steps vanish. You simply tell your agent what you need—'What is the current plan and usage for cust-123?' The entire operation runs in the background, giving you a clean, direct answer without ever leaving your chat window.
Stigg: Instant Billing Control
Gone are the days of copying and pasting customer IDs between different systems. Gone is the manual process of confirming if a new subscription was created correctly or if usage reports were properly sent.
You manage everything—from rest_create_customer to gql_report_usage—through natural conversation. It makes billing operations feel like talking to an expert coworker, not wrestling with a dozen dashboards.
What Stigg MCP does for your AI
Stop switching between billing dashboards just to check a customer's status or adjust their plan. This connector lets you take full control of your entire pricing and packaging workflow, right from any MCP-compatible client. You can handle the whole customer journey, whether it’s creating a new account, updating details, provisioning a subscription, or canceling service when needed.
Need to know how much usage a user has consumed? Just ask your agent to report the metered feature usage in real time for accurate billing. Because this MCP is hosted on Vinkius, you get access to these core operations—like customer profile retrieval and plan management—all from one place. Your AI acts like an instant, hands-on billing ops assistant that never gets tired of API calls.
019e38f4-4e9c-7083-9e6e-c575c09eba5d How to set up Stigg MCP
The bottom line is that your AI client turns complex billing API calls into simple, conversational instructions.
First, subscribe to this MCP on Vinkius and input your Stigg API Key.
Next, tell your AI client exactly what you need—for example, 'Get the details for customer X' or 'Report usage of feature Y'.
The agent uses the appropriate tool (like gql_get_customer or rest_report_usage) to perform the action and gives you a direct answer.
Who uses Stigg MCP
Product Managers who need instant status checks; Customer Success reps needing to provision trials mid-call; and Developers who want to test complex billing flows right from their IDE without leaving the terminal.
Uses this MCP to quickly provision trial subscriptions or update customer details during a support call, eliminating manual dashboard navigation.
Checks current feature entitlements and plan statuses for various users instantly, verifying if a feature is accessible before writing product documentation.
Tests billing logic by reporting usage metrics or creating test customers directly from the terminal while building new features.
Benefits of connecting Stigg MCP
Avoid dashboard hopping: Instead of jumping between the Stigg console to check a customer's plan status or feature entitlements, you just ask your agent. It gives you the data instantly.
Process complex lifecycle changes quickly: Need to create an account and immediately set up their first paid subscription? Use gql_provision_customer or rest_create_subscription in one go with simple instructions.
Maintain billing accuracy: Don't rely on manual reporting for usage. Tell your agent to report the metered feature usage (like using gql_report_usage) so billing is always accurate and up-to-date.
Flexible integration options: Whether you prefer calling out updates via rest_update_customer or fetching data through GraphQL, this MCP handles both REST and GraphQL actions for maximum flexibility.
Centralized control: You can manage the entire customer journey—from initial provisioning to final cancellation using rest_cancel_subscription—without ever leaving your primary development environment or chat tool.
Stigg MCP use cases
Onboarding a new enterprise client
A Customer Success rep asks their agent: 'Create customer ID cust-456 and provision them the Enterprise plan.' The agent executes gql_provision_customer, ensuring both the account and the subscription are live immediately.
Verifying usage limits during a sprint
A Developer runs into an apparent billing issue. They prompt their agent to 'Report 150 units of usage for feature X.' The agent uses rest_report_usage, providing immediate confirmation and allowing the dev to confirm if the limit was hit.
Auditing a customer's plan status
A Product Manager needs to know what features 'cust-123' has access to. They ask their agent to use gql_get_entitlements_state, getting instant confirmation without opening the billing console.
Handling service termination
Support receives a cancellation request. The rep directs the agent to 'Cancel subscription for cust-123.' The agent uses rest_cancel_subscription and confirms the status change, logging the action immediately.
Stigg MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Using multiple tools sequentially
The user manually runs 'rest_get_customer' to get an ID, then copies that ID and pastes it into a separate prompt for 'gql_get_entitlements_state', wasting time.
Ask your agent in one go: 'Get the customer details AND their entitlements state for cust-123.' The agent handles both calls automatically.
Forgetting to specify the API style
The user is unsure if they should use REST or GraphQL, leading to multiple failed attempts and confusion about which data source is correct.
Just tell your agent: 'I need the customer details.' The agent will know how to select the right function (like gql_get_customer or rest_get_customer) based on context.
Attempting provisioning without an ID
The user tries to run 'gql_provision_subscription' without first giving the agent a customer ID, causing the process to fail immediately.
Always start by ensuring the account exists. First, use rest_create_customer or gql_get_customer. Then follow up with 'Now provision a subscription for them.' This ensures data integrity.
When to use Stigg MCP
Use this MCP if your primary pain point involves coordinating multiple billing actions: creating accounts, changing plans, tracking usage, and retrieving customer status. It's the central hub for SaaS finance operations.
Don't use it if you only need to read simple data that doesn't relate to billing (e.g., reading a user's name from an internal CRM). For those cases, look for a dedicated integration tool. Also, don't use this MCP just because you have trouble with one API type; since it supports both REST and GraphQL actions, it handles the technical choice for you.
Frequently asked questions about Stigg MCP
How do I create a customer using the Stigg MCP? +
You use rest_create_customer or gql_provision_customer. You just need to tell your agent the necessary details, like name and email, and specify which endpoint you want to use.
Is reporting usage difficult with Stigg? +
No. You simply ask your agent to report the metered feature usage by using gql_report_usage or rest_report_usage, providing only the units and the feature name.
Can I retrieve customer details in multiple ways with Stigg? +
Yes. You can use both GraphQL (gql_get_customer) for flexible querying, or REST (rest_get_customer) if you prefer direct resource retrieval via API calls.
What happens when I try to cancel a subscription? +
The agent executes rest_cancel_subscription. It confirms the cancellation and updates the customer's status immediately, making it visible in your chat history.
Does Stigg handle complex provisioning? +
It does. You can use gql_provision_customer to provision both a new customer account and an associated subscription plan simultaneously.