Using Ace's Tools from Claude or ChatGPT

Connecting Ace to Claude or ChatGPT gives those assistants direct, permissioned access to your Follow Up Boss data and to Ace's own intelligence — up to 193 role-scoped tools on one connector URL. This article explains what that number is, why the number you see may be smaller, and what Ace will and won't do on your behalf.

What you'll have when you're done

• Claude or ChatGPT able to read and write your Follow Up Boss data and call Ace’s own intelligence, on one connector URL.
• A tool list scoped to who you are — an agent seat cannot reach team-wide reporting by asking cleverly.
• The exact count for your account, read off the live connector rather than a written list.
• Confidence that nothing reaches a client without an explicit confirm.

Your first win, in about 5 minutes

You need an Ace Pro seat of your own — an Ace seat can use Ace inside Follow Up Boss and the Companion but not the connector. Setup itself lives in the linked MCP article; this is the five minutes after it.

1. Open Manage → Integrations in the admin dashboard. It shows your exact server URL, whether your own sign-in email can connect (and, if not, why), when the account last used the connector, and every tool your account can currently call — generated from the live connector.
2. Add the connector in Claude or ChatGPT using that URL and sign in.
3. Ask it something read-only first: "What’s my speed-to-lead looking like this week?"
4. Now ask it to reach out to someone. Watch it come back with a draft and a confirm step instead of sending. That is the normal contract — outreach starts as a draft, and an explicit send path still requires confirm=true on the exact reviewed content.
5. If you are on ChatGPT and see only a couple of actions, remove the connector, add it again and re-authorize — ChatGPT caches the action list and does not refresh it. Claude always receives the full list.

For the step-by-step setup (server URL, sign-in, per-conversation enabling), see Connecting Ace to Claude, ChatGPT & Other AI Tools (MCP). This article is about what you get once you're connected.

Who can connect

