The Claude connector

Connect your own Claude to WealthY and ask about clients, tasks and meetings in plain language, with your own sign-in.

WealthY runs a connector that Claude (and other assistants that speak the same protocol) can use. Once connected, you ask Claude about your clients, prospects, tasks, requests and meetings, log a call or a note, and create or complete tasks, all from the Claude app you already use. Everything is scoped to your seat at your firm.

What it is

A remote connector at https://wealthy.to/api/mcp, with sixteen tools.
Sign-in is your usual WealthY login, through a consent screen. There is no key to copy and nothing to paste into a URL.
Read tools are marked read-only. The tools that write (log an activity, create or complete a task, update a prospect, prepare an onboarding package) are marked so Claude asks you before using them. Preparing a package never sends it: you review and send from WealthY.

Who can connect

Seat	Can connect
Advisor	Yes. Clients, prospects, tasks, requests and meetings as the tools allow.
Firm owner	Yes. Same tools; the API access panel shows every connection at the firm.
Sales	Yes, prospects and tasks only. The sales seat never receives client data.
Client, dealer admin, admin support	No. The consent page says why.

Connect from claude.ai

Open Customize > Connectors > Add custom connector.
Name: WealthY. URL: https://wealthy.to/api/mcp. Leave the advanced fields empty.
Click Add, then Connect. The WealthY consent page opens.
Sign in if asked, read what Claude will be able to do, click Allow.

Connect from Claude Cowork or Claude Code

Cowork: Settings > Plugins > Add plugin, paste https://github.com/ddjjyy1997/wealthy-for-advisors, then click Connect on the WealthY card in a new session. The plugin adds six skills: setup, pre-meeting, post-meeting, prospect intake, daily brief and compliance check.
Claude Code: claude mcp add --transport http wealthy https://wealthy.to/api/mcp, then /mcp, pick wealthy, choose Authenticate.

Names the app that is asking.
Lists in plain words what it will be able to do: see your clients and their accounts, log calls and notes, create and complete tasks, see meetings, briefs and meeting notes, see and update prospects.
Allow or Cancel. Cancel returns to Claude with nothing granted.
If your firm requires two-step sign-in for API access, the same rule applies here.

What Claude can do once connected

"Prep me for Amelia's review on Thursday": the client record, accounts, recent activity, open tasks and the WealthY meeting brief, in one page.
"Log my meeting with the Tremblays" with your notes pasted: a drafted note and the action items, shown in one approval table before anything is written.
"What is on today": meetings with brief-ready flags, overdue tasks, tasks due this week.
"What did Amelia and I agree last time": the notes of her recent meetings, newest first: summary, decisions, action items with owner and due date, and what is still open. Never the transcript.
"Where is Jane's TFSA transfer": who has each of her requests and since when, and the next step.
"Check this email before I send it": a screen for performance promises and unbalanced risk language, shown as a diff.

Every lookup starts by finding the person and confirming who they are. Nothing is written on a name match alone. Results are capped at fifty rows per call and 120 calls per minute per connection.

See and revoke connections

Settings > API access lists every connection at the firm as a Connected app row, with the seat that connected and the last use. Revoke stops every token for that connection at once. Reconnecting from Claude creates a new row.

Every tool call is written to the firm's data access log with the connection that made it. WealthY stores only hashes of tokens.

Other clients

Software that cannot sign in through a consent screen uses a wly_ key from Settings > API access instead, sent as a bearer header. Same tools, same scopes, same limits. Keys are for software; people connect through the consent screen.