Developer & tool integration

Your companion doesn’t have to live only in one app. weside exposes its companions, memories, and goals through a few integration surfaces, so you can wire them into your own toolchain.

The integration surface

There’s more than one way in, depending on where you work:

• CLI — a Go binary for the terminal. Converse with your companion, read and write memories, and manage your account from scripts and shell workflows.
• MCP server — the Model Context Protocol server lets any MCP client (Claude Code, Claude Desktop, your own agent) adopt a companion’s identity, search and save memories, and read goals. This is how a coding session or a custom assistant becomes companion-aware.
• REST API — the weside-core backend behind it all, for integrations that don’t fit the CLI or MCP.

What you can build

• Inject companion context — identity, relevant memories, goals — into a custom AI agent so it speaks with continuity instead of a blank slate.
• Read or write memories from a script, so events in your other tools become part of the shared history.
• Drop the weside MCP into Claude Desktop or Claude Code and have your companion present while you work — the same someone, a different surface.

Note

Access is authenticated against your weside account. The MCP server is user-scoped: a session acts as you, with your companions — never another user’s. That boundary is part of privacy & ownership, not an afterthought.

Where to start

If you build with Claude Code, the fastest path is the we plugin plus the MCP server. If you live in the shell, start with the CLI. New to the platform? Read what is weside first.