Docs · Claude Connector

Connect Loopthink to Claude.

One connector URL gives Claude governed access to every MCP server your workspace has granted you — databases, HubSpot, Salesforce and curated tools, with field-level masking applied before any result reaches the model.

Setup — about two minutes

  1. 1

    In Claude, open Settings → Connectors → Add custom connector.

    Available on claude.ai (web), the desktop apps and mobile.

  2. 2

    Paste the connector URL https://mcp.eu.loopthink.ai/mcp and confirm.

  3. 3

    Sign in with your Loopthink account and, if you belong to several, pick a workspace.

    The connection is scoped to that workspace — reconnect to switch.

  4. 4

    Done. Claude lists every tool your member group was granted — ask away.

Connector URL

https://mcp.eu.loopthink.ai/mcp

Example prompts

Claude discovers your tools automatically. Each enabled table or CRM entity publishes its own tools — these examples exercise different ones:

  • “Which tables can you access, and what do they contain?”

    Uses the discovery tool (listTables / listEntities) — the fastest way to see what a workspace exposes.

  • “List all organisations with their member counts, sorted by creation date.”

    Combines read tools across tables — scan, then join by key.

  • “Look up the order with ID o-2024-1387 and summarize its status history.”

    Uses a get-by-primary-key tool with the table’s real key attributes.

  • “Search HubSpot contacts for “Miller” and show their companies.”

    Uses a CRM search tool — masking rules apply before Claude sees the data.

Authentication

The connector uses OAuth 2.0 with PKCE and dynamic client registration. You sign in with your Loopthink account and pick a workspace; no API keys are shared with the AI client. Tokens are short-lived and refresh automatically.

Governance built in

Claude only sees tools your member group was granted. Field-level masking rules are applied on the server before results reach the model, and every tool is annotated read-only unless writes were enabled explicitly.

Questions or issues? See our privacy policy or contact us via the details in the imprint.