Getting started
Connect ClaraT to your own Claude and ask your first questions. ClaraT is both the connector you add to Claude and the assistant you then talk to.
What ClaraT is
- ClaraT, in your Claude. Connect ClaraT to claude.ai, the Claude desktop app or Claude Code, and Claude becomes ClaraT: it knows how SearchLight works, which numbers mean what, and how to read your accounts, because it reads SearchLight's knowledge base before it answers and reaches your data through SearchLight's own API and services.
- Signed in as you. There is no separate ClaraT account. ClaraT signs you in with your SearchLight login and makes every call as you. What you can reach in the app is what ClaraT reaches for you, nothing more and nothing less. An administrator sees what an administrator sees; a user on one account sees that account.
- Live, never a copy. ClaraT holds no data of its own. Each answer is read from the platform at the moment you ask, the same reconciled numbers the app shows, and nothing is cached or kept in between.
- It learns. When ClaraT works something out in a conversation, a definition, a method, a fix, it saves the lesson to the knowledge base so the next person, or the next session, starts further along. What it saves is scoped to you, to your organization, or to everyone, depending on what the lesson holds (see What ClaraT saves, and who sees it).
Who can connect
Anyone with a SearchLight user account. There is no enrollment, no pilot list and no separate ClaraT credential: a valid SearchLight sign-in is the whole requirement. A sign-in that has no SearchLight user record is refused with "this SearchLight sign-in has no user record — ask an administrator".
Which Claude plans
Every Claude plan can add a custom connector (a Free plan allows one). On a Team or Enterprise plan an organization owner adds ClaraT once for everyone, and each member then connects with their own SearchLight sign-in; connectors there work in private projects. On an individual plan you add the connector yourself. The Claude mobile apps use the connectors on your account: add ClaraT on the web first.
How to connect
claude.ai and the Claude desktop app
- Add the connector. Customize → Connectors (claude.ai/customize/connectors; the same list in the desktop app) → + Add → Add custom connector. Name it ClaraT. MCP server URL:
https://searchlight.digital/clarat, exactly that:https://, no trailing slash, nothing after/clarat. Leave the other settings as they are and click Add. Or open the prefilled link, Add ClaraT to Claude, and confirm. On a Team or Enterprise plan this step is an organization owner's; members then find ClaraT, labelled Custom, under Customize → Connectors. If it is not listed yet, reload claude.ai, or fully quit and reopen the desktop app. - Connect. Click Connect. SearchLight's sign-in opens, your normal app login; a browser that already has a live SearchLight session goes straight through. Click Allow. That is the whole identity: no Google step, no token to paste.
- Check the tool permissions on ClaraT's connector page (Customize → Connectors → ClaraT → Tool permissions: Always allow, Needs approval or Blocked, per tool or per group). Reads arrive on Needs approval or Always allow. The tools that can write (saving to the knowledge base, calling SearchLight's services with a change) arrive Blocked by Claude's default. Set them to Always allow or Needs approval; Blocked means ClaraT cannot save a learning or make a change until you allow it.
- Start a new chat. A chat opened before the connection does not see it. Ask something that needs SearchLight ("which accounts can I see?") and watch ClaraT answer from the platform.
Claude Code
Add ClaraT as a remote server from a terminal (add --scope user to have it in every project):
claude mcp add --transport http clarat https://searchlight.digital/clarat
Then sign in: in a session, /mcp → clarat → Authenticate, and finish the SearchLight sign-in in the browser (or claude mcp login clarat from the shell). A session opened after the connect sees ClaraT's tools. If Claude Code is signed in with your claude.ai account, a connector added on claude.ai appears in Claude Code by itself.
Who am I connected as?
Ask ClaraT "who am I signed in as". It reads your identity from the platform and answers with your user and whether you are an administrator. If that read is refused, the connection needs to be made again (see When something changes).
Troubleshooting the connection
| What you see | What it means and what to do |
|---|---|
| ClaraT is not in the connector list after it was added | Reload claude.ai, or fully quit and reopen the desktop app. On a Team or Enterprise plan the connector is added by an organization owner; a member's Add custom connector button says "Ask an organization owner to add this for your team". |
| The sign-in fails, or answers "this SearchLight sign-in has no user record — ask an administrator" | Sign in with the login you use in the SearchLight app. That message means the login has no SearchLight user account; whoever manages users for your organization adds you, and the connect then goes through. |
| ClaraT says a call was unauthorized, or every call fails | The key on the connection is no longer accepted, usually because it was rotated or deleted under Settings → API in the app. On the connector's page Disconnect, then Connect (the sign-in runs again), and start a new chat. |
| ClaraT does not see the connector, or answers from an old state | The chat was opened before the connection, or before a change to it. Start a new chat; older chats keep the state they opened with. |
| ClaraT says it cannot save a learning or make a change | That tool is Blocked under the connector's Tool permissions (Claude's default for tools that can write). Set it to Needs approval or Always allow, then start a new chat. |
| An account you expected is missing | Ask "which accounts can I see?". ClaraT reaches exactly what your SearchLight login reaches in the app, so a missing account is a missing grant on your user: whoever manages users for your organization adds it, and ClaraT sees it on the next ask, no reconnect needed. |
| A tool ClaraT names is missing after a release | On the connector's page, ⋮ beside Disconnect → Refresh tools list, check the write tools' permissions again, start a new chat. |
| "The platform did not answer within 25 seconds" | The ask was too big for one call. Narrow it: a shorter range, fewer fields, one organization. |
| ClaraT cannot read a PDF or Word file reached through a connector | Binary files do not render through connectors. Attach the file to the chat instead. |
How to use ClaraT
Ask in plain English. ClaraT works out which SearchLight door answers the question, reads the knowledge base for the rules that apply, makes the calls as you, and explains the answer in your terms. Some things to ask:
- Your numbers. "Spend, leads, booked jobs, revenue and ROAS by channel for last month", for an organization, split by account, in one ask. Trends by week or month. The latest AI insights for an account. Down to the individual lead or call, with its summary and transcript where SearchLight holds one.
- Your accounts. Which accounts you can see; how an account is configured; whether a CRM, call-tracking or ad-platform connection is erroring; what RevSync or Lead Grading is doing for an account.
- Definitions and method. What a metric means, why two reports show different spend, how attribution decides a lead's channel, what a lead grade is. ClaraT answers from the same knowledge base SearchLight's own team uses.
- Your platforms, live. For any account you reach that has a Google Ads, Microsoft Advertising, Facebook, ServiceTitan or FieldRoutes connection, ClaraT can call that platform's API directly on the account's own connection (campaign settings, budgets, ads and their landing pages, a ServiceTitan job or customer, a FieldRoutes appointment) and bring back the platform's own answer. Nothing to set up: the connection SearchLight already holds is the one ClaraT uses, and no key or token is ever shown. Reads only: the proxies pass no call that would change anything at the provider.
- Your cached data. Everything SearchLight has pulled for your accounts (call records, ad metrics, CRM activity), listed and readable by what you reach.
Starter prompts by role
Most people do not know what to ask on day one. These are asks ClaraT answers today, in the words people use; copy one and change the names and dates.
If you own or run the business
- "How did my marketing do last month: spend, leads, booked jobs, revenue and ROAS by channel?"
- "Why doesn't my Google Ads spend match what SearchLight shows?"
- "Which of my connections are broken or erroring right now?"
- "What are the latest insights for my account, and what should I do about them?"
- "Show me last week's leads with their call summaries. Which ones booked?"
- "What does a lead grade mean, and how are my leads graded?"
If you run several accounts (an agency or a multi-location business)
- "Which accounts can I see?"
- "For my organization, spend, leads and ROAS by account for last month."
- "Which of my accounts have a CRM, call-tracking or ad-platform connection erroring?"
- "Booked jobs by week for the last eight weeks, split by account."
- "How is the Springfield account configured: which CRM, which call tracking, what is RevSync doing for it?"
- "What is the daily budget on each of the Springfield account's Google Ads campaigns?"
Getting good answers
- Start a fresh chat after connecting, and after any change to the connector. Older chats keep the state they opened with.
- One organization per ask, split by account. ClaraT reaches everything you reach, but a question is clearest at one organization.
- Long ranges come by month, week or day. The platform computes a window of up to 90 days as one total; a longer range is read in buckets, and the buckets never sum to an exact whole-range total. Ask for the range whole when you want the total.
- Grading metrics in their own question. Lead-grade counts asked beside lead counts distort the lead counts. ClaraT knows this and separates them; if you ask for both at once, expect two reads.
- Check a number that matters. Ask ClaraT how it got it: the door, the parameters, the range. The numbers are the platform's; the reading of them is ClaraT's, informed analysis rather than a guarantee.
- Other connectors work beside ClaraT in the same conversation (your Google Drive, Gmail or Slack, a weather connector), and Claude joins the answers. Binary files (PDF, Word) reached through a connector do not render; attach the file to the chat instead.
Getting help
Ask ClaraT first. "How do I…" questions are what the knowledge base is for, and when it has no answer ClaraT works it out from the platform and saves what it learned. For anything about your account or access, contact support as today.