Connect your ZenLink account to your AI assistant.

Use the same login you use for ZenLink. It takes about a minute. Your assistant gets the tools your role already has in the app, and nothing more.

Add ZenLink to your assistant.

You need a ZenLink login first, the one you use for the app or the web. StoneLink staff: if you haven’t been set up yet, ask your ZenHome coordinator before connecting. The connector can’t create an account.

  1. 1

    Start on a computer

    Use the Claude desktop app or claude.ai in a browser. The Claude phone app can’t add a new connector yet. Once it’s set up here, it shows up on your phone by itself.

  2. 2

    Add ZenHome

    Open Connectors, click the + (or “Browse”) in the top right, choose “Add custom connector,” and paste the address below. It won’t be in the list already: ZenHome is a custom connector, so you add it by address. Not Settings → Developer: that screen is for servers on your own computer.

    Open Claude’s connectors
  3. 3

    Sign in to ZenHome

    Claude hands you to ZenHome to approve. Use the phone or email on your account and the 6-digit code we send, or Google, Microsoft or Apple if that’s how you sign in. No password to make up.

  4. 4

    Ask your first question

    Back in Claude, ZenHome shows as connected. Ask it to plan a project or check on one.

On a Team or Enterprise plan, an Owner enables it once for everyone: add it org-wide. Everyone still signs in as themselves.

Connecting to Claude · Connectors → + / Browse → Add custom connector → paste https://zenhome.ai/api/mcp

From a coding agent (Claude Code, Cursor, Codex)

Same address, same sign-in. Add it as a remote MCP server and sign in in the browser window it opens. Claude Code, for example:

claude mcp add -t http zenlink function(){throw Error("Attempted to call MCP_URL() from the server but MCP_URL is on the client. It's not possible to invoke a client function from the server, it can only be rendered as a Component or passed to props of a Client Component.")}

Then run /mcp and pick ZenLink to sign in. Cursor and Codex take the same URL in their MCP settings.

Your role decides what it can do.

There’s nothing to set up. When you sign in, ZenLink gives your assistant the tools your account already has in the app.

  • ZenHome coordinators

    52 tools

    Find, read, price, schedule, assign, text techs and customers, read checkups, file records.

    Try asking

    Which of Thursday’s jobs have no tech yet, and who’s free?

  • StoneLink coordinators

    20 tools

    Look up every StoneLink job, checkup, estimate and property. Draft estimates at the rate on file, add job photos, and book or staff visits on your own jobs once you approve each one. Messages and checkup edits stay in the app.

    Try asking

    What did this turnover’s checkup find, and what’s tenant-caused?

  • Field techs

    6 tools

    Pull up the job, find the next one, add photos, log what happened, ask for a visit, message the customer through the office. Only your assigned jobs.

    Open this page from Connect your AI on the Profile tab of the phone app.

    Try asking

    What’s the scope on my 1pm, and is there a gate code?

Coordinators: a message waits for your approval in ZenLink.

  1. You ask

    For example, “Text both customers with times.”

  2. It files a card

    The exact message, as an approval card in ZenLink. Nothing is sent yet.

  3. You read it, then approve

    From the link it gives you. This is the step that matters.

  4. It sends

    Right after it’s approved.

Sending a quote, an invoice or a balance request works the same way: one card, nothing out until it’s approved. Email to customers waits until ZenLink can send it, so ask for a text. Invoice corrections, refunds and new logins stay in the app, where someone is looking at the page.

Setup detail, sign-in snags, and every tool by role are on the documentation page.