# Wealthbox MCP server for financial advisors

> A Wealthbox MCP server for financial advisors: connect each advisor through OAuth, keep deletes off the AI path, and see who touched a client record.

**TL;DR** A Wealthbox MCP server for financial advisors lets an advisor ask Claude or ChatGPT about clients, tasks and notes. Wealthbox authorizes OAuth per user, so each advisor connects their own account and sees only what they may see. Elaichi's Wealthbox connector has 50 tools, seven of them deletes, and a role restriction plus the audit log decide what an assistant may touch and what is recorded.

## Can a Wealthbox MCP server for financial advisors keep each advisor to their own clients?

Yes. Connect each advisor's own Wealthbox account in Elaichi through OAuth, add https://api.elaichi.ai/mcp in Claude, ChatGPT, Cursor or Microsoft Copilot, and hold the advisor role to nine named tools with a restriction on the role. Wealthbox's own per-user rules then decide which clients each call can see.

Before a client meeting, an advisor wants the last notes, the open tasks and any pending opportunity on one screen. Operations staff want the next step of an onboarding workflow. Both live in Wealthbox. MCP (Model Context Protocol) lets an AI client discover and call tools, and Elaichi's [Wealthbox connector](/connectors/wealthbox/) puts 50 of them behind one address. The hard questions at an advisory firm are whose access each call uses, which tools can erase a client record, and what trail exists afterward.

## How does Wealthbox decide what a call can see?

By the signed-in user. Wealthbox offers a personal access token and OAuth 2.0, and they behave differently for a firm.

A token comes from Settings, then API Access, in the app. Wealthbox's help center says trial accounts have no API access (checked November 2026, [Wealthbox help center](https://help.wealthbox.com/hc/en-us/articles/29980458723739-How-do-I-create-an-API-access-token)). The developer docs reserve personal tokens for personal builds and testing, and describe OAuth 2.0 with two scopes, login and data. Authorization is scoped to individual users. Tasks and workflow calls return only items that user can access, and a 403 means the user may not view the resource. An access token lives two hours, and a refresh token lives 90 days (checked November 2026, [Wealthbox developer docs](https://dev.wealthbox.com/)). For a firm, that points to OAuth, one advisor at a time.

## Why should each advisor connect Wealthbox separately?

Because a connection runs every call as the account that made it. In Elaichi, whoever is calling, the call uses the Wealthbox account of the person who connected.

Picture one operations lead who connects Wealthbox and shares it with fifteen advisors. Every advisor's question then runs as the operations lead, who may see more clients than any single advisor should. If each advisor authorizes their own Wealthbox account, Wealthbox's per-user rules cut each call down to that advisor's view. Each advisor also approves their own AI client grant. After an admin edits a role, the change takes effect in about two minutes. At departure, revoking a share or disconnecting an account takes effect on the caller's next call. A shared connection has one honest use: a service identity for a back-office job that operations owns.

## Which Wealthbox tools should an advisor role reach?

Nine: six reads and three small writes. The connector has 26 list and get tools, 8 creates, 6 updates, 7 deletes and 3 workflow and bulk actions.

The reads are list_all_wealthbox_contacts, get_single_wealthbox_contact_by_id, list_all_wealthbox_notes, list_all_wealthbox_tasks, list_all_wealthbox_opportunities and list_all_wealthbox_events. The writes are create_a_wealthbox_note, create_a_wealthbox_task and create_a_wealthbox_event. An operations role adds wealthbox_workflow_steps_complete, wealthbox_workflow_steps_revert and create_a_wealthbox_household_member for onboarding.

One read earns a second look. list_all_wealthbox_activity_stream returns events across the workspace, which is more than a single advisor's book needs.

## Which Wealthbox tools should no role hand to an assistant?

The seven delete tools. They remove a contact, event, household member, opportunity, project, task or workflow, and a client record is what a firm must be able to produce later.

They are delete_a_wealthbox_contact_by_id, delete_a_wealthbox_event_by_id, delete_a_wealthbox_household_member_by_id, delete_a_wealthbox_opportunity_by_id, delete_a_wealthbox_project_by_id, delete_a_wealthbox_task_by_id and delete_a_wealthbox_workflow_by_id. The connector has no delete tool for notes at all. Hold update_a_wealthbox_contact_by_id for the staff who maintain contact data, because an assistant rewriting a client's details is easy to ask for and hard to spot.

