Does my data leave ShareAndGo when I connect Claude?

Yes, the same way it does if you download a document and paste it into Claude. The difference: native MCP connection has no laptop copy, no email forwarding, and a complete audit trail. We don't train any models on your data.

Can recipients of a data room use their own AI on it?

Only if the room owner has enabled AI access for that room. Recipients can request access; the owner approves or denies.

What's the difference between read and write scopes?

Read lets the AI list rooms, read documents, search, and ask questions. Write additionally lets it create rooms, upload, move, and delete documents. Write is opt-in per token AND per room; both gates must be enabled.

Where can I see what my AI has done?

Every MCP tool call is logged in the room's tamper-evident audit log under actions starting with ai_mcp.* (e.g. ai_mcp.read_document, ai_mcp.upload_document).

Which AI clients are supported?

Anything that speaks MCP. We've tested claude.ai (Custom Connectors), ChatGPT (Custom Connectors), and Claude Desktop (via the npx mcp-remote bridge).

AI Connectors

Connect Claude or ChatGPT
to ShareAndGo

Bring your own AI assistant into ShareAndGo via the Model Context Protocol. Ask questions, search across every room you have access to, and (with write scope) let your AI create rooms and upload documents on your behalf. All without copying a single file.

Set up your connector See setup steps

Two consent gates, by design

AI access in ShareAndGo is controlled at both the connector level (you decide what your AI can do globally) and the room level (each owner decides what AI can do in their specific room). Your AI can only act when both gates are open.

Token scopes (yours)

When you connect your AI, the consent screen shows two checkboxes:

Read access: list rooms, read documents, search, ask questions
Write access: create rooms, upload, move, delete documents

Write defaults to OFF. It's a deliberate opt-in.

Per-room toggles (theirs)

Each room has separate Read access and Write access toggles, controlled by the room owner from the Insights tab. Recipients can request read access; owners must enable write themselves.

Workspace defaults live at Settings → Workspace.

How to connect

From start to working connector in under a minute.

Generate your MCP URL

Open Settings → Integrations in ShareAndGo and scroll to the AI Assistants section. Click Connect AI, give the connector a name, and copy the MCP server URL.

Add the connector to your AI

claude.ai: Settings → Connectors → Add custom → paste the MCP URL. claude.ai handles OAuth for you.

ChatGPT (Plus or higher): Settings → Custom Connectors → Add → MCP → paste the URL.

Claude Desktop: Edit your config file via Settings → Developer → Edit Config and paste the JSON snippet shown after you click Connect AI in ShareAndGo. Restart Claude Desktop.

Approve scopes on the consent screen

Your browser will land on a ShareAndGo consent page showing your email and two checkboxes: Read (default on) and Write (default off). Tick what you want and click Authorize.

Enable AI on a specific room

Open any data room → Insights tab → flip the AI Assistant Access toggle (Read or Write). Your AI client can now see and act on that room.

Try it

In Claude or ChatGPT, ask "What ShareAndGo data rooms can I see?" The connector will call list_data_rooms and show the rooms you've granted access to.

What your AI can do

Read tools work as soon as a room owner enables AI read access. Write tools additionally require AI write access on the room AND the write scope on your token.

list_data_roomsread

List every room with AI access enabled, that the connector's owner can see.

list_documentsread

List documents in a specific room with filenames, AI tags, summaries, and IDs.

search_documentsread

Free-text search across one room or the entire AI-enabled tenancy.

read_documentread

Pull the full extracted text of a specific document.

ask_roomread

Ask a natural-language question. ShareAndGo's AI synthesises an answer from the room's documents.

create_data_roomwrite

Create a new room in the connected user's organisation. Plan limits apply.

upload_documentwrite

Upload a base64-encoded document into a room (max 10MB per file).

create_folderwrite

Create a folder, optionally nested under a parent folder.

move_documentwrite

Move a document to another folder (or to room root).

delete_documentwrite

Soft-delete a document. Recoverable from the Recycle Bin by an admin.

What works in which client

