wealthmcp.ai
← Back to directory

Wealth.com (Wealth MCP)

Wealth.com · Financial Planning

MCP ServerVendor

First-party remote MCP server bringing Wealth.com's estate and tax planning engine into Claude for Financial Advisors, announced September 14, 2026 and listed in Anthropic's connector directory. Wealth.com's developer documentation publishes the connection details: server address https://mcp.wealth.com/mcp over Streamable HTTP, OAuth 2.0 against identity.wealth.com, and 18 tools of which 15 read and 3 write. An advisor connects with their normal Wealth.com credentials, including their usual multi-factor step, and sees exactly the clients the web app shows them. From inside Claude they can ask what a trust actually says with page-level citations back to the document, find gaps in an estate plan, ask about health directives and asset disposition, model tax scenarios such as a Roth conversion against next year's brackets, visualize estate structures as flowcharts, and read household data including asset titling, beneficiary designations and wealth concentration.

estate planningtax planningtrust documentspage-level citationsClaude for Financial Advisors
Status
Vendor
Auth
OAuth
Hosting
Remote
Community rating
Not rated yet
Role
System

Provides one system's data and actions. Reads and writes inside a single product of record; it can act, but only within its own walls. More on System servers → All seven roles →

Open documentation →

Caveats

  • Vendor-verified only. The endpoint, transport, auth and tool counts above are reproduced from Wealth.com's own developer documentation. Not independently verified, and no live connection was tested here.
  • Not read-only. Wealth.com documents 3 write tools alongside 15 read tools. Start with read-only scopes and know which writes your firm has enabled.
  • Provisioned per firm. An active advisor account is not enough: Wealth MCP has to be on the firm's contract. Without it the connector still connects and lists its tools while every call fails. Client logins and read-only roles cannot use it at all.
  • Planning output is a model, not a fact. Tax scenarios and estate projections carry assumptions that will not travel with the numbers into a client deliverable. Check anything client-facing against the plan itself.
  • Document answers still need reading. Page-level citations make a claim checkable; they do not make it correct. Open the cited page before a trust provision goes into advice.
  • Firms with managed devices or networks may need mcp.wealth.com and identity.wealth.com allowed by IT.
Rate this server

How to connect Wealth.com (Wealth MCP)

Step 1

Remote server: paste a URL

Wealth.com (Wealth MCP) publishes a remote (Streamable HTTP) endpoint, so nothing is installed locally. Add it as a custom connector in Claude, ChatGPT or your IDE and paste the endpoint below.

Endpoint

https://mcp.wealth.com/mcp

Client config snippet

{
  "mcpServers": {
    "wealth-com-mcp": {
      "url": "https://mcp.wealth.com/mcp"
    }
  }
}

Step 2

Authenticate with OAuth

Your client opens a browser sign-in with the vendor. Approve only the scopes you need, and use a read-only account first when the platform offers one.

Step 3

Verify, then widen access

Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.

Prompts that use this server

Starter prompts from the Practice Stacks that rely on Financial Planning.

Planning data-gathering gap check

What's still missing before a plan can be built.

Financial PlanningFinancial PlanningInsurance & Annuities

Read-only: compare the planning inputs on file for <client name> in the planning tool against what the insurance and annuity records actually show, and list what is missing, stale or inconsistent before I build or update a plan: income, expenses, balances, coverage amounts, riders, premiums, beneficiaries, goals and assumptions. Output Item / Value in plan / Value at source / Status / Last updated. Do not edit the plan or write any assumption, flag gaps and mismatches rather than filling them in.

Guardrail · Read-only. Never let a tool invent a planning assumption.

Scenario comparison brief

A side-by-side read on two planning scenarios.

Financial PlanningFinancial PlanningMarket & Financial Data

Read-only: compare the existing plan for <client name> against the scenario <describe change, e.g. retire two years earlier>. Pull the plan's stored return, inflation and yield assumptions, then use market-data tools to show current comparable figures for the same inputs. Present outcome differences, an assumptions table of Plan assumption / Current market reading / Source / Date, and which assumption the result is most sensitive to. State every assumption explicitly. Do not save, overwrite or publish any scenario in the planning system.

Guardrail · Read-only. Plan illustrations are not advice, review before sharing.

Insurance and protection gap review

Coverage on file versus what the plan implies.

Financial PlanningInsurance & AnnuitiesFinancial Planning

Read-only: list <client name>'s in-force coverage, life, disability, LTC, annuity riders, with carrier, benefit, term and cost, then compare against the protection need implied by the plan. Flag gaps and expiring coverage. No product recommendations and no applications. Note where policy data could not be verified.

Guardrail · Read-only. Product recommendations require suitability review, not a chat tool.

Read the full connection guide →