## Should the advisor rule be an allow rule or block rules?

An allow rule, because each role must stay on a short list. Wealthbox has only 24 tools that are not reads, so block rules are a fair choice when a firm wants nothing more than the seven deletes gone.

In Elaichi, restriction targets are role or user only; the organization default is the absence of a rule, which means allow everything. An allow rule naming the nine advisor tools gives the advisor role nothing else from Wealthbox. The catch is that once a role carries any allow rule, every connector and tool none of its allow rules names is blocked for that role. An advisor who also uses Gmail through the same endpoint needs allow rules for those tools too. Block rules work the other way, since a layer with only block rules has no allowlist, so everything it does not block passes it. When an advisor asks for a tool outside the rule, the reply says so. A restricted tool is left out of the tools Elaichi offers a client and cannot be called. Search still names it, flagged restricted, with no schema. Without a rule, approving an AI client lets it use every tool that advisor can use, deletes included, unless the grant is limited to chosen toolboxes. For more on per-user limits, see [how employee permissions reach AI agents](/blog/ai-agents-employee-permissions/).

## What does the audit log record, and is it a records archive?

It records who ran which tool, on which connection, from which AI client, for 90 days. It is not a books-and-records archive.

A row exists for each Wealthbox call that reaches execution, and it names the person, the tool, the connector, the connection and the AI client. A call a restriction refuses writes no row, so the log shows what ran, not what was tried. Ninety days is short against the five-year retention the SEC rule sets for most adviser records. That rule also asks for records to be indexed, retrievable, duplicated and safeguarded from loss or alteration ([17 CFR 275.204-2](https://www.law.cornell.edu/cfr/text/17/275.204-2), checked November 2026). Whether an AI conversation counts as a record under that rule is a question for your counsel. For a longer trail on your own side, export to your own Datadog comes with the Black plan.

## Does a two-advisor firm need role restrictions at all?

Usually not. With no operations staff, each advisor connects their own Wealthbox, and Wealthbox's per-user rules already separate their books.

The case for a role restriction begins when advisors, associates and operations see different books and do different work, and a principal wants one place to read who did what. The [Wealthbox connector page](/connectors/wealthbox/) lists every tool by name, and [audit log retention for AI actions](/blog/audit-log-retention-ai-actions/) goes further on the log.

## FAQ

### Does Wealthbox apply each advisor's access when an AI tool calls its API?

Yes, when the advisor connects through OAuth. Wealthbox says authorization is scoped to individual users, that requests act within the signed-in user's permissions, and that a 403 means that user may not view the resource (checked November 2026, https://dev.wealthbox.com/). Connect each advisor separately, because a shared connection runs everyone's calls as one user.

### Can the Elaichi audit log serve as a books-and-records archive?

Do not rely on it for that. Elaichi keeps 90 days of audit history, and the SEC rule for investment advisers sets most record retention at five years from the end of the fiscal year of the last entry (checked November 2026, https://www.law.cornell.edu/cfr/text/17/275.204-2). For a longer trail, export to your own Datadog comes with the Black plan. Ask your compliance counsel what must be kept.

### What can an assistant do in Wealthbox without delete rights?

Plenty. Elaichi's Wealthbox connector offers reads for contacts, notes, tasks, events, opportunities, projects and workflows, plus creates and updates. The seven delete tools, covering contacts, events, household members, opportunities, projects, tasks and workflows, can stay off every role. Notes have no delete tool at all.

### How many requests can an AI client send to Wealthbox?

Wealthbox throttles per access token at one request per second, measured over a five-minute sample, and short bursts above that are allowed (checked November 2026, https://dev.wealthbox.com/). A shared token means the whole firm shares that budget, which is another reason to connect advisors one by one.

## Read next

- [Audit Log Retention: AI Actions at 90 Days vs Seven Years](/blog/audit-log-retention-ai-actions/) — Elaichi keeps 90 days of audit log retention, AI actions included. A seven-year mandate needs a customer-owned destination, and only Datadog delivers today.
- [AI agents with employee permissions, no shared bot](/blog/ai-agents-employee-permissions/) — How to run AI agents with employee permissions instead of one shared service account, and the cases where a named service identity is still correct.
- [What an AI agent audit log must capture](/blog/what-an-ai-audit-log-must-capture/) — An AI agent audit log must capture who acted, which client called, which account was reached, what was tried and how it ended. Argument contents stay out.
