← All seven roles

Composition axis

Aggregator MCP servers

Normalizes several systems behind one interface. Hides many underlying providers behind a single normalized shape.

Example · Truthifi

An Aggregator normalizes several underlying providers behind one interface. You ask it one question in one shape, and it deals with the fact that six custodians answer that question six different ways.

That normalization is the whole product. Anyone who has pulled positions from multiple custodians knows the work is not the retrieval, it is reconciling formats, field names, and the several ways a single account can be represented. An Aggregator absorbs that so the agent does not have to.

What you give up is fidelity at the edges. A normalized shape is a lowest common denominator, and provider-specific fields either get dropped or mapped into something approximate. When a number looks wrong, you are now debugging two layers instead of one.

Aggregators also sit on credentials, as gateways do, though usually for a narrower set of systems. Ask where the credentials live, whether the connection is read-only, and what happens to cached data when you disconnect.

Account aggregation and the custodial bridges are the main Aggregators here. They are frequently the only practical route to a platform that has not published a server of its own.

Aggregator servers in the directory

18 servers in this directory play this role

The other roles

Read the full role taxonomy →