CursorIDE

Stigg MCP Server

Bring Billing
to Cursor

Name: Stigg MCP Server
Price: 29 USD
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

Learn how to connect Stigg to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Gql Get CustomerGql Get Entitlements StateGql Provision CustomerGql Provision SubscriptionGql Report UsageRest Cancel SubscriptionRest Create CustomerRest Create SubscriptionRest Get CustomerRest Get SubscriptionRest Report UsageRest Update Customer

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

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)

gql_get_customer

Get customer details via GraphQL

gql_get_entitlements_state

Get entitlements state via GraphQL

gql_provision_customer

Provision a customer and optional subscription via GraphQL

gql_provision_subscription

Provision a subscription via GraphQL

gql_report_usage

Report usage via GraphQL

rest_cancel_subscription

Cancel a subscription via REST API

rest_create_customer

Create a new customer via REST API

rest_create_subscription

Create a subscription via REST API

rest_get_customer

Retrieve a customer via REST API

rest_get_subscription

Retrieve a subscription via REST API

rest_report_usage

Report usage for metered features via REST API

rest_update_customer

Update a customer via REST API

Why Cursor?

Cursor's Agent mode turns Stigg into an in-editor superpower. Ask Cursor to generate code using live data from Stigg and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

—
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
—
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
—
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
—
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

See it in action

Stigg in Cursor

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

Stigg and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Stigg to Cursor 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.

4,000+MCP Servers ready

<40msCold start

60%Token savings

	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

Unlock for AI Agents View step-by-step setup guide for Cursor →

Enterprise Security

Why teams choose Vinkius for Stigg in Cursor

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 Cursor 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.

Unlock for AI Agents View full Stigg details →

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures
Stigg for Cursor

Every tool call from Cursor to the Stigg MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start

Ed25519Signed audit chain

60%Token savings

FAQ

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.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.