Skip to main content
The NeetoCal MCP server lets your AI assistant manage scheduling from plain-language requests. Ask it to list bookings, check availability, create a scheduling link, or reschedule a meeting, and it works with your NeetoCal workspace for you. MCP (Model Context Protocol) is an open standard that connects AI assistants to tools such as NeetoCal. You describe the task; the assistant uses the right tool.

​
What you can do

Manage bookings

List, reschedule, approve, cancel, and record payments on bookings.

Check availability

Look up open slots and team availability before booking.

Create links

Create meetings, one-off links, and reusable templates.

Hand off the busywork

Ask your assistant to find a free slot, book a client, or fix a conflict for you.

​
MCP vs CLI: which should I use?

NeetoCal’s CLI reaches the same resources MCP does - meetings, bookings, availabilities, team members, and the rest. Neither one can do more than the other, so choose on how the work reaches NeetoCal.

​
Reach for MCP when

  • The details live in your chat, not in your head. An email, a thread, or a pasted note turns into the booking with no retyping. The CLI cannot see any of it.
  • You have not decided the steps yet. “Someone double-booked me on Thursday - sort it out” means looking at what is there and choosing. A command can only carry out a decision you have already made.
  • One request should cover several steps. Check availability, pick a slot, book it, and record the reason, with no glue between commands.
  • The person doing it does not use a terminal. NeetoCal hosts the server, so there is nothing to install or keep updated.

​
Reach for the CLI instead when

  • No AI assistant should be in the loop. A cron entry or a CI step runs the CLI with nothing but the binary and a workspace it is already signed in to - no assistant open, no model account, no tokens spent per run. Every MCP call needs something with model access running.
  • The output feeds another program. The CLI prints a bare identifier or raw JSON for jq, a spreadsheet, or your own script. Here you get prose you would have to copy out by hand.
  • You are working through thousands of records. Here every page is a separate tool call, and a list that long crowds out the assistant’s context. The CLI returns total_pages next to the records, so a shell loop walks every page unattended and writes each one to a file or into jq - the size of the list stops mattering.
  • The run has to be repeatable and reviewable. A command is the artifact: it records exactly what ran and repeats identically. Ask twice here and the assistant may take a different route.
You can have both. Run neetocal setup claude and the same assistant drives the CLI for you, so a plain-language request still ends in an exact command you can read, repeat, and paste into a script.
Ask your assistant to show you what it plans to do before it books, moves, or cancels anything. These tools act on your live workspace.

​
What you need

  1. A supported AI assistant - Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, or Antigravity.
  2. A NeetoCal API key - learn how to generate one.
The MCP server authenticates with the same API key the REST API uses. Unlike the CLI, which signs in through your browser, MCP passes the key as a bearer token from your assistant’s config.
Connect your assistant to get started.