wealthmcp.ai
← Back to directory

OpenWealth MCP

Community (alpflo) · Wealth Platforms

MCP ServerCommunity

Early-stage open-source server exposing Swiss custody data — customers, positions and transactions — through the OpenWealth Custody Services API v3.2.0 standard. Read-only by design; requires OpenWealth credentials, sandbox-oriented, research-grade rather than production.

openwealthswitzerlandcustodyread-onlyopen source
Status
Community
Auth
API key
Hosting
Local
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. All seven roles →

Open documentation →
Rate this server

How to connect OpenWealth MCP

Step 1

Local server — run it on your machine

OpenWealth MCP runs locally over stdio. You need Node.js (for npx) or Python (for uvx) installed, then add the command below to your client's MCP config file.

Command

pip install alpflo-openwealth-mcp && python -m openwealth_mcp

Client config snippet

{
  "mcpServers": {
    "openwealth-mcp": {
      "command": "pip",
      "args": [
        "install",
        "alpflo-openwealth-mcp",
        "&&",
        "python",
        "-m",
        "openwealth_mcp"
      ]
    }
  }
}

Step 2

Authenticate with API key

Create a key in the vendor's dashboard and store it as an environment variable in your client config — never paste it into a chat window.

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 Wealth Platforms.

Pre-meeting client brief

Everything you need on one page before you walk in.

Client Review Meeting PrepCRMWealth Platforms

Read-only: build a pre-meeting brief for <client name>: current portfolio summary, allocation vs. target, YTD performance, open service items, last three CRM interactions, and any commitments I made previously. Mask account numbers to the last four digits, cite the source tool for each figure, and do not update CRM, place trades or send anything.

Guardrail · Read-only. Verify performance numbers against the system of record before presenting.

Market context talking points

Three to five neutral talking points on recent market moves.

Client Review Meeting PrepWealth PlatformsMarket & Financial Data

Read-only: pull <client name>'s current holdings and sector or asset-class weights from the wealth platform, then use market-data tools to explain what moved those specific exposures over the last quarter. Return three to five neutral talking points, each tied to a holding or weight and to the market data behind it. No forecasts, no recommendations to buy or sell, no performance promises. Cite the source and date for both the holdings figure and the market figure so I can verify before I use it with a client.

Guardrail · Educational framing only. Avoid forward-looking or promissory language.

Allocation drift report

Which accounts have drifted and by how much.

Trade & RebalanceWealth PlatformsCustody & Clearing

Read-only: compare current allocations against target models across my accounts, using the wealth platform for targets and modelled positions and the custodial feed for actual settled holdings and cash. List every position or sleeve drifted beyond <tolerance, e.g. 3%> as Account / Sleeve / Target / Actual / Drift / Estimated trade size, and separately flag any holding or cash balance where the platform and the custodian disagree, since that breaks the drift math. Do not place, stage, cancel or modify any order. Cite the tool behind each figure.

Guardrail · Read-only. Never grant trading scopes to a tool that only needs to report.

Read the full connection guide →