Which queries lost clicks this week, and which pages drove them?
Your agent runs Search Console and Google Analytics and writes the brief. The brief names the page and the query.
SingleBrain Gateway gives the assistant you already use one key to your own marketing accounts. Ask which pages lost traffic this week, and it pulls Google Analytics and Search Console and writes the answer in Claude, ChatGPT, or Cursor.
Free to start. Accounts you connect are not charged, and a new organization includes $5 in credits for paid tools.
Works with Claude, ChatGPT, and Cursor.
Connects to Google Analytics, Search Console, Google Sheets, Slack, HubSpot, Stripe, Gong, Coda, Asana, OpenAI, and Perplexity.
The weekly question usually starts in Slack or a doc. Someone still has to open Google Analytics and Search Console and pull the numbers by hand.
Your agent runs Search Console and Google Analytics and writes the brief. The brief names the page and the query.
Your agent reads the HubSpot deals that changed and the Gong calls about those deals, then writes the summary in the chat where you asked.
"How did sessions look last week, and which deals moved?"
Sessions are up, and the pipeline moved with it. The lift is one creative.
Example only. Not customer data.
Google Analytics, Search Console, Slack, HubSpot, and the other tools on this page. You use your own login, and you can revoke it any time.
Paste it into Claude, ChatGPT, or Cursor. It reaches only the accounts you connected.
The agent calls the tools and writes the answer. Every call shows up in your activity log.
OAuth, refresh, and revocation, handled. You grant access, and you can revoke it.
An agent sees tools for the accounts you connected. Nothing else is listed.
One endpoint for Claude, ChatGPT, and Cursor. Plain HTTP for everything else. No SDK to adopt.
claude mcp add singlebrain \ --url https://gateway.singlebrain.com/mcp curl https://gateway.singlebrain.com/api/data/google/properties \ -H "Authorization: Bearer $KEY"
Each organization is separated in Postgres. A query for another organization's accounts returns nothing.
Only the accounts your organization connected, and only the access you granted. Accounts you did not connect are not listed.
We store the encrypted credential and a short record of each call: who asked, which service, and what kind of request. We do not store the data that came back.
No. Each organization is its own tenant. Row-level security in Postgres refuses a cross-organization query, and the application connects as a role that cannot bypass it and has no schema rights. Credentials are encrypted with AES-256-GCM, bound to the organization and the service. SOC 2 is in progress. The tests run against a real database as both roles.
Mention the assistant in Slack and it replies in that thread. That reply does not pull your other accounts. The key you paste into Claude, ChatGPT, or Cursor can read Slack. It does not post, upload files, or add reactions.
Single Grain sells managed revenue agents. The Gateway is how one reaches your accounts. This site is shared, and each organization is separated in the database. A dedicated deployment runs on infrastructure nobody else shares, for agents that act and not only read.
Connect an account, take a key, and ask the question in the agent you already use.
gateway.singlebrain.com