Give your AI assistant direct access to your financial data.

You do not need a paid plan. Custom MCP connectors live behind Developer mode in ChatGPT, which is available on the free tier as well as Plus, Pro, Business and Enterprise. If you only see the public Apps catalogue at Settings → Apps with no Advanced section, your account has not been enrolled yet — use Claude Desktop or Cursor in the meantime.

Step by step:

1. Open Settings → Apps → Advanced and turn Developer mode on.
2. Back on the Apps page click Create app and pick MCP server.
3. Fill in:
   • Name: MosaicHub — use a single word with no spaces. ChatGPT exposes the connector to the model as a namespace and removes spaces, so "Mosaic Hub" would surface as Mosaic_Hub in the tool router.
   • Description: "Read your Mosaic Hub data — Numbers (profit and loss, transactions, balances), People (payroll, leave) and Personal (documents, pensions)."
   • MCP Server URL: https://mcp.mosaic.co.za/mcp
   • Authentication: OAuth (leave Advanced OAuth settings blank — they auto-discover from the URL).
4. Tick the risk-acknowledgement checkbox and save.
5. On the connector card, click Connect. A new browser tab opens to hub.mosaic.co.za: sign in, tick which Mosaic clients ChatGPT may read on the consent screen, click Allow access.
6. The tab closes itself. The card now shows Connected · Authorization used: OAuth.

There is nothing technical to paste — no key, no header, no config file. ChatGPT figures out how to talk to Mosaic Hub on its own; you just sign in once when prompted, and it remembers from there.

Open a new chat and start your message with @MosaicHub. ChatGPT only uses custom connectors on conversations that explicitly point at them — the built-in tool router (web search, image generation, code interpreter) outranks every custom MCP connector by default, so a generic *"what is my profit and loss for May?"* prompt will usually get an apology that ChatGPT cannot see your accounting system. Anchor every Mosaic Hub question to the connector and the model will route to it without hesitation.

Examples that work:

• "@MosaicHub list my clients."
• "@MosaicHub show me the profit and loss for Achiever Corporation for May 2026." (any client display name from your consent works — ChatGPT calls numbers_list_clients first to resolve names).
• "@MosaicHub what are the overdue receivables on Achiever Trust as of today?"
• "Using @MosaicHub, give me a financial-analysis summary for Achiever Corporation. Include margins and the current ratio."

Once the conversation has called a Mosaic Hub tool once, ChatGPT remembers the connector for the rest of that chat — you can drop the @MosaicHub prefix on follow-up questions in the same conversation. For a brand-new chat, always lead with @MosaicHub again.

If ChatGPT replies that it cannot see your data even with @MosaicHub, the connector is probably disabled on the chat. Click the tools icon below the message box and confirm MosaicHub is enabled for this conversation.

The Mosaic clients you explicitly ticked on the consent screen, only for the modules you ticked, and only if the relevant MCP access right (Numbers MCP, People MCP, Personal MCP) is enabled on your account for each (set by the client owner under Home → Access Rights). The granted-module set and the granted-client list are both frozen into the OAuth access token at consent time, so ChatGPT cannot widen scope mid-session even if asked — if you withhold People at the consent screen, the assistant never sees a single People tool, no matter what it tries.

In your Hub portal go to Home → Developer → Model Context Protocol. The Connected applications table lists every assistant (ChatGPT, Claude, custom agents) you have authorised, with the scopes granted, the clients tied to that consent, and the last time the access token was used. A single Revoke click kills both the access and refresh tokens immediately.

To revoke from ChatGPT's side, go to Settings → Apps → MosaicHub → Delete app. Doing it in both places leaves nothing behind.

In Claude Desktop go to Settings → Developer → Edit Config. Open claude_desktop_config.json and add:

{
  "mcpServers": {
    "mosaic-hub": {
      "url": "https://mcp.mosaic.co.za/mcp"
    }
  }
}

Save the file and restart Claude Desktop. The first time you use a Mosaic Hub tool, Claude pops up the Hub sign-in + consent screen in your browser. No keys to copy, no shared secrets in the config file.

