Claude Desktop Setup Guide for Ace MCP

Part of Model Context Protocol for Real Estate

Install the Ace DXT extension in Claude Desktop, paste a revocable signed MCP token, and connect to the production Follow Up Ace endpoint with tools scoped to your role and entitlements.

What You Need Before Starting

You need Claude Desktop, an active Ace Pro seat connected to Follow Up Boss, and a signed MCP token generated under Follow Up Ace Settings → Integrations → MCP. You do not enter a Follow Up Boss password into the extension. Treat the token like a password: do not send it in chat, screenshots, tickets, or URLs, and revoke it if a device is lost or shared.

Installing the Ace DXT Extension

In Follow Up Ace, open Settings → Integrations → MCP and download followupace-crm-v1.2.0.dxt. In Claude Desktop, open Settings → Extensions, choose Install Extension, and select the downloaded file. Review the network and CRM-data permissions before approving the extension. The package is a thin local proxy to the same production connector used by the web clients; it does not contain your Follow Up Boss API key.

Configure the Signed MCP Token

When Claude Desktop opens the extension settings, paste the signed token into FollowUpAce MCP Token. Leave MCP Server URL set to https://followupace.com/api/mcp. The token is sent only as an Authorization header to that HTTPS endpoint; never append it to the URL. Save the configuration and restart the extension if Claude requests it. The production server rechecks the token, Ace entitlement, FUB role, and tool scope on requests.

Testing Your Connection

Start a new conversation and ask a read-only question such as 'Show me my most recent lead in Follow Up Boss.' Confirm the result matches the records and permissions you see in FUB before trying any write. If setup fails, verify the MCP Server URL is exactly https://followupace.com/api/mcp, the signed MCP token is current and unmodified, the Ace Pro seat is active, and the account still has a live FUB connection. Revoke and replace the token rather than sharing it with support.

What You Can Do Now

The DXT proxies the live production tool registry rather than shipping a separate hard-coded tool list. What Claude receives is scoped to your authenticated FUB role, Ace seat, and enabled entitlements. Start with read-only workflows, review tool confirmations and returned record IDs, and verify consequential changes in Follow Up Boss. Reconnect after a server metadata update if Claude is still showing an older tool snapshot.

Frequently Asked Questions

Does the DXT extension slow down Claude Desktop?

No. The extension only activates when Claude needs to access your CRM data. It does not run in the background or consume resources when you are using Claude for non-CRM tasks. You can use Claude Desktop for general AI conversations and the Ace tools only engage when your request involves Follow Up Boss data.

Can I use the same Ace account on multiple computers?

Install the same DXT package on each supported computer, but use a freshly generated signed MCP token where the Ace settings allow it and never copy a token through chat or email. Revoke outstanding MCP sessions when retiring, losing, or sharing a device.

What if Claude Desktop updates — do I need to reinstall the extension?

Routine Claude Desktop updates normally preserve installed extensions, but verify the installed Follow Up Ace version and run a read-only test after either Claude or the extension changes. Install a newer DXT package when Follow Up Ace publishes one; do not assume the local package updates itself.

Ready to automate your Follow Up Boss CRM?

Start free. No credit card required. 189 AI tools at your fingertips.

Get Started Free