> ## Documentation Index
> Fetch the complete documentation index at: https://api.lawtte.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Claude, Grok Bot or any MCP client

> Plug Claude, Grok Bot, Claude Code, Cursor or any MCP client into Lawtte's Agent Builder, then build, launch and change your firm's agents just by talking.

Your Agent Builder doesn't have to live in one browser tab. Connect the AI you
already talk to all day, and it gets the keys to the same builder: it can see your
agents, draft new ones, launch them in Test mode, take them live, and tidy them up.

Everything it builds shows up in your dashboard with a little tag, like
**via Claude**, **via Grok Bot** or **via Cursor (MCP)**, so you always know who
made what.

> [card] The one thing you need
>
> ```
> https://www.lawtte.ai/api/mcp
> ```
>
> It's also on **Settings → Developers → MCP** in your dashboard, with a Copy button.

## Pick your AI

> [tab] Claude
>
> **1. Add a custom connector**
>
> In Claude, open **Settings → Connectors → Add custom connector**. Name it
> **Lawtte** and paste the server address. Leave advanced settings empty.
>
> **2. Sign in**
>
> Claude shows a connect card the first time it needs your account. Sign in to
> Lawtte and pick your firm.
>
> **3. Say hi**
>
> > What agents does my firm have?
>
> More detail: [Connect Claude](https://api.lawtte.ai/mcp/connect-claude.md).

> [tab] Grok Bot
>
> **1. Add the server**
>
> In a Grok Bot chat, ask **"Add the Lawtte connector"**, or add a custom MCP
> server in settings and paste the address.
>
> **2. Sign in**
>
> Approve access for your firm when the connect card appears.
>
> **3. Say hi**
>
> > Show me which of our agents are live and which are still in Test mode.
>
> More detail: [Connect Grok Bot](https://api.lawtte.ai/mcp/connect-grok-bot.md).

> [tab] Claude Code
>
> One line in your terminal:
>
> ```bash theme={null}
> claude mcp add --transport http lawtte https://www.lawtte.ai/api/mcp
> ```
>
> Then run `/mcp` inside Claude Code and choose **lawtte** to sign in.

> [tab] Cursor, VS Code and others
>
> Any client that speaks MCP over streamable HTTP works. Most take a URL:
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "lawtte": { "url": "https://www.lawtte.ai/api/mcp" }
>   }
> }
> ```
>
> If your client supports OAuth, it signs you in like Claude does. If it can't,
> create a key under **Settings → Developers → API key** and send it as a header:
>
> ```http theme={null}
> Authorization: Bearer lawtte_sk_YOUR_KEY
> ```
>
> Stdio-only clients can use `mcp-remote`; see [Claude Desktop](https://api.lawtte.ai/mcp/claude-desktop.md)
> for the exact config. Builds made with a key show as **via Lawtte MCP**.

> [!NOTE]
>
> Firms whose agents Lawtte runs for them connect once Lawtte switches the connector
> on. If the MCP page says it isn't on yet, ask your Lawtte account team.

## Your first five minutes

Try these in order. Each one is a real thing your AI can do now.

> [accordion] 1. Take the tour
>
> > What agents do we have, and what tools and inboxes are connected?
>
> It reads your agents, the systems you've connected (Clio, GHL, Slack…), your
> inboxes and text lines, and your house rules.

> [accordion] 2. Dream one up
>
> > Build an agent that follows up with the manufacturer when we ask for the
> > signed release and they go quiet for 5 business days. Up to 3 reminders,
> > CC Karina.
>
> It drafts the blueprint and the wording. You'll see it in **Agents** right away,
> tagged with your AI's name.

> [accordion] 3. Kick the tires
>
> > Launch it in Test mode and show me what it would pick up from the last two
> > weeks.
>
> Test mode sends nothing. You get a practice run on real emails so you can see
> exactly what it would say, and to whom.

> [accordion] 4. Let it loose
>
> > Looks great. Take it live.
>
> Your AI asks you to confirm first, then it's on and sending by itself.

> [accordion] 5. Tweak it later
>
> > Change the wait to 7 days and pause it over the holidays.
>
> It shows you a before and after for each change, and applies them when you say so.

> [accordion] 6. Teach it your rules
>
> > From now on, never text clients after 7pm, and always CC Karina on
> > manufacturer emails.
>
> It saves these as **house rules**, and every agent it builds after that follows
> them. You'll see them in **Agents → Settings → House rules** too.

> [accordion] 7. Get a number with your name on it
>
> > Get us a 916 number that shows OCONNOR LAW on caller ID.
>
> It sends the request to the Lawtte team, who usually set it up within a business
> day. Then your call agents can use it.

> [accordion] 8. Make the call
>
> > Use the adjuster call agent to call Jane Doe at (916) 555-0142. She agreed to be
> > called and doesn't have her own lawyer.
>
> It checks the call is allowed (consent, calling hours, Do Not Call), asks you to
> confirm, then dials and reports back what it learned.

## The safety rails stay on

Your AI drives, but Lawtte keeps the guardrails:

* **It asks before anything that sends.** Going live, running a live agent, applying
  changes and removing an agent all need your OK in the chat.
* **Test mode first, always.** Every new agent starts there.
* **Calls follow the calling rules.** Consent, calling hours, Do Not Call and daily
  limits are checked by Lawtte on every call, and the chat can't turn them off. See
  [limits and safety](https://api.lawtte.ai/mcp/limits-and-safety.md).
* **It only sees your firm.** One sign-in covers one firm.

## See what it built, or unplug it

Open **Settings → Developers → MCP**. You'll find:

* **Connected apps**, each with a **Disconnect** button. Access ends right away.
* **Built over MCP**: everything your AIs have built, with who asked and the status.

Your agents keep running after you disconnect. Pause them in **Agents** if you want
them stopped too.

> [card] [Writing your own integration, or are you an AI agent?](https://api.lawtte.ai/agent-builder/for-ai-agents.md)
>
> The exact tool order, config formats and rules.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.