To request access, please have the account admin user contact support@precisefp.com

PreciseFP MCP lets you connect PreciseFP to Claude or ChatGPT, so you can ask questions about your clients, analyze your book, and create accounts or send engagements — in plain language, working on your live PreciseFP data.

Setting it up takes two steps: we enable it for your company, then you add it in your AI tool.

During beta, PreciseFP MCP is enabled per company. Email support@precisefp.com ask to be added to the MCP beta. We’ll turn it on for your company and confirm when you’re ready to go.

You’ll need the PreciseFP MCP address:

That’s it. You’ll now see PreciseFP in your connector list, along with the tools it makes available. You can allow or restrict individual tools from here, and disconnect at any time.

The experience is very similar in both tools. Everything in the rest of this collection works the same way regardless of which one you use.

Start a new chat and ask:

Who am I in PreciseFP?

You should get your own name, role, and team back. If you do, you’re connected.

Another good first question:

What can you do in PreciseFP?

You’ll get a summary of the areas it can reach — accounts, forms and engagements, activities, pipelines, and users.

Your AI tool will ask for approval the first time it uses each PreciseFP capability. You can approve each one as it comes up, or allow them up front from the connector settings.

We’d suggest reviewing these rather than allowing everything at once, particularly the tools that write data — creating accounts, updating profiles, and sending engagements all make real changes in PreciseFP.

Sending an engagement always asks you to confirm first, because it emails a real client a request for personal financial information.

For anyone who wants to know what’s actually happening.

How the connection is authorized. PreciseFP MCP uses OAuth with dynamic client registration, which is why there’s no client ID or secret to copy anywhere. Your AI tool registers itself with PreciseFP automatically at connection time, then you authenticate as yourself in the normal PreciseFP sign-in flow. The AI tool never sees or stores your PreciseFP password.

What it can reach. Every call runs as you — the authenticated advisor — and is confined to your organization. It uses your existing PreciseFP permissions, so it can do exactly what you can do in the web app and nothing more. Archiving an account, converting a prospect, and moving a pipeline stage each require the permission you’d need anyway.

What is permanently blocked. SSNs and equivalent PCI or credential fields are always returned empty on read and rejected on write, regardless of your permissions. There is no configuration that changes this.

Where form data goes. When you send an engagement, the client fills it in on PreciseFP directly. Their answers are never routed through the AI tool.

Which environment you’re connecting to. https://app.precisefp.com/mcp is production — your live data. Use this address; don’t use any other environment URLs you may come across.

Some things stay in the PreciseFP web app:

Do I need a paid Claude or ChatGPT account? You need an account that supports custom connectors. If you don’t see the option to add one, check with whoever administers your AI subscription.

Can my whole team use it? Yes. Each person adds it in their own AI tool and signs in as themselves, once your company has been enabled. Everyone sees only what their PreciseFP permissions allow.

Can I disconnect it? Yes, from your AI tool’s connector settings, at any time. Disconnecting stops all access immediately.

Will it change my data without asking? No. It asks for confirmation before writing, and sending engagements always requires an explicit go-ahead. That said, it can make real changes at scale once approved — read what it proposes before you approve a bulk action.

Why isn’t PreciseFP in the Claude or ChatGPT app directory? We’re still going through those approval processes. The custom connector setup above is how you get access in the meantime.