Documentation
Connect your calendar to your AI client.
Connect Google Calendar once, add this remote MCP server to a compatible client, and approve that client in your browser. Calendar access is scoped to the Google account you connect.
https://tarikul-open-mcp-server.vercel.app/mcpWorks in MCP Inspector and other clients that support Streamable HTTP.
Connection flow
Connect once, then use your tools
STEP 01
Sign in to the dashboard
Choose Continue with Google. This signs you in and creates your personal account on the server; it does not connect Google Calendar yet.
STEP 02
Connect Google Calendar
In the dashboard, choose Connect Calendar and approve the requested read/write Google Calendar access. Calendar credentials are stored on the server for your account.
STEP 03
Add the remote server to your MCP client
Use the endpoint below in a client that supports Streamable HTTP and OAuth. The client discovers the authorization flow from the server automatically.
STEP 04
Review and approve the client
The client opens a browser page showing which MCP client is requesting access. Sign in if prompted, check the client name, then choose Allow access. Approval is saved separately for each user and client.
STEP 05
Use your calendar tools
Your assistant can now read or change events in the primary Google Calendar connected to your account. If you approved the client before connecting Calendar, connect it from the dashboard; you do not need to set up the client again.
Personal accounts
Each person keeps a separate calendar
Multiple people can use the same server. Each person signs in with Google, connects their own Calendar, and approves MCP clients for their account.
Your Google sign-in → your stored Calendar credentials → your primary Calendar
Their Google sign-in → their stored Calendar credentials → their primary Calendar
Every MCP access token identifies one Google account. Calendar tools use that identity for every request, so a client authorized for one account cannot switch to another account’s Calendar.
Available tools
What an AI assistant can do
Calendar tools work with the signed-in account’s primary Google Calendar. Event creation and changes happen using the Google account that signed in.
calendar_list_eventsList upcoming events from your primary calendar. Optional maxResults is 1–100; defaults to 10.calendar_find_events_by_dateList events between startDate and endDate (ISO 8601 with timezone); returns up to 100.calendar_find_eventGet an event by its Google Calendar eventId.calendar_create_eventCreate an event with summary and start/end times; description and Google colorId are optional.calendar_update_eventUpdate an event's summary, description, start/end times, or colorId; omitted fields stay unchanged.calendar_delete_eventPermanently delete an event by its eventId.health_checkCheck that the MCP server is running.example_toolEcho a message; a simple tool for checking a client connection.
Event times use ISO 8601 date-time values with a timezone, such as 2026-10-22T14:00:00+06:00. Create and update currently support the fields listed above.
Security
Account access stays separate and revocable
Google sign-in
Signing in identifies your account. Connecting Google Calendar is a separate step that requests calendar access. Each MCP client then needs your approval for that account.
Short-lived access
Authorization codes use PKCE and expire after 5 minutes. MCP access tokens expire after 15 minutes and are renewed using rotating refresh tokens. Refresh tokens have a 30-day lifetime. Removing an MCP client in the dashboard blocks its access immediately.
Server-side credentials
Google credentials are stored on the server per account and are not sent to the browser or MCP client.
Manage access
The dashboard lists MCP clients for your Google account. Remove access there to block that client’s current tokens and future renewals, or restore it later to reconnect. The list shows the client name supplied during connection; it cannot identify a specific AI model.
Disconnect Calendar
Disconnecting removes this server's saved Calendar credentials. MCP client grants remain listed until you remove them. Calendar tools work again after you reconnect Calendar.
Troubleshooting
Quick fixes for common connection issues
Calendar tools say Calendar is not connected
Open the dashboard and connect Google Calendar. Approving an MCP client and granting Google Calendar access are separate steps.
The OAuth client or redirect is rejected
Start authorization from the MCP client so it can register its callback address. Use the exact server endpoint shown above and do not edit the generated redirect URL.
You want to stop one client’s access
In the dashboard, remove that MCP client under MCP access. Its tokens stop working immediately. Disconnect Calendar separately to remove the Calendar credentials stored by this server.
Ready to connect?
Sign in to see your connection status and manage your account.