ClubPlanner MCP Server for CursorGive Cursor instant access to 12 tools to Create Appointment, Create Checkin, Create Prospect, and more
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this App Connector for Cursor
The ClubPlanner app connector for Cursor is a standout in the Productivity category — giving your AI agent 12 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install ClubPlanner and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"clubplanner": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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
About ClubPlanner MCP Server
Connect your ClubPlanner fitness management account to any AI agent and simplify how you coordinate your gym, manage member relationships, and track facility usage through natural conversation.
Cursor's Agent mode turns ClubPlanner into an in-editor superpower. Ask Cursor to generate code using live data from ClubPlanner 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.
What you can do
- Member & Prospect Management — List active members, track new leads (prospects), and retrieve detailed profile metadata and status.
- Access Control & Check-ins — Monitor real-time entry history and record new member check-ins at specific locations.
- Appointment Scheduling — List and create appointments for personal training, sales tours, or consultations directly via AI.
- Contract Oversight — Query active membership agreements and contracts to monitor renewals and billing cycles.
- Product Catalog — Browse available membership types and club products to assist with sales inquiries.
- Staff Directory — List registered employees and staff members to coordinate facility operations.
- Operational Monitoring — Check your club account metadata and verify API connectivity in real-time.
The ClubPlanner MCP Server exposes 12 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 12 ClubPlanner tools available for Cursor
When Cursor connects to ClubPlanner through Vinkius, your AI agent gets direct access to every tool listed below — spanning member-management, class-booking, facility-management, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
Schedule a new appointment
Record a new member check-in
Add a new prospect to ClubPlanner
Get club account information
Get details for a specific member
List scheduled appointments
List recent member check-ins
List active membership contracts
List all club members
List available products/memberships
List potential members (prospects) in ClubPlanner
List club staff members
Connect ClubPlanner to Cursor via MCP
Follow these steps to wire ClubPlanner into Cursor. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using ClubPlanner
Why Use Cursor with the ClubPlanner MCP Server
Cursor AI Code Editor provides unique advantages when paired with ClubPlanner through the Model Context Protocol.
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
ClubPlanner + Cursor Use Cases
Practical scenarios where Cursor combined with the ClubPlanner MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for ClubPlanner in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with ClubPlanner immediately.
"List all active members in my ClubPlanner account."
"Record a check-in for member 'mem_10293' at the main facility."
"Show me the appointments scheduled for tomorrow."
Troubleshooting ClubPlanner MCP Server with Cursor
Common issues when connecting ClubPlanner to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
ClubPlanner + Cursor FAQ
Common questions about integrating ClubPlanner MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
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.