No. There is one Mosaic Hub MCP connector and one connector URL. Modules — Numbers, People, Personal — are tickboxes on the consent screen, not separate connectors. When People and Personal tools ship they appear inside the same connector you already added, the next time you sign in. If you don't want a particular module visible to a given AI assistant, untick it on the consent screen for that connection.

Claude Desktop shows the connected server in the chat toolbar. Try: "List the tools you have available from Mosaic Hub." You should see fifteen numbers_* tools covering bank accounts, sub-ledgers, trade balances, sales, purchases, profit and loss, statement of financial position, the financial-analysis snapshot and general-ledger drill-down. people_* and personal_* tools join the same list once those modules ship.

Open Cursor Settings → Features → Model Context Protocol → Add new MCP server. Set:

• Name: mosaic-hub
• Type: HTTP (Streamable HTTP — the modern MCP transport)
• URL: https://mcp.mosaic.co.za/mcp

Leave the auth field blank. The first time Cursor uses a Mosaic Hub tool, it pops a browser tab to sign you in. Cursor remembers the connection per workspace from then on.

Yes — once the server is enabled in MCP settings, Cursor's chat advertises the tools to the model and calls them when relevant. You can also force a call by display name, for example "Use the Mosaic Hub connector. Show me the profit and loss for Achiever Corporation for May 2026."

Open Zed → Settings → Open settings.json and add a context_servers entry:

{
  "context_servers": {
    "mosaic-hub": {
      "url": "https://mcp.mosaic.co.za/mcp"
    }
  }
}

Reload the Zed window. On first use, Zed walks you through the Mosaic Hub OAuth sign-in + consent in your browser, then caches the token. The Mosaic Hub tools appear in Zed's Assistant panel.

MCP Streamable HTTP (the modern transport from the 2025-06-18 spec revision). One unified endpoint at POST /mcp accepts every JSON-RPC message in a single round-trip; the response body is either JSON or an SSE event stream on the same response (the client picks via Accept). There is no Mcp-Session-Id, no SSE long-poll and no persistent server-side session state. Any MCP SDK with a Streamable HTTP client will work — the official Python mcp SDK, the TypeScript @modelcontextprotocol/sdk, and both LangChain's and LlamaIndex's MCP adapters.

Use any MCP SDK with built-in OAuth 2.1 client support. The flow:

1. Open POST /mcp with an MCP initialize JSON-RPC body. With no Bearer header the server returns 401 plus a WWW-Authenticate: Bearer resource_metadata="…/.well-known/oauth-protected-resource" header.
2. Fetch that metadata document, discover https://hub.mosaic.co.za as the authorisation server, and fetch /.well-known/oauth-authorization-server for its endpoints.
3. Dynamically register your client at /oauth-register.php (RFC 7591), run the authorization-code + PKCE flow at /oauth-authorize.php → /oauth-token.php, and resend the initialize POST with Authorization: Bearer mh_at_…. Every subsequent tools/list / tools/call request is an independent authenticated POST to the same endpoint.

Tokens last one hour; refresh tokens last 90 days and rotate on every use.

The PostgreSQL read role caps concurrent connections at 8, and the asyncpg pool keeps a max of 4 per App Service instance, so practical concurrency is fine for individual members but not for high-fanout backends. Each session is in-process; do not assume horizontal stickiness.

Open the Connected applications view in your Hub portal and click Revoke next to the assistant. The connection is cut immediately. The assistant has to ask for permission again before it can read anything — and you can simply not grant it.

Only data for the clients you explicitly ticked during the Mosaic Hub sign-in screen, and only where you already have Model Context Protocol access in the portal. The list of clients the assistant may read is locked in for that session, so it cannot expand it mid-conversation.

No. The connector is strictly read-only — it can answer questions about your data but cannot create, edit or delete anything. Even if you ask it to, the request will be refused. Any changes to your Mosaic Hub still happen the way they always have: through the portal, with you in the driver's seat.