Bring Loyalty Programs
to Cursor
Learn how to connect Swarm to Cursor and start using 5 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Swarm MCP Server?
Connect your Swarm loyalty account to any AI agent and simplify how you manage customer rewards, award points for transactions, and handle redemptions through natural conversation.
What you can do
- Point Management — Retrieve real-time point balances and loyalty tiers for specific customer IDs.
- Transaction Processing — Programmatically award points to customers by registering sale amounts and product data via AI.
- Reward Redemption — Convert customer points into discount vouchers or specific rewards and list all active vouchers.
- Catalog Discovery — Browse available rewards and check eligibility for specific customers instantly.
- Voucher Oversight — List and query all unused discount codes currently assigned to a customer's profile.
- Loyalty Lifecycle — Manage the entire customer reward journey directly from Claude, Cursor, or any MCP client.
How it works
1. Subscribe to this server
2. Enter your Swarm API Key (found in your account dashboard)
3. Start managing your loyalty program from your favorite AI assistant
Who is this for?
- Retail Business Owners — quickly check customer points and award rewards during checkout via simple AI commands.
- Marketing Managers — monitor reward distribution and verify voucher availability directly from the workspace.
- Customer Success Teams — assist customers with point inquiries and handle manual redemptions via the AI assistant.
Built-in capabilities (5)
Check customer loyalty points
List redeemable rewards
List active customer vouchers
Process a sale and award points
Redeem points for a reward
Why Cursor?
Cursor's Agent mode turns Swarm into an in-editor superpower. Ask Cursor to generate code using live data from Swarm and it fetches, processes, and writes. all in a single agentic loop. 5 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
Swarm in Cursor
Swarm and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Swarm 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ 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 Swarm in Cursor
The Swarm 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 5 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.
* 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
Swarm for Cursor
Every tool call from Cursor to the Swarm MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I check a customer's points balance via AI?
Yes! Use the get_customer_balance tool and provide the Customer ID. Your agent will retrieve the current points and the loyalty tier for that specific user.
How do I award points for a recent purchase using the agent?
Use the process_loyalty_transaction action. Provide the Customer ID and the transaction amount. The agent will instantly calculate and award the correct points based on your Swarm settings.
Is it possible to list all the rewards a customer can claim?
Absolutely. Use the list_available_rewards query and provide the Customer ID. The agent will return the catalog of rewards that the user is currently eligible to redeem.
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.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.