NeetoCal MCP Server for CursorGive Cursor instant access to 12 tools to Cancel Booking, Check Neetocal Status, Create Booking, 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 NeetoCal app connector for Cursor is a standout in the Industry Titans 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 NeetoCal and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"neetocal": {
"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 NeetoCal MCP Server
Connect your NeetoCal account to any AI agent and take full control of your scheduling orchestration and appointment management through natural conversation. NeetoCal provides a robust platform for managing bookings and team availability, and this integration allows you to retrieve booking metadata, monitor team schedules, and manage public scheduling links directly from your chat interface.
Cursor's Agent mode turns NeetoCal into an in-editor superpower. Ask Cursor to generate code using live data from NeetoCal 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
- Booking & Appointment Orchestration — List all scheduled meetings and create new bookings programmatically to ensure your calendar is always synchronized.
- Availability & Schedule Intelligence — Access and monitor team member availabilities directly from the AI interface to track team throughput and identify open slots.
- Link & Page Control — List and retrieve all active scheduling links via natural language to facilitate frictionless meeting coordination.
- Participant Management — Access granular details for specific bookings to understand attendee requirements and meeting context using simple AI commands.
- Operational Monitoring — Track system responses and manage workspace metadata to ensure your scheduling pipelines are always optimized.
The NeetoCal 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 NeetoCal tools available for Cursor
When Cursor connects to NeetoCal through Vinkius, your AI agent gets direct access to every tool listed below — spanning appointment-booking, scheduling, team-availability, 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.
Cancel a booking
Verify connectivity
Create a booking
Get availability
Get booking details
Get scheduling link
Get available slots
List availabilities
List bookings
List calendars
List scheduling links
Reschedule a booking
Connect NeetoCal to Cursor via MCP
Follow these steps to wire NeetoCal 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 NeetoCal
Why Use Cursor with the NeetoCal MCP Server
Cursor AI Code Editor provides unique advantages when paired with NeetoCal 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
NeetoCal + Cursor Use Cases
Practical scenarios where Cursor combined with the NeetoCal 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 NeetoCal in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with NeetoCal immediately.
"List all active bookings in NeetoCal."
"Show me the available time slots for my 30-min Discovery Call link next Monday."
"Cancel the booking with ID bk_293847 and notify the attendee."
Troubleshooting NeetoCal MCP Server with Cursor
Common issues when connecting NeetoCal to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
NeetoCal + Cursor FAQ
Common questions about integrating NeetoCal 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.