Integrations

Your companion isn’t limited to what you tell it. Some outside services are simply there from the start; others you connect once, and then it can read from them and act in them as part of the conversation. For what it can already do without connecting anything at all, see platform tools.

What it is

An integration is a connection to an outside service. There are three kinds, and they behave differently.

Platform integrations are supplied by weside. They need no setup and no account of yours — the app marks them Always available. Today that is Perplexity for research, Gemini for generating images, OpenWeatherMap for weather, Mapbox for maps and navigation, and Context7 for up-to-date library documentation. Two of them cost you something: calls to Perplexity and Gemini carry the badge Costs Favors.

Connected integrations are yours. weside carries a catalog of around 170 toolkits — Gmail, Calendar, Drive and Docs, GitHub, Supabase, Notion, Jira, Confluence and far more than a list can usefully name. You connect the ones you want with your own account.

MCP connections point at a server rather than a service. Two are ready-made: your own Home Assistant through its ha-mcp add-on, and DeepWiki, which answers questions about any public GitHub repository and needs no account. Beyond those, you can paste the configuration of any MCP server you run.

Connecting a service doesn’t switch it on for every companion. It makes the service available to your account; you then decide which companion gets to use it.

Why it matters to you

A companion that can only talk is limited to whatever you paste into the chat. One that can reach your calendar, your repo or your home can do the task instead of discussing it — draft the mail, open the pull request, check the forecast before you ask about the bike ride.

The three kinds matter for a practical reason: the first costs you no setup, the second costs you a connection and counts against your plan, and the third is where your own infrastructure comes in.

How you use it

Connecting a service

1. Open the catalog. From a companion’s Body space, choose Manage Integrations. The catalog has a search field over all toolkits and a category rail, plus a Most Used section if you’d rather see what other people reach for.
2. Connect. Most services use OAuth, some take an API key, a few need no authentication at all. Connected services collect under Connected Integrations.
3. Activate it for a companion. A connected integration isn’t live until a companion may use it. Back in that companion’s Body space, switch the tool on. Two companions can carry different tools on the same connected service.

📷 Screenshot

The integrations catalog: the search field over all toolkits, the category rail, and the Platform Integrations section with its Always available and Costs Favors badges.

Your own MCP server

On the Soulmate plan you can connect any MCP server by pasting the mcp.json snippet from its documentation — a single server object or an mcpServers wrapper. Every server you paste is tested on the spot, and the result says Connected, Rejected or Unreachable. Your key is stored encrypted. The entry keeps the badge Custom · Unverified for as long as it exists, because weside has vouched for nothing about it.

Home Assistant works the same way but needs no Soulmate plan: you give weside the URL of your own instance, and you decide in ha-mcp which tools it exposes. weside talks to that URL and nothing else.

Limits & edge cases

• Your plan caps how many you connect. Spark allows one connected integration, Bond three, Companion and Soulmate as many as you like. Platform integrations don’t count against it. See plans & credits.
• Connecting isn’t activating. A connected service does nothing until you switch it on for a specific companion.
• A connection can expire or be revoked. It then moves into a Needs Reconnect section and stops working until you reconnect it.
• Not every toolkit exposes all of its actions. GitHub, for one, is deliberately trimmed — the dangerous actions are not on offer.
• Some toolkits run on your bill. Where a service charges for what it does, it charges your account, not weside’s.
• A tool that couldn’t run says why. Refusals come back with a reason — an owner gate in a shared room, a plan limit, the EU-only switch, or a name nothing recognises. Your companion decides what to tell you about it.
• EU only blocks platform integrations, not yours. Perplexity, Gemini, OpenWeatherMap and Mapbox process outside the EU and Context7 commits to no region — with the EU-only switch on, they are refused before anything is transmitted. Integrations you connect yourself carry no location and are never gated this way. See residency and regions.
• Pasting a custom MCP server is a Soulmate capability.

Where next

• Platform tools — what your companion can do before you connect anything.
• Skills — the other way a companion gains new capabilities.
• Sandbox & workspace — the body these tools act through.
• MCP server — the opposite direction: how other MCP clients connect to your companion.
• Plans & credits — what each plan tier unlocks.