DataToRAG

com.datatoragPublished by datatorag.comOfficial publisherv1.0.0Updated Oct 29, 2026

Hosted MCP for Google Workspace, Atlassian and Notion: one OAuth, per-user accounts, write access.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & MemoryCommunication & Collaboration

Overview

AI-generated overview

Hosted MCP gateway that connects an assistant to a user's own Google Workspace, Atlassian and Notion accounts through one OAuth sign-in.

What you can do
  • Read and write Gmail, Calendar, Drive, Docs, Sheets, Slides, Contacts and Tasks
  • Work with Jira issues and Confluence content
  • Create and edit Notion pages, databases and comments
  • List connected accounts, run ready-made skills, and create single-use file upload and download links
  • Move files between services by reference, returning size and SHA-256
When to use it
Useful when an assistant should work across Google Workspace, Jira, Confluence and Notion under one connection, including several accounts per service, and when you want a hosted endpoint rather than a local process.
Requirements
Remote endpoint at datatorag.com/mcp over Streamable HTTP; OAuth sign-in with the same email in the client and the dashboard. Each user must connect their Google, Atlassian or Notion accounts in the dashboard and grant the requested scopes. Self-hosting needs Node.js 20 or later, pnpm 9, Postgres via DATABASE_URL, CONNECTION_TOKEN_KEYS and OAuth client credentials per provider.
Before you install
Grants write access to mail, calendars, files, issues and pages, so the assistant can send, change and delete data in those accounts. Google's consent screen starts with every scope unticked and the README advises ticking all or the ones you want, so review scopes carefully. Provider tokens are stored encrypted server-side, and calls are metered. Files from your computer go through single-use upload links.

Installation

In SourceWeft

  1. Open DataToRAG in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.datatorag%2Fmcp-gateway/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "datatorag": {
      "type": "http",
      "url": "https://datatorag.com/mcp"
    }
  }
}

README

[DataToRAG: your work tools behind one MCP endpoint. Gmail, Drive, Docs, Sheets, Calendar, Jira, Confluence and Notion connected to datatorag.com/mcp, used from any MCP client.]

Google Workspace, Jira, Confluence and Notion for Claude and other MCP clients, through one endpoint.

[License: MIT] [CI status on main] [Last commit on main] [143 tools as of October 2026] [Works with Claude, Cursor and ChatGPT]

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

Try it in 60 seconds

Setup is two connections, and both are needed:

  1. Connect your accounts. Sign in at datatorag.com/dashboard and connect Google, Atlassian or Notion. Google's consent screen arrives with every box unticked: tick "Select all", or the services you want.
  2. Connect your AI client to 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.

bash
claude mcp add --transport http datatorag https://datatorag.com/mcp

Cursor and other clients that take a JSON config.

