DataToRAG MCP

Connect your Google Workspace, Jira, and Confluence to Claude — through one MCP endpoint.

DataToRAG is an open-source Model Context Protocol gateway that turns your everyday work tools into something your AI assistant can actually use. Gmail, Calendar, Drive, Docs, Sheets, Slides, Tasks, Contacts, Jira, and Confluence — 77 tools across one endpoint, with multi-account support and token-optimized responses.

• Website → datatorag.com

• Docs → datatorag.com/docs

• Dashboard → datatorag.com/dashboard

Why DataToRAG

Works with any MCP client. Claude Desktop, Cursor, Windsurf, custom agents — anything that speaks the Model Context Protocol.

Google Workspace, natively. 55 tools across Gmail, Calendar, Drive, Docs, Sheets, Slides, Contacts, and Tasks. Search threads, draft replies, label and triage mail, update cells, batch-create slides, find files, manage tasks — from a single prompt.

Atlassian, too. 22 tools for Jira and Confluence: search by JQL or CQL, create and transition issues, read and edit pages, manage comments and attachments.

Multi-account out of the box. Connect personal, shared, and team Google accounts under one endpoint. Your assistant can target a specific account or search across all of them.

Token-optimized. Naive API wrappers dump everything into your context window. DataToRAG tunes tool responses for token efficiency — the same Gmail thread read costs a fraction of the tokens, which means longer conversations and smarter agents.

OAuth per user. Each user signs in with Google and Atlassian themselves. No shared service accounts, no tokens in code.

Self-hostable. MIT-licensed. Run it on your own infrastructure, or use the hosted version at datatorag.com.

Related MCP server: MCP-GET

Quick Start (hosted)

Add this to your MCP client config:

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

Then sign in at datatorag.com/dashboard and connect your Google or Atlassian accounts. That's it — your AI assistant now has access to every tool listed in the docs.

Available Connectors

Each tool is documented with its operations, required OAuth scopes, and example prompts at datatorag.com/docs.

Both connectors are themselves open-source MCP servers that plug into the gateway: gws-mcp and atlassian-mcp.

Architecture

              ┌──────────────────┐
              │    MCP Client    │
              │  Claude Desktop, │
              │   Cursor, etc.   │
              └────────┬─────────┘
                       │
             POST /mcp │  Bearer <OAuth token>
                       │
                       ▼
              ┌──────────────────┐
              │    1. Auth       │── OAuth2 token
              │                  │   validation
              └────────┬─────────┘   401 if invalid
                       │
                       ▼
              ┌──────────────────┐
              │   2. Session     │── Streamable HTTP
              │                  │   Create or reuse
              └────────┬─────────┘
                       │
                       ▼
              ┌──────────────────┐    ┌────────────┐
              │  3. tools/list   │───>│ PostgreSQL │
              │     tools/call   │    │            │
              └────────┬─────────┘    │ users      │
                       │              │ tools      │
                       ▼              │ accounts   │
              ┌──────────────────┐    │            │
              │  4. Route by     │<──>│            │
              │     namespace    │    └────────────┘
              └────────┬─────────┘
                       │
          ┌────────────┼─────────────┐
          ▼            ▼             ▼
   ┌────────────┐ ┌────────────┐ ┌──────────┐
   │  gws-mcp   │ │ atlassian- │ │ plugin-n │
   │  (Node.js) │ │    mcp     │ │   ...    │
   │ :40000/mcp │ │ :40001/mcp │ │          │
   └────────────┘ └────────────┘ └──────────┘

The gateway is a thin routing layer: it authenticates the client, forwards per-user OAuth tokens to the plugin that owns the tool namespace, and streams the response back. Plugins run as separate Node.js processes — they can be added, removed, or replaced without changing the gateway.

Self-Hosting

Prerequisites

• Docker

• A PostgreSQL database and its connection string in DATABASE_URL — any Postgres works (Neon, RDS, or a container you run yourself). The dev stack does not start one for you.

• Google OAuth client for login (and a separate one for Google Workspace scopes)

• Atlassian OAuth client (optional, for Jira + Confluence)

Local Development

# Apply the schema to your database (once, and after any schema change)
pnpm --filter @datatorag-mcp/db db:push

# Boot the gateway
DATABASE_URL=<your-postgres-url> \
  docker compose -f docker/docker-compose.dev.yml up -d

Migrations are deliberately not run on startup — the stack never mutates your schema as a side effect of booting.

Connect a local MCP client:

{
  "mcpServers": {
    "datatorag": {
      "url": "http://localhost:8285/mcp"
    }
  }
}

Development Without Docker

pnpm install

# Push schema + seed a test user
DATABASE_URL=<your-postgres-url> \
  pnpm --filter @datatorag-mcp/db db:push && \
  pnpm --filter @datatorag-mcp/db db:seed

# Start gateway (reads DATABASE_URL from the root .env)
pnpm dev:gateway

Environment Variables

Production Deployment

Production runs on Docker Compose with a build-arg pipeline for NEXT_PUBLIC_* values. See docker/docker-compose.prod.yml and apps/gateway/Dockerfile for the reference setup.

Project Structure

apps/
  gateway/             MCP proxy server (Express + MCP SDK) + Next.js dashboard
    src/
      app/             Dashboard, docs, landing page (Next.js App Router)
      gateway/         MCP routing, auth, plugin manager, tool tracking
      lib/             Shared utilities (docs parser, analytics, hooks)
    content/
      blog/            Markdown blog posts
      docs/            Markdown connector docs
    server.ts          Custom Express server entry point
packages/
  config/              Environment variable parsing (zod schema)
  db/                  Drizzle ORM schema + database client
  types/               Shared TypeScript types
  auth/                OAuth helpers
docker/
  docker-compose.dev.yml    Local development stack
  docker-compose.prod.yml   Production (Lightsail)

Contributing

Issues and pull requests welcome. For substantial changes, open an issue first so we can align on direction.

License

MIT