The connector requires one exact active tenant seat, an active account, and Ace Pro entitlement — the seat you sign in with must itself be on Ace Pro (account admins are no exception — an admin needs an Ace Pro seat too; your team's other Pro seats never cover you). Sign-in is bound to that one Follow Up Boss account-and-user seat and is re-checked on every call. A platform admin who does not also hold an active seat in that tenant cannot authorize the customer connector. An Ace seat can use Ace inside Follow Up Boss and the Companion, but not the connector. If sign-in fails with a Pro-license message, that's the gate.

The tool count, honestly

There is one customer-facing surface and it carries up to 193 role-scoped tools. Other figures circulate, and none of them counts your own tools:

• 193 — the production customer connector ceiling. This is what Claude, ChatGPT, Claude Desktop, and the downloadable Ace desktop extension all talk to. The desktop extension is a thin proxy to the same connector, so installing it does not get you a bigger tool set.
• The standalone developer package. A local, self-hosted build used for development has its own, larger catalog. It is not the customer path and is not what your Claude connector uses.
• Any other figure you find in older material — 122, 170+, 183, 187, 189, 192, 227 — is stale. The current ceiling for the production customer connector is 193.

Why your number may be smaller than 193

Ace scopes the tool list to who you are. The assistant is only shown the tools you're entitled to, and every call is re-checked when it runs — so a tool that isn't yours can't be reached by asking cleverly.

The seatless-admin row is a catalog-filtering reference, not a connectable customer session: authorization always requires an exact active tenant seat. The counts are still shown so engineering and support can distinguish role filtering from the login gate.

Two things move the number:

• Team-wide vs. your own book. Cross-agent tools — team leaderboards, account-wide revenue at risk, peer benchmarks, the engine brief — are admin-only. An agent seat sees its own contacts, deals, and performance instead.
• Ace Trove. Exactly 14 tools carry the Trove gate: ace_engine_brief, get_team_cockpit, ace_my_commissions, ace_back_office_ledger, ace_team_retention, ace_you_vs_market, ace_revenue_guard_summary, ace_autopilot_status, ace_my_transactions, ace_transaction_room, ace_transaction_ask, ace_transactions_board, ace_lookup_property, and ace_contact_seller_intent. Without Trove, an entitled caller sees a clear "Ace Trove not enabled" message rather than a wrong answer. Ace Smart List planning and deployment are admin-scoped, not Trove-gated; deployment has its own explicit preview-and-confirm requirement.

What the tools cover

• Your CRM. People, notes, calls, texts, emails, tasks, appointments, deals, pipelines and stages, templates, tags, users, and global search — read and write.
• Ace intelligence. Contact scores and person intelligence, the NOW view, next-action recommendations, at-risk deals, pipeline movement, speed-to-lead status, conversion funnel, source ROI, and the daily brief.
• Your client tools. Lead magnets and their leads, forms and their leads, client packets and packet leads, Ace Page leads and status, the cross-silo Capture inbox, your ambassadors and referral pipeline, the Home Almanac homes you've enrolled, and your transactions.
• Market and compliance. Mortgage math, property lookup, seller-intent signals, economic and housing data, and a compliance scan for message drafts.
• Memory. Ace remembers facts you tell it about a contact or about your own practice, and you can ask it to recall or forget them.

Nothing sends without you

This is the part worth reading twice. Most client-outreach tools draft first. The two explicit send paths — sendEmail and the approved-draft sender — can deliver, but only when that exact call carries confirm=true after you review it. sendEmail also gets a final server-side compliance scan; if the safe draft changes, nothing is sent until you review and confirm the changed subject and body. A normal request to "reach out" still returns a draft rather than delivering on the strength of the request alone. The value-touch tool for your referral sphere follows the same draft-then-confirm contract.

The same posture applies elsewhere: deploying Smart Lists into Follow Up Boss shows you a preview unless you explicitly confirm, and estimates are labeled. If a tool reports a dollar figure or an equity number, it carries "(est.)" because it is modeled from your account's own history and 30+ third-party data sources — not observed lien or appraisal data.

Permissions, reconnection, and switching accounts

The connector uses your exact active Follow Up Boss account-and-user seat. Ace checks that seat, account, role, session, and Pro access again when a call runs. The connector needs the seat you sign in with to be on Ace Pro — account admins included, since an admin needs an Ace Pro seat too. Ace Pro seats your team bought for other people don't extend to your seat, and an Ace seat is turned away at sign-in. If a billed Ace Pro seat is moved down to Ace, the connector keeps working until the end of the Ace Pro period that was already paid for. Team reporting still requires the caller's own admin role, and Trove tools still require Trove.

On the authorization screen, review the requested permissions. A read-only connection can answer questions but cannot change records or send. Reconnect and approve write access if you want those tools. Reauthorizing with another account does not upgrade the old account's connection: remove the old connector and sign in to the intended seat.

Access renews automatically while the client supports refresh and the seat remains eligible. If renewal fails after a seat move, deactivation, revoked session, or plan change, check the seat and reconnect. If you see a Follow Up Boss connection error, reconnect your own Follow Up Boss identity in Ace. An agent cannot borrow the account owner's credential to bypass a missing personal connection.

Before an outbound email, sequence enrollment, destructive change, contact edit, appointment change, or tag update, review the affected records and exact content and explicitly confirm the action. Write permission alone is not that confirmation. If the final email compliance check changes the draft, review and confirm the new version before it can send.

Revoking access

You can disconnect at any time:

• From the client: remove the connector in Claude or ChatGPT settings.
• From Ace: the Integrations page can revoke your connector session. Revoking signs out every outstanding connection for that user immediately, not at the next token expiry — use it if a laptop goes missing.
• By seat: deactivating a seat cuts off its connector access on the next call, even if that person still holds an old token.

Frequently asked questions

Does the desktop extension give me more tools than the web connector?
No. It proxies to the same connector and serves the same 193.

ChatGPT only shows me a couple of actions — is that the same 193?
ChatGPT reads the action list when the connector is added and doesn't refresh it afterward. Remove the connector, add it again, and re-authorize. This affects ChatGPT only; Claude and other clients always receive the full list.

Can an agent use the connector to see the whole team's numbers?
No. Team-wide tools are admin-scoped in the list, every tool call is re-checked against the caller's exact live tenant seat, and each backing team-wide surface verifies the live role again before returning anything.

Do I need Ace Trove to use the connector?
No. Trove unlocks a specific set of account-wide tools; the rest work on a Pro seat alone.

Related articles

• Connecting Ace to Claude, ChatGPT & Other AI Tools (MCP)
• Cheat Sheet: Ace MCP + Claude
• What Ace Reads, Writes, and Syncs in Follow Up Boss

Last updated: October 2026