> ## Documentation Index > Fetch the complete documentation index at: https://docs.maverickintelligence.co/llms.txt > Use this file to discover all available pages before exploring further. # Claude Connector > Connect Maverick Intelligence to Claude so you can ask about your website visitors in plain language # Claude Connector The Maverick Intelligence connector lets Claude read your identified website visitors — and, if you allow it, push them into HubSpot and adjust your hot-lead settings — without you leaving the conversation. Ask things like: * *"Who visited our pricing page this week?"* * *"Any hot leads from fintech companies in the last few days?"* * *"Has anyone from Acme been on the site? Show me their journey."* * *"Push that person into HubSpot."* **Connector URL** ``` https://mcp.maverickintelligence.co/mcp ``` It is a remote [MCP](https://modelcontextprotocol.io) server over Streamable HTTP, so it also works with any other MCP-compatible client. *** ## Add the connector to Claude **Pro and Max plans** 1. Go to **Settings › Connectors** 2. Click **Add custom connector** 3. Paste `https://mcp.maverickintelligence.co/mcp` 4. Click **Add**, then **Connect** 5. Sign in with your Maverick email — we'll send you a link, no password needed 6. Review the permissions and click **Allow access** **Team and Enterprise plans** An owner adds the connector once for the whole organization under **Organization settings › Connectors › Add › Custom**. Each member then connects individually from **Settings › Connectors**, signing in with their own Maverick email. Everyone sees only the data their own Maverick account can see. ```bash theme={null} claude mcp add --transport http maverick https://mcp.maverickintelligence.co/mcp ``` Run `/mcp` inside Claude Code to complete the sign-in. Claude Code opens a browser for the same email link and consent screen. To use an API key instead of signing in: ```bash theme={null} claude mcp add --transport http maverick \ https://mcp.maverickintelligence.co/mcp \ --header "X-API-Key: mk_live_your_key_here" ``` Point any MCP client at `https://mcp.maverickintelligence.co/mcp` using the Streamable HTTP transport. The server implements OAuth 2.1 with Dynamic Client Registration ([RFC 7591](https://www.rfc-editor.org/rfc/rfc7591)) and Client ID Metadata Documents, so most clients discover and complete the flow with no manual configuration. Discovery starts from the `WWW-Authenticate` header on the 401: ``` GET /.well-known/oauth-protected-resource GET /.well-known/oauth-authorization-server ``` Clients that cannot do OAuth may instead send `X-API-Key: mk_live_...`. *** ## What Claude can do Every tool is scoped to the account you sign in with, and the connector can only ever see what that account can see in the dashboard. ### Reading visitors | Ask about | Tool | | --------------------------------- | ------------------------------- | | Anyone on the site recently | `list_visitors` | | Visitors to a specific page | `who_visited_page` | | Qualified prospects | `list_hot_leads` | | People from a named company | `find_visitors_at_company` | | One person in detail | `get_visitor` | | What someone actually looked at | `get_visitor_journey` | | Companies rather than individuals | `list_companies`, `get_company` | | Totals and coverage | `get_account_stats` | | Your hot-lead criteria | `get_hot_lead_criteria` | | Which client sites you track | `list_tracked_clients` | Most site traffic resolves to a **company** even when no individual is identified, so `list_companies` usually returns more than `list_visitors` for the same period. Claude is told this, and will normally mention it rather than report a person-level count as your total traffic. ### Making changes These three tools change live data, so Claude asks you to confirm before using them, and Claude itself will normally check with you first. | Tool | What it does | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `push_visitor_to_hubspot` | Creates or updates the visitor as a contact in your connected HubSpot, with their company, and associates the two. Matches on email and domain, so it updates existing records rather than duplicating them. | | `update_hot_lead_criteria` | Changes the ideal customer profile that decides who counts as a hot lead. Merges with your existing settings — only the criteria you name are changed. Account-wide. | | `exclude_company_domains` | Suppresses visitors from given company domains, for hiding your own staff and known bots. In `replace` mode it removes domains not listed, so Claude will read the current list back to you first. | *** ## Authentication There are two ways to connect. **Signing in is the recommended one.** ### Signing in (OAuth) The default. Claude sends you an email link, you pick your account if your address has more than one, and you approve a list of permissions. Nothing is copied or pasted, access is tied to your own Maverick account, and you can revoke it at any time. Permissions are requested individually: | Permission | Grants | | ---------------- | -------------------------------------------------- | | `read:visitors` | See the people and companies visiting your website | | `write:crm` | Push visitors into your connected HubSpot | | `write:settings` | Change hot-lead criteria and excluded domains | | `offline_access` | Stay connected without signing in again | Access tokens last one hour and refresh automatically in the background. ### API key For automation, or clients that cannot do OAuth, send your existing Developer API key as an `X-API-Key` header. See [Authentication](/authentication) for how to create one. **API keys are read-only for the connector by default.** Your `mk_live_` keys were issued for a read-only REST API, so the connector will not let one write to your HubSpot or change your settings — a key you created for reporting cannot be turned into a key that edits your CRM just because it was pasted somewhere new. Write access for a specific key is enabled per key by Maverick support — contact us if you need it for an automation. For anything interactive, sign in with OAuth instead. ### Agencies and partners If you hold a **domain-scoped** API key — one restricted to particular client sites — the connector honours that restriction on every tool. Visitors outside your scope are not returned, and are reported as "not found" rather than as "not allowed", so the connector cannot be used to discover which other clients exist. Use `list_tracked_clients` to see the sites available to your credential, then pass `domain` or `client_ref` to any read tool to narrow further. OAuth connections are account-wide, so use a scoped API key when you need a per-client boundary. *** ## Limits | | | | --------------- | ------------------------------------------------------------------------------------------------------- | | Rate limit | 1,000 requests per hour, shared with the REST API. Domain-scoped keys get their own separate allowance. | | Rows per call | 100 maximum, 25 by default. Claude pages automatically when it needs more. | | Result size | Large results are truncated with a note telling Claude to narrow the query. | | Request timeout | 29 seconds. Broad queries over large accounts return a partial page plus a cursor rather than failing. | *** ## Privacy and safety * **Claude sees only what your account sees.** Excluded domains, excluded paths and suppressed visitors stay hidden. * **Write tools ask first.** Claude confirms before touching your CRM or settings, and your MCP client prompts for approval too. * **You can block individual tools.** In Claude, open the connector under **Settings › Connectors** and set any tool's permission to **Blocked** — a good way to allow reads while ruling out writes entirely. * **Disconnect at any time** by removing the connector in Claude, or by revoking the API key in your dashboard. Access tokens are short-lived and expire within an hour of last use. * **Tool arguments are not logged.** Request logs record which tools ran, not the page paths or company names you asked about. *** ## Troubleshooting Check the URL includes the `/mcp` path — `https://mcp.maverickintelligence.co/mcp`, not the bare domain. The path is part of the server's identity, and a token issued for the bare domain will not be accepted. Links are single-use and expire after 15 minutes. They are also tied to the specific connection attempt that created them, so a link from an earlier attempt will not work — start again from Claude and use the newest email. Use the email address you sign in to the dashboard with. Any of your account's registered addresses works, including secondary contacts. If you have just been added to an account, ask the account owner to confirm your address was saved. Either you connected with an API key (read-only by default — see the warning above), or you approved only the read permission when signing in. Remove the connector in Claude and add it again to be re-prompted for the full set. Two likely reasons. Read tools default to 25 rows — ask for more and Claude will page. And many visits resolve to a company without identifying a person; ask about companies to see the fuller picture. The connector shares the 1,000 requests/hour limit with the REST API. A long analysis session can consume it. The limit resets on the hour.