Analytics Brain MCP

Analytics Brain is Witbee's knowledge base on marketing analytics, tracking and data engineering: webinar write-ups, newsletter issues, procedures and guides.

This connector exposes that knowledge base to an AI assistant over the Model Context Protocol. Once connected, the assistant can search the library and read documents in full while answering, and cite what it used — instead of relying on whatever it happens to remember.

It is read-only. The connector can read Witbee content that your account is entitled to, and nothing else.

Endpoint

https://mcp.brain.witbee.com/mcp

Connecting

The exact wording differs between clients, but the shape is the same everywhere: add a custom connector, paste the endpoint, complete the sign-in that opens in your browser.

Claude — Settings → Connectors → Add custom connector → paste the endpoint.

ChatGPT — Settings → Connectors → Add → paste the endpoint. Requires a plan that allows custom MCP connectors.

Gemini — add the server through your client's MCP configuration, using the endpoint above.

Any other MCP-compatible client works too, as long as it supports Streamable HTTP and OAuth 2.1.

There is no API key to issue, copy or rotate — clients register themselves. You sign in with your Analytics Brain account in the browser and approve the connection once.

Access

You need an Analytics Brain account. The connector acts strictly as the signed-in user: it can read exactly the documents that account is granted, and a document outside those grants is not visible to it at all — it is absent from listings rather than merely unreadable.

If you do not have an account yet, create one.

Tools

The connector exposes three tools, all read-only. Your assistant reaches for them on its own — you do not call them by hand.

list_documents — returns every knowledge-base document the account may read, with names, short descriptions and the folder structure. No bodies.

search_documents — full-text search across titles and bodies. Returns matches with a snippet around the hit.

read_document — returns one document in full, together with its ancestor chain for context.

What it cannot do

Worth being explicit, because it is the usual first question:

• No access to your own data. No analytics accounts, no ad platforms, no BigQuery, no CRM, no website. If a question needs your numbers, the assistant has to say so and answer only the general part.
• No writes. Every tool is read-only. The connector cannot create, change or delete anything — in the knowledge base or anywhere else.
• No access beyond your grants. Content you are not entitled to is invisible, not merely locked.

Data handling

The connector reads Witbee's own published content and returns it to the assistant you connected. What your assistant then does with that text is governed by the client you use.

Requests are authorized per user and scoped to that user's entitlements. The server holds no copy of your conversations, prompts or assistant output — it answers a tool call and returns knowledge-base content.

See the Privacy Policy.

Support

Questions, access problems or a document that should be there and is not: contact@witbee.com.