One MCP endpoint, every client account

Your assistant connects to one mailbox. You have four clients.

Claude and Cursor attach a single Microsoft or Google account. Fractional work does not fit in one. Conflu puts every client account behind one endpoint, and every answer says which one it used.

Free plan, no card. Two accounts, 500 requests a month.

mcp.conflu.xyz · 3 accounts connected

What came in this morning across all my clients?

Checked three connected mailboxes:

  • you@client-a.commicrosoftBoard pack due Thursday — three replies waiting on you.
  • you@client-b.comgoogleSecurity review signed off. Invoice approved for payment.
  • you@client-c.commicrosoftNothing urgent. Two calendar invites for next week.

Every response names the account_email it read from.

Microsoft 365LIVE
Google WorkspaceLIVE

Mail · Calendar · Contacts · Tasks · Files

Today you reconfigure. Or you stop asking.

Without ConfluYou, three client accounts, and an AI client wired to only one of them — the other two are dotted linesYouClient AClient BClient CAI clientone account only
Two of the three are dotted lines. To reach them you disconnect, reconnect and re-approve consent — every time you switch client.
With ConfluYou, one Conflu endpoint, and every client account reachable through itYouConfluone endpointClient AClient BClient C
Connect each account once. Ask across all of them in one question, and read back which mailbox each answer came from.

Set up once. Then forget it.

One URL and one key go into your AI client. Adding a fourth client later changes nothing on that side.

Read the setup guide
  1. 1

    Sign in to each client account

    OAuth once per mailbox, Microsoft or Google, across as many tenants as you work with.

  2. 2

    Paste one endpoint into your AI client

    url https://mcp.conflu.xyz/v1
    auth Bearer cfx_••••••••••••
  3. 3

    Ask across clients

    Name one account, or say “all of them”. A broken connection never silences the rest — the answer lists what it could not reach.

Eighteen tools your assistant can actually call

Nine per provider, identical in shape. List tools take an account or all of them at once; read tools need one account.

Mail

List and read messages from any folder.

microsoft_list_emailsmicrosoft_read_emailgoogle_list_emailsgoogle_read_email

Calendar

Upcoming events, over any window you ask for.

microsoft_list_calendar_eventsgoogle_list_calendar_events

Contacts

Find a person across every client at once.

microsoft_list_contactsgoogle_list_contacts

Tasks

List, create and complete — the only writes Conflu makes.

microsoft_create_taskgoogle_complete_task

Files, read-only

Search OneDrive and Drive, and read text files up to your plan's cap. Conflu downloads only what it will return, and says when a file was truncated instead of implying it read the whole thing.

microsoft_list_files · microsoft_read_file · google_list_files · google_read_file

Partial results, by design

One expired token used to silence every other mailbox. Now a list call returns what it could reach and names what it could not, so an assistant can tell you a client is missing instead of quietly leaving it out.

accounts_queried · accounts_skipped · errors[]

More connectors (Slack, Notion, accounting tools, and others) will use the same multi-account MCP model when they ship — Pro and Ultra plans are built for that expansion.

Your clients' mail never lands on our servers.

You are handling other people's businesses. That deserves a plain answer rather than a badge.

Read what we store
  • Nothing is stored. Mail, calendar, contacts and files stream live from Microsoft Graph and Google, straight through to your assistant.
  • Tokens live in Secret Manager, one per account, never in the database. Disconnect an account and its token is deleted with it.
  • Every call is logged for you, with the account, the tool, the latency and the bytes — so you can see what an assistant did on a client's behalf.
  • Read-only where it matters. Files are never written. The only writes Conflu can make are creating and completing your own tasks.

Start free. Pay when a client depends on it.

Limits are on accounts, requests and data — never on which provider you may connect.

Free

$0

For trying it on one client

  • Microsoft 365 and Google Workspace
  • 2 connected accounts
  • 500 MCP requests / month
  • 50.0 MB egress / month
  • List cloud files (OneDrive and Drive); file content on Pro or Ultra
Get started

Pro

MOST FRACTIONAL WORK

$19 /month

Four clients, comfortably

  • Microsoft 365 and Google Workspace
  • 10 connected accounts
  • 50,000 MCP requests / month
  • 50.00 GB egress / month
  • Read file content up to 10.0 MB per file
  • Need more for one month? Ask us about top-ups
Start on Pro

Ultra

On request

Heavier file and data use

  • Microsoft 365 and Google Workspace
  • 25 connected accounts
  • 250,000 MCP requests / month
  • 100.00 GB egress / month
  • Read file content up to 50.0 MB per file
  • Web Crawling allowance: 1,000 pages / month (not shipped yet)
Contact us

Compare plan limits →

Questions people ask first

What is an MCP endpoint?
An MCP endpoint is a single URL your AI client (Claude, Cursor, and others) calls to access tools. Conflu gives you one streamable HTTP endpoint that covers every connected client account — no separate setup per mailbox or tenant.
Which tools does Conflu support today?
Microsoft 365 and Google Workspace only: list and read mail, calendar events, contacts, tasks, and read-only OneDrive and Google Drive files (list on every plan; file content on Pro and Ultra). Each tool accepts an account_id so your assistant can target one client mailbox or query them all.
Where are my emails stored?
They are not stored on our servers. Conflu is privacy-first: email and calendar data stream live from Microsoft Graph and Google APIs. We keep OAuth tokens only, in Google Cloud Secret Manager — not in Firestore.
Can I use multiple client accounts?
Yes — multi-account is the point. OAuth once per account, label each client (for example "Client A", "Client B"), and pass account_id on each MCP call so your assistant knows which mailbox to use — without reconfiguring your AI client.
Which AI clients work with Conflu?
Any MCP client that supports streamable HTTP: Claude Desktop, Cursor, Windsurf, and others. Paste one MCP URL from your dashboard and use the same endpoint across all connected accounts.
How is Conflu different from a regular MCP server?
Most MCP servers connect one account per provider. Conflu connects many Microsoft or Google accounts behind one endpoint. You choose the account per tool call; the assistant can also see which account_email was used in the response.
Who is Conflu for?
Fractional and independent professionals — fractional CTOs, CFOs, and CMOs, consultants, and freelancers — who juggle separate Microsoft 365 and Google Workspace accounts across several clients.
How does billing work?
Conflu has three plans: Free ($0), Pro ($19/month), and Ultra, priced on request while it is still self-serve only for early customers. Each plan sets monthly limits on connected accounts, MCP requests, and data egress. When you reach a limit, calls return quota errors until you upgrade or the next billing period begins.
Is my data secure?
Conflu stores no email, calendar, contact, or file content. It keeps only OAuth tokens, encrypted at rest in Google Cloud Secret Manager — never in the database. Provider data streams live from Microsoft Graph and Google APIs and is never cached or indexed.

Connect one client account and ask it something.

Two minutes, no card. If it does not save you a reconfiguration this week, it was not for you.

Connect an account