AI Access

Local Wrangler runs an MCP server, so an AI assistant such as Claude, Cursor or Windsurf can query this account directly in conversation. You ask in plain language, the assistant picks the right tool, and the answer comes from your real data rather than from a guess.

It is read only. A connected assistant can look at 8 tools covering leads, traffic, attribution and calls. It cannot change a lead, delete anything, send a message, or reach another account.

Endpoint

https://app.localwrangler.com/api/mcp

Authentication

Every request carries the token you created in Settings, AI Access. A header is the better way, because a query string is written to the logs of every proxy it passes through. Both work, for clients that cannot set headers.

Authorization: Bearer YOUR_TOKEN

https://app.localwrangler.com/api/mcp?token=YOUR_TOKEN

Getting a token

1. 1
   Open Settings, AI Access and find Need a token.
2. 2
   Give the connection a name you will recognise later, such as the device it runs on.
3. 3
   Decide whether it may read call and chat transcripts. This is off unless you turn it on.
4. 4
   Click Create connection, then copy the token straight into your AI client.

Owners and admins can create and disconnect connections. A connection reads the whole account, so it takes the same standing as inviting a colleague. Everyone on the team can see which connections exist and when each was last used.

Connect your AI client

Pick the client you use and replace YOUR_TOKEN with the token you copied. The same blocks are on the Settings screen, with a copy button.

{
  "mcpServers": {
    "local-wrangler": {
      "type": "streamable-http",
      "url": "https://app.localwrangler.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

claude mcp add --transport http local-wrangler https://app.localwrangler.com/api/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

{
  "mcpServers": {
    "local-wrangler": {
      "url": "https://app.localwrangler.com/api/mcp",
      "transport": "streamable-http",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

{
  "mcpServers": {
    "local-wrangler": {
      "serverUrl": "https://app.localwrangler.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

{
  "servers": {
    "local-wrangler": {
      "type": "http",
      "url": "https://app.localwrangler.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

{
  "name": "local-wrangler",
  "transport": "streamable-http",
  "url": "https://app.localwrangler.com/api/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_TOKEN"
  }
}

Available tools

You do not call these yourself. You ask a question and the assistant picks the tool, often several in a row. They are listed so you know what it can and cannot see.

Dates and time zones

Ask for a period in plain language and your assistant works out the dates. Two things are worth knowing, because they decide whether a number matches the one on your screen.

• Days are counted in UTC unless your assistant passes your time zone. If it does not, a lead that arrived late in the evening can be counted on the following day. Telling your assistant your city once, at the start of a conversation, is enough.
• Any comparison against the period before covers the same elapsed portion. Half way through today, it compares against half of the equivalent earlier day, so a normal day never looks like a collapse.

Call and chat transcripts

Off unless you switch them on for a connection, because the words in a transcript are your customers', not yours. With the switch off, the assistant still gets the AI written summary of a call, its sentiment and its qualification, so you can ask which calls went badly without the conversation itself leaving your account.

What a connection can never reach

• Call recordings and audio files
• Passwords, API keys, or the secrets behind your integrations
• Anything belonging to another account

Disconnecting

Click Disconnect beside a connection and confirm. It stops working on the next request. The row stays in the list, marked as disconnected, so you keep the record of what was connected and when it was cut off.