wealthmcp.ai
← All seven roles

Composition axis

System MCP servers

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.

Example · Salesforce

A System server reads and writes inside one product of record. A CRM, a planning tool, a custody platform, an accounting package. It can act, but only within its own walls.

This is where most of the wealth stack lives, and it is where the real risk sits. A server that can create a task in your CRM can also create the wrong task. One that can update a household record can overwrite a field somebody spent an hour getting right. The question to ask before connecting a System server is not whether it works. It is what it can change, and whether you can tell afterward that it did.

Start read-only. Every listing here carries its auth model and whether the server is official, vendor-published or community-built. Where we know a server exposes write actions, the listing says so. Where a vendor's documentation does not make its write surface obvious, assume it is wider than you would like and scope the credential accordingly.

The other thing System servers do not do is compose. Each one knows its own product and nothing else. Getting a household's plan, positions and last meeting note into one answer means connecting three of them and letting the agent carry the facts between them.

System servers in the directory

103 servers in this directory play this role

The other roles

Read the full role taxonomy →