The MCP transport itself is universal, but each AI client's sandbox has different limits. Here's what's reliable today.

Client	Read / search / Q&A	Small writes (rooms, folders, metadata)	File uploads
claude.ai (web)	✓	✓	⚠ Slow / unreliable
Claude Desktop	✓	✓	✓
ChatGPT Desktop	✓	✓	✓ when MCP ships generally
Custom MCP clients	✓	✓	✓

Why claude.ai web is slow on uploads: Anthropic's web sandbox blocks external HTTPS hosts, so the only file-upload path is inline base64 in the tool-call argument. Claude has to materialise the file character-by-character. Fine for a few KB, painful past ~75KB, unreliable past ~150KB. We'll lift the limit when Anthropic improves the sandbox transport. For now, the ShareAndGo web UI is the right place to upload files; let your AI handle everything else.

Example prompts to try

Real prompts that work cleanly in claude.ai web today.

"What ShareAndGo data rooms can I see?"

"Summarise all documents in the BetaCorp ATO Audit room."

"Find every document that mentions 'overseas contractor' across my tax audit rooms, and quote one source clause from each."

"Read the BAS for Q2 2026 and tell me the GST payable."

"Create a new room called 'EOFY 2026 Acme Ltd'."

"Compare the indemnity clauses in the SPA and the Master Services Agreement in the Acme room."

For bulk uploads, document moves at scale, and similar byte-heavy operations, use Claude Desktop, ChatGPT Desktop, or a custom MCP client. See the table above.

Every action is audited

Every tool call your AI makes is recorded in two places: ShareAndGo's global ai_query_logs collection, and the affected room's tamper-evident audit log. Look for actions starting with ai_mcp. in the room's Audit Log tab.

ai_mcp.list_data_rooms · [email protected] via Claude · 2026-05-08 16:42

ai_mcp.search_documents · [email protected] via Claude · 2026-05-08 16:43

ai_mcp.read_document · [email protected] via Claude · 2026-05-08 16:43

ai_mcp.upload_document · [email protected] via Claude · 2026-05-08 16:45

AI-issued tokens can be revoked instantly from Settings → Integrations → AI Assistants. Revocation takes effect on the next request, with no propagation delay.

Troubleshooting

My AI says "no rooms accessible" but I have rooms

This is the per-room consent gate working as designed. Open the room → Insights tab → flip the Read access toggle on. Your AI will see it on the next call.

My AI says "this connector does not have write scope" when creating a room or moving files

You only granted read scope when you authorized the connector. Revoke it from Settings → Integrations → AI Assistants and re-add it, ticking the Write checkbox on the consent screen.

Uploading a file via claude.ai is taking forever or fails

That's a known Anthropic-sandbox limitation, not a ShareAndGo issue. Claude.ai's web client has to base64-encode the file into the tool-call argument character-by-character. Files past ~75KB get slow, past ~150KB get unreliable. For uploads at any size, use the ShareAndGo web UI directly, or switch to Claude Desktop / ChatGPT Desktop / a custom MCP client where uploads work normally.

"AI write access not enabled for this room"

Your token has write scope but the room owner hasn't turned on the room-level write toggle. Open the room → Insights tab → enable Write access (admin only). Both gates must be open.

claude.ai shows "Sign in to ShareAndGo first"

Open shareandgo.com.au, sign in, then re-add the connector in claude.ai. Sessions are scoped to the frontend domain so the consent flow needs an active ShareAndGo session.

Privacy posture

ShareAndGo doesn't train any models on your data. The MCP server simply hands off document content to whichever AI you've connected (Claude, ChatGPT, etc.); that AI's own privacy policy applies to anything it sees. The connection is identical in privacy posture to downloading a document and pasting it into the AI yourself, except more secure: no laptop copy, no email forwarding, full audit trail. The room owner controls whether AI access is even possible.

Ready to bring your AI to ShareAndGo?

Set up takes about 60 seconds. Read access is on by default; write is opt-in. Revoke any time.

Connect your AI

Connect Claude or ChatGPT to ShareAndGo