Wealth MCP
Wealth MCP connects an advisor's Wealth.com book of clients to Claude, so estate and tax questions can be asked in plain language and answered from the client's own records. It is a remote Model Context Protocol server, listed in Claude's connector directory — nothing to install, no URL to paste, and no API key to manage.
Ask who is on your book, what a trust actually says, where an estate plan has gaps, how a client's assets are owned, what a filed return reported, or what a Roth conversion would do against next year's brackets. Every answer is drawn from the client file and carries the source it came from.
| Detail | Value |
|---|---|
| Find it in | Claude's connector directory |
| Server address | https://mcp.wealth.com/mcp |
| Transport | Streamable HTTP |
| Authentication | OAuth 2.0 against identity.wealth.com |
| Tools | 18 — 15 read, 3 write |
| Audience | Wealth.com financial advisors |
Before you start
- An active Wealth.com advisor account. The connector shows you the same clients the web app does — it grants no new access, and client logins and read-only roles cannot use it.
- Wealth MCP on your firm's contract. Access is provisioned per firm. If it is not enabled, the connector will connect and list its tools but every tool call will ask you to contact Wealth.com. See Who can use it.
- A Claude plan that supports connectors.
- Nothing to install, and no API key to manage. You sign in with the Wealth.com credentials you already use.
If your organization manages your device or network, your IT administrator may need to allow connections to
mcp.wealth.com and identity.wealth.com.
Connect it to Claude
1. Open Connectors in Claude
Go to Settings → Connectors, then Browse connectors.
2. Find Wealth.com and connect
Search for Wealth.com in the directory and choose Connect.
On Team and Enterprise plans an administrator enables the connector for the organization first, and members connect to it afterwards. See Team and Enterprise below. If you do not see it, your workspace may not have it enabled yet — on Team plans you can choose Request to notify your administrators.
3. Sign in to Wealth.com
A Wealth.com sign-in window opens. Use your normal credentials, including your usual multi-factor step, then approve the request to let Claude read on your behalf.
4. Ask your first question
Try "List my clients" to confirm the connection, then ask about one of them by name — "What's in the Brady family's estate plan?"
Questions to try
You never name a tool. Claude picks what it needs from what you ask.
- "Who is on my book, and which of them have a trust on file?"
- "What does the Brady family trust say about the successor trustee, and what page is that on?"
- "Where are the gaps in the Brady estate plan?"
- "How is the Brady family's net worth split between them personally and their trusts?"
- "What did the Brady 2024 return report, and what planning opportunities were in it?"
- "What would a $200,000 Roth conversion have cost the Bradys against their 2024 return?"
- "What are the federal brackets and the standard deduction for 2026, married filing jointly?"
Team and Enterprise
An administrator enables Wealth MCP once for the organization, and each member then connects as themselves.
Administrator, once per organization:
- Go to Organization settings → Connectors.
- Find Wealth.com in the directory and enable it for the organization.
Each member, once:
- Go to Settings → Connectors.
- Find Wealth.com in the list and choose Connect.
- Sign in to Wealth.com as above.
Each member authenticates as themselves, so each one sees only their own book. Administrators can also disable individual tools for the organization — the three write tools, for example — from the same settings.
How discovery works
You do not need any of this to connect from Claude; it is here for completeness. The server publishes standard OAuth 2.0 protected-resource metadata, which is how a client finds the authorization server without being configured for it:
curl -sS https://mcp.wealth.com/.well-known/oauth-protected-resource
An unauthenticated call to the endpoint answers 401 with a WWW-Authenticate header pointing at the same metadata, so a compliant client can begin the flow from the endpoint alone. The three scopes identify the advisor; the server defines no authorization scopes of its own, because entitlement is decided by Wealth.com's permissions service rather than restated in the token.
GET /health answers without a token. Everything else requires one.
Where to go next
- Tools — the 18 tools, grouped by the part of the client file they read.
- Data access and security — who can use the connector, how it is scoped to one advisor, what it never returns, and how to revoke it.