Skip to content →

Oppulence Desktop speaks MCP. Point it at servers in your config and the copilot can use those tools. We are not going to pretend every tool in the registry is a first-party, production-ready integration. MCP is how you attach the rest.

Oppulence / MCP

Bring the tools you already run.

A closed catalog goes stale the week after we publish it.

We are not going to pretend every tool in the registry is a first-party, production-ready integration. MCP is how you attach the rest.

A config file, a server, a tool call.

MCP servers live in ~/.rowboat/config/mcp.json. The desktop agent runtime can call them. The API also has a managed connector registry — treat money-moving scopes as development-only unless we say otherwise.

Local servers

If it runs on your machine and speaks MCP, the desktop app can use it.

Managed registry is not a promise of production writes

GitHub, Linear, Notion, Stripe, and others appear in the API connector registry. Finance write scopes are environment-limited.

Questions

Stripe is how Oppulence itself bills plans. A Stripe MCP connector in the registry is a different thing, and money-moving scopes are not a production claim.