Using API v1? See what changes in v2, or the v1 docs

Cursor

Add Pyas to Cursor, and its agent can set up your Pyas app, write the code that connects calendars, and check your sandbox while you code. You add Pyas by its address and sign in. There is nothing to install and no key to copy.

Start with the sandbox address, https://mcp.pyas.io/sandbox. It works in your app's sandbox, on sample people, calendars and events, so nothing you try reaches a real calendar.

Add Pyas to Cursor

Select Add to Cursor. Cursor opens and asks you to install pyas-sandbox.

Or add it yourself:

  1. Add the server to ~/.cursor/mcp.json to use it in every project, or to .cursor/mcp.json in one project:
    {
  "mcpServers": {
    "pyas-sandbox": { "url": "https://mcp.pyas.io/sandbox" }
  }
}
  2. Save the file and restart Cursor.

To see the server, open Customize in the sidebar, then MCPs.

Sign in

The first time Cursor connects to Pyas, your browser opens the Pyas dashboard:

  1. Sign in, or create an account.
  2. Choose the app that Cursor works with.
  3. Check what Cursor asks for, and select Allow.

Go back to Cursor. Under Customize, then MCPs, pyas-sandbox lists its tools. See Sign in for what each permission allows.

Use it while you code

Ask the agent in plain words, in the project you're working on:

Set up Pyas in this app so people can connect their Google or Outlook calendar.

The agent checks your app's setup with setup_status, gets the code for your stack with get_recipe, and creates a test key with get_test_key. It tells you where to store the key, such as PYAS_API_KEY in your .env file. Recipes cover Next.js and Express, and the AI app builders.

What's on Avery's calendar tomorrow?

My last request to Pyas failed. Why?

The sandbox's sample people, such as Avery Brooks and Riley Chen, have calendars with a week of events. For a failed request, the agent looks it up with get_request and explain_error, from its trace ID.

To leave out a tool, select its name in the tools list at the top of the chat panel.

Every request Cursor makes is on the Logs page in the dashboard, marked with the tool that made it.

Choose what needs your approval

Cursor asks you before it uses a Pyas tool. To let it use every Pyas tool in the sandbox without asking, add the server to the allowlist in ~/.cursor/permissions.json:

{
  "mcpAllowlist": ["pyas-sandbox:*"]
}

Don't add the live server to the allowlist. Keep being asked before the agent changes a live calendar.

Live calendars

To work on the real calendars that people connected to your app, add a second server next to the sandbox:

{
  "mcpServers": {
    "pyas-sandbox": { "url": "https://mcp.pyas.io/sandbox" },
    "pyas-live": { "url": "https://mcp.pyas.io" }
  }
}

When you sign in, choose whether Cursor may only read live calendars, or change them too.

Before the agent changes a live calendar, you confirm the change in Pyas, from a link that it gives you. See Live calendars for how that works and who can confirm.

While you work in the sandbox, turn the live server off with the switch next to pyas-live, under Customize, then MCPs.

Disconnect

To remove Pyas from Cursor, remove it under Customize, then MCPs, or delete its entry from mcp.json.

To stop Cursor from Pyas's side, open your profile in the Pyas dashboard. Connected tools lists Cursor with when it was last used, and Disconnect stops it immediately. To use it again, add it again and sign in.