json
{  "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.

Screenshots

[The dashboard agent searching Notion with notion_search, reading the page with notion_get_page, and summarising what it says.]

The agent in the dashboard runs the same tools against your connected accounts, with no client setup.

[The upload page after a file was sent: the file's name, size and SHA-256, and a short reference to paste back into the conversation.]

An upload link takes one file from your computer, up to 25 MB, and answers its size and SHA-256.

[The public status page: the latest full check of production, with checks working and failing, tools working, and Gmail's results by check.]

The status page shows the latest end-to-end run against production, by service.

Connectors

Tool counts are from the code as of October 2026: 133 tools in the three connectors, and 10 built into the gateway.

ConnectorToolsServicesDocs
Google Workspace (plugins/gws-mcp)87Gmail, Calendar, Drive, Docs, Sheets, Slides, Contacts, Tasksdocs
Atlassian (plugins/atlassian-mcp)28Jira, Confluencedocs
Notion (plugins/notion-mcp)18Pages, databases, commentsdocs
Gateway built-ins10Connected accounts, skills, file upload and download links, a connectivity checkdocs

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.

What makes it different

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).

Architecture

[How a tool call travels: an MCP client posts to /mcp with a bearer token; the DataToRAG gateway authenticates it, serves tools/list from the registry and routes tools/call to the plugin that owns the tool; each plugin calls its service's API with the user's OAuth grant; Postgres holds users, accounts, provider tokens and the tool registry.]

In text:

  1. Client. Any MCP client sends Streamable HTTP to POST /mcp with a bearer token: an OAuth access token from the gateway's own authorization server, the only credential it accepts.
  2. Gateway (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.
  3. Built-ins. list_connected_accounts, skills_*, file_upload_link and file_download_link are answered by the gateway itself, with no plugin and no registry row.
  4. Plugins. Each connector is an MCP server under 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.
  5. Registry. Postgres holds users, connected accounts, provider tokens and the tool registry (name, description and input schema for each plugin tool). Changes to the registry in production are SQL files under registry/, applied by the registry workflow after an approval.

Self-hosting

Prerequisites

  • Node.js 20 or later and pnpm 9.
  • A Postgres database, and its connection string as DATABASE_URL. Any Postgres works; nothing here starts one for you.
  • An OAuth client for each provider you want: Google (one client for sign-in, a second for Workspace scopes), Atlassian, Notion.

Run the gateway

bash
pnpm installpnpm -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 clientspnpm --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):

PathWhat it is
/mcpThe MCP endpoint
/dashboardSign in, connect accounts, the agent
/docs/getting-startedThe docs
/healthLiveness, and each plugin's state
/.well-known/oauth-authorization-serverOAuth 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).

Environment variables

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:

VariablePurpose
DATABASE_URLPostgres connection string. Required
CONNECTION_TOKEN_KEYSKeys the provider tokens are encrypted with: <id>:<base64 of 32 bytes>, comma separated, the first encrypts and all decrypt. Required; make one with openssl rand -base64 32
GATEWAY_PORT, GATEWAY_BASE_URLPort, and the public URL OAuth redirects are built from
GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRETGoogle sign-in for the dashboard
GOOGLE_GWS_CLIENT_ID, GOOGLE_GWS_CLIENT_SECRETGoogle Workspace connections
ATLASSIAN_CLIENT_ID, ATLASSIAN_CLIENT_SECRETJira and Confluence connections
NOTION_OAUTH_CLIENT_ID, NOTION_OAUTH_CLIENT_SECRETNotion connections
SLACK_CONNECTOR_CLIENT_ID, SLACK_CONNECTOR_CLIENT_SECRET, SLACK_CONNECTOR_TEAM_IDSlack connections, for one workspace and admins only; optional
ANTHROPIC_API_KEY, PLAYGROUND_MODELThe dashboard agent; empty turns it off
STRIPE_*Billing; optional
POSTHOG_API_KEY, SLACK_BOT_TOKEN, BREVO_API_KEYAnalytics, notifications and email; each is off when empty

Production

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.

Project structure

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: dashboard, docs, blog, changelog, status, skills  src/mastra/          The dashboard agent  content/             Markdown for the blog, changelog, docs and skillspackages/  config/              Environment schema (zod)  db/                  Drizzle schema and migrations  auth/                Token hashing and constant-time compares  types/               Shared types, including the plugin manifestplugins/  gws-mcp/             Google Workspace connector  atlassian-mcp/       Jira and Confluence connector  notion-mcp/          Notion connectorregistry/              Reviewed SQL for changes to the tool registrydocker/                Compose filesscripts/               The pre-merge gate, leak scan, deploy and registry helpersdocs/                  Architecture notes and implementation planstools/capture/         Product screenshots and recordings (Remotion)

Contributing

Issues and pull requests are welcome. For a substantial change, open an issue first so we can agree on the direction; every pull request runs the gate (typecheck and tests) and a leak scan.

Security

Please report a vulnerability privately to [email protected] rather than in a public issue.

License

MIT

Source: README.md at commit 9aa3915

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts