
Pyas
Calendar API for Google, Outlook and Zoom, no OAuth review
4 followers
Calendar API for Google, Outlook and Zoom, no OAuth review
4 followers
Pyas allows you to effortlessly integrate with Google Calendar and Microsoft Outlook. You can also easily add conferencing to calendar events with Zoom and Google Meet, all using a single API.
This is the 2nd launch from Pyas. View more

Pyas
Launching today
One API for Google Calendar, Outlook and Zoom. Pyas v2 gives Claude, Cursor or your own agent your users' calendars. Add the hosted MCP server by its URL and sign in, or use the same tools with the Vercel AI SDK, LangChain, OpenAI or Anthropic. Agents find meeting times, create events with Meet, Teams or Zoom links and answer invitations. Google, Microsoft and Zoom have already verified Pyas's sign-in, so you skip the OAuth review. Pyas runs no AI models.




Free Options
Launch Team

AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted

Hi Product Hunt,
Pyas launched here as a calendar API for Google, Outlook and Zoom, and it has been running in production since 2023. Everything those years taught us about keeping real calendars in sync went into v2. It's out today, and the biggest change is that your agent can use it directly.
Add https://mcp.pyas.io/sandbox to Claude, Cursor or VS Code and sign in. No key to paste. Then ask "find 30 minutes with Sam next week and send him an invite with a with a Meet link". The agent calls find_meeting_times, then create_event, on sample calendars in your app's sandbox. When you want real calendars, add https://mcp.pyas.io as well.
There are three ways to use it:
Assistants. Claude, Cursor, VS Code or any MCP host can read and change events, find free time, answer invitations and add meeting links.
Coding agents building on Pyas. The API reference, error codes and your request logs are tools, so "why did my last request fail?" gets an answer from the actual trace.
The agent inside your product. @pyas/ai-tools gives you the same tools for the Vercel AI SDK, LangChain, OpenAI or Anthropic, so your agent can schedule for your users.
Calendars hold real people's days, so the server is careful:
Every tool says whether it reads, changes or deletes, so the host can ask you first. The npm package's --read-only flag offers only tools that change nothing.
Event titles and descriptions are written by other people. The server marks them as data, so an agent doesn't take orders from an invitation.
Test keys reach only the sandbox. On live calendars, you confirm each change.
Plans, payment and live keys never go through the agent. It sends you a dashboard link.
Pyas runs no AI models. Your calendar data isn't sent to a model provider by us, and there's no per-call AI cost on your bill.
Underneath is the new v2 API: one event shape for Google and Outlook, signed webhooks retried for 41 hours, a TypeScript SDK, a CLI and a new dashboard. Your users still connect through Pyas Auth, which Google, Microsoft and Zoom have already verified, so you skip Google's OAuth review and Zoom's app review. When you want your own name on the consent screen, switch any provider to Native Auth and use your own OAuth app. If you're on v1, nothing changes until you move to v2, and your keys and connected accounts carry over.
You can find the docs here: https://developer.pyas.io/ai-tools
If you're building with agents, I'd like to hear what you'd want one to do with a calendar.