Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Description from the maker (original English)
Hosted MCP for Google Workspace, Atlassian and Notion: one OAuth, per-user accounts, write access.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://datatorag.com/mcpRun this in your terminal
claude mcp add --transport http gateway https://datatorag.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"gateway": {
"url": "https://datatorag.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"gateway": {
"type": "http",
"url": "https://datatorag.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://datatorag.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain datatorag.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 222 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 9 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Agent-Native Google Calendar - manage events, sync, and public booking
Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Google Workspace, Jira, Confluence and Notion for Claude and other MCP clients, through one endpoint.
DataToRAG is an open-source Model Context Protocol gateway. You point your AI client at one URL. Each person connects their own Google, Atlassian and Notion accounts, and the gateway hands the client the tools for those accounts, calling the services with the person's own OAuth grant. It runs hosted at datatorag.com, or on your own infrastructure under the MIT license.
Website · Docs · Status · Changelog · Skills
Setup is two connections, and both are needed:
https://datatorag.com/mcp, then sign in with the same email when the client asks.Claude (web and Desktop). Customize, then Connectors, then Add, then "Add custom connector". Paste the URL and leave the advanced OAuth fields empty.
Claude Code.
claude mcp add --transport http datatorag https://datatorag.com/mcp
Cursor and other clients that take a JSON config.
{
"mcpServers": { "datatorag": { "url": "https://datatorag.com/mcp" } } }
ChatGPT. Settings, then Connectors, enable Developer mode, then Create, and paste the URL.
The getting started guide has screenshots of each step. Every client connects with OAuth.
The server is listed in the official MCP registry as com.datatorag/mcp-gateway; server.json is the listing.
The agent in the dashboard runs the same tools against your connected accounts, with no client setup.
An upload link takes one file from your computer, up to 25 MB, and answers its size and SHA-256.
The status page shows the latest end-to-end run against production, by service.
Tool counts are from the code as of October 2026: 133 tools in the three connectors, and 10 built into the gateway.
| Connector | Tools | Services | Docs |
|---|---|---|---|
Google Workspace (plugins/gws-mcp) | 87 | Gmail, Calendar, Drive, Docs, Sheets, Slides, Contacts, Tasks | docs |
Atlassian (plugins/atlassian-mcp) | 28 | Jira, Confluence | docs |
Notion (plugins/notion-mcp) | 18 | Pages, databases, comments | docs |
| Gateway built-ins | 10 | Connected accounts, skills, file upload and download links, a connectivity check | docs |
The three connectors live in this repository under plugins/ and ship inside the gateway's image. A client only sees the tools for services its user has connected.
Several accounts per service. Connect a work and a personal Google account, or two Notion workspaces, under one login, and pick a default. Every connector tool takes an account argument to choose one (how we built it).
Responses sized for a context window. Tools return what the model needs rather than the raw API response. A two-page Google Doc comes back as 2 to 3 KB of text instead of 50 KB or more of JSON (the write-up).
OAuth per user. Each person grants access to their own accounts, and the gateway refreshes the grants. A connector receives only the calling user's access token, never a shared credential.
Files move between services without passing through the chat. A file reference names an email, an attachment or a Drive file, and the gateway carries it to Jira, Drive or an email in one call, answering with its size and SHA-256. Files from your computer arrive through a single-use upload link (file references).
Skills. Ready-made workflows, such as a morning brief or inbox triage, that run in the dashboard, on a schedule, or from any client as MCP prompts (skills, announcement).
A public status page. A test run calls the tools on production the way a user would and publishes what works, by service (status).
In text:
POST /mcp with a bearer token: an OAuth access token from the gateway's own authorization server, the only credential it accepts.apps/gateway, one Node.js process: Express plus Next.js). It authenticates the bearer, opens or reuses the session, and answers tools/list from the tools table in Postgres, filtered to the services the user has connected. A tools/call is split on __ into the plugin and the tool, the user's token for that service is resolved (and refreshed if expired), and the call is forwarded to the plugin. Every call is metered. The same process serves the dashboard and its agent, the docs, the changelog and the status page.list_connected_accounts, skills_*, file_upload_link and file_download_link are answered by the gateway itself, with no plugin and no registry row.plugins/. The gateway starts each one as a child process under its own non-root account, with an environment of PATH, NODE_ENV and PORT only, and passes the user's token on each call in the X-User-Token header. A crashing plugin is restarted up to three times a minute, and /health reports each plugin as up or down.registry/, applied by the registry workflow after an approval.DATABASE_URL. Any Postgres works; nothing here starts one for you.pnpm install
pnpm -r --filter "./packages/*" run build # the gateway reads these packages' built output
cp .env.example .env # then fill in DATABASE_URL, CONNECTION_TOKEN_KEYS and the OAuth clients pnpm --filter @datatorag-mcp/db db:migrate # schema changes are never applied on start
pnpm dev:gateway
The gateway listens on http://localhost:8285 (set by GATEWAY_PORT):
| Path | What it is |
|---|---|
/mcp | The MCP endpoint |
/dashboard | Sign in, connect accounts, the agent |
/docs/getting-started | The docs |
/health | Liveness, and each plugin's state |
/.well-known/oauth-authorization-server | OAuth metadata for MCP clients |
On a laptop the gateway loads plugins from ~/.datatorag/plugins, or from DATATORAG_PLUGINS_DIR when it is set. Build them with pnpm --filter @datatorag-mcp/gws-mcp run build (and the same for atlassian-mcp and notion-mcp).
The full list, with comments, is in .env.example, and the schema that validates it is packages/config/src/index.ts. The ones a self-host needs:
| Variable | Purpose |
|---|---|
DATABASE_URL | Postgres connection string. Required |
CONNECTION_TOKEN_KEYS | Keys the provider tokens are encrypted with: : , comma separated, the first encrypts and all decrypt. Required; make one with openssl rand -base64 32 |
GATEWAY_PORT, GATEWAY_BASE_URL | Port, and the public URL OAuth redirects are built from |
GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET | Google sign-in for the dashboard |
GOOGLE_GWS_CLIENT_ID, GOOGLE_GWS_CLIENT_SECRET | Google Workspace connections |
ATLASSIAN_CLIENT_ID, ATLASSIAN_CLIENT_SECRET | Jira and Confluence connections |
NOTION_OAUTH_CLIENT_ID, NOTION_OAUTH_CLIENT_SECRET | Notion connections |
SLACK_CONNECTOR_CLIENT_ID, SLACK_CONNECTOR_CLIENT_SECRET, SLACK_CONNECTOR_TEAM_ID | Slack connections, for one workspace and admins only; optional |
ANTHROPIC_API_KEY, PLAYGROUND_MODEL | The dashboard agent; empty turns it off |
STRIPE_* | Billing; optional |
POSTHOG_API_KEY, SLACK_BOT_TOKEN, BREVO_API_KEY | Analytics, notifications and email; each is off when empty |
Production runs the image built from apps/gateway/Dockerfile, which carries the three plugins. A merge to main builds and publishes it (build.yml), and a deploy is dispatched by hand and approved (release.yml), starting it with docker/docker-compose.prod.yml.
apps/gateway/ The product: MCP gateway, OAuth server, dashboard, site
server.ts Express entry: /mcp, /oauth, /auth, /files, /health src/gateway/ Tool routing, auth, plugin manager, file references, metering src/app/ Next.js app: dashb
Only the beginning is shown; read the rest in the repo