MCP · the long version

Plug in anything
that speaks MCP.

MCP is the open standard for connecting AI to tools — and Catalyst speaks all of it. Connect a tool server running on your own machine or in the cloud; secure sign‑in is handled for you. Catalyst discovers each server's tools automatically and keeps the connection alive, so the model sees new tools the moment a server comes online. Tools run on Catalyst's servers, not in your browser — your keys stay where they belong.

Three ways to connect

Local. Remote. Streamed.

Paste a command or a URL. Catalyst connects, lists the tools, and adds them to your chat toolbar. No code to write, nothing to glue together.

local

On your own machine.

Your files, git, a local database, your own scripts — anything that speaks MCP. Catalyst starts it up, keeps it running, and talks to it for you.

$ npx @modelcontextprotocol/server-filesystem ~/projects
remote

Hosted in the cloud.

Hosted servers — Linear, Notion, Stripe, your own internal services. Paste the URL and sign in once (secure sign‑in is handled for you), and the server's tools are ready in chat, workflows, and agents.

https://mcp.linear.app/sse
streaming

Streaming servers.

For long‑running tools that report progress as they go — image generation, web crawls, background queries. Updates stream straight into the chat in real time, so you watch the work happen instead of waiting on a spinner.

data: {"tool":"crawl","progress":42}
How it works

Tools run on the server. Your browser never sees the keys.

Your list of servers is stored privately, locked to your account. The tools themselves run on Catalyst's servers, never in your browser — so your keys and tokens never touch the page.

discovery

Tools show up on their own.

The moment a server connects, Catalyst reads its list of tools and hands them to the model. Added new tools on the server? Refresh it and they're available the next turn.

sign‑in

Protected services, handled.

Servers that need a login are handled for you — secure sign‑in, with access kept up to date automatically. Your credentials stay on Catalyst's servers and never pass through the chat in your browser.

health

Status visible at a glance.

Each server shows Active, Connecting, or Error in real time, with the actual error message — so when something breaks, you know whether to restart it, sign in again, or check the service itself.

isolation

Yours, and only yours.

Your servers belong to you. No one else on the platform can list them, run them, or even see they exist.

under the hood

Connections, kept alive.

Catalyst manages every connection for you — reusing them, reconnecting when one drops, and speaking the right version of the protocol with each server. Built on proven, battle‑tested foundations, so you never have to think about any of it.

everywhere

One tool, every surface.

A tool you connect once shows up in chat, in workflows (as a tool step), and in agents — ready to use everywhere, with nothing to set up twice.

it just works

Paste it. Watch tools appear.

The MCP servers page shows everything you've connected — name, type, status, number of tools — with one tap to add another. Your chat toolbar updates right away. No deploys, no rebuilds, nothing to code.

  • Live status. Each server's state stays in sync across your devices and tabs in real time.
  • It's all just settings. Add and remove servers without touching a prompt, a template, or a line of code.
  • Same model, more tools. The chat picker doesn't change. You just have more verbs available next turn.
catalyst · mcp servers
brave‑search HTTP · 14 tools · 42ms
github HTTP · 32 tools · OAuth
linear SSE · 11 tools · 88ms
filesystem STDIO · 6 tools · local
notion HTTP · token expired · refresh
+ add server STDIO · HTTP · SSE
Bring your tools

Any verb you can name.
Any service you can reach.

If it speaks MCP — and increasingly, everything does — Catalyst can call it. From chat, from workflows, from agents. One platform, every tool.