Built to connect
Use our agent, or bring your own
There are two ways to work with Vega: through Sienna, the agent built into VegaOS, or through the AI assistant your teams already use, over MCP. Either way it is signed-in, permissioned and auditable, and it works in the systems the firm already runs.
Use our agent
Sienna
The agent built into VegaOS. She works in the systems you already run, and every change she wants to make arrives as a proposal for a person to approve.
Meet SiennaUse your agent
MCP
Bring the assistant your teams already use. Vega's MCP connectors work across MCP clients, including Claude and ChatGPT, and act as the signed-in user.
How the connectors workMCP connectors
Vega, inside your AI assistant
Vega ships two MCP connectors, Vega LP and Vega GP, that work across MCP clients, including Claude and ChatGPT. Sign in with OAuth 2.1 and the connector acts as you: it sees exactly what you are permitted to see, and nothing else.
Built to the latest MCP spec
Designed for the current specification, with the user experience in mind, not a thin wrapper over an API.
Asks rather than guesses
When a request is missing a detail, such as which fund, Vega prompts the user back through MCP elicitation.
MCP Apps, not only tools
Vega serves MCP Apps: interactive views of funds, documents and capital activity that open inside the conversation.
Vega LP
Read-only for investors: funds, investments, performance, capital activity, documents and interactive viewers. Ask a question in your assistant; the answer comes from your own fund data.
Vega GP
Tools for the firm: analytics, pipeline and casework, in the same conversation as the rest of your work.
Both connectors are brandable per tenant, so your investors see your name, not ours.
Where it works
Wherever your people already work
The same connectors and the same permissions, in Claude, ChatGPT and other MCP clients.
In claude.ai and Claude Desktop. Investors and IR teams ask about funds, performance and documents in plain language, and the answers come from Vega, scoped to the signed-in user.
VegaOS connectors
The systems Sienna reads from and works in
VegaOS reads from and works in the systems your firm already runs: your CRM, email and calendar, documents and data platforms. We also build the integrations nobody else wants to, into fund administrators, and a connector builder covers the systems particular to your firm. Your stack stays your stack; VegaOS joins it.
Questions we are asked
- Which AI assistants do the connectors work with?
- Any client that supports MCP, including Claude (claude.ai, Claude Desktop and Claude Code) and ChatGPT. The connectors follow the current MCP specification, so they work the same way in each.
- What can the MCP connectors actually do?
- Vega LP is read-only: funds, investments, performance, capital activity, documents and interactive viewers. Vega GP covers analytics, pipeline and casework. Both act as the signed-in user, never beyond their permissions.
- How do users authenticate?
- OAuth 2.1. Each person signs in as themselves, and the connector acts as that user; there are no shared credentials and no service-account workarounds.
- Can investors see the connector under our brand?
- Yes. The connectors are brandable per tenant, so your investors connect to your name inside their assistant.
See Vega connected
Walk through both ways in with us, from Sienna and your AI assistant to your CRM.