Skip to main content
The catalog is the list of MCP servers Splox already knows how to talk to. You pick one, connect it once, and your agents can call its tools. It lives on the Tools screen, under Browse.
The Browse tab of the Splox Tools screen

The catalog: name, category, description, auth type and transport

What a catalog entry is

An entry is a server somebody else runs, plus everything Splox needs to reach it on your behalf. This is one, as the app fetches it:
The two fields that decide what connecting feels like:
string
http or sse. How Splox speaks to the server. The catalog knows the right one; you only choose it when you add a server of your own.
string
oauth — you are redirected to the provider and come back with a token. manual — you paste API keys into named fields. Either way the credential is held by the platform, not by your harness. See Connections.
Some entries are Splox’s own bridges to a service (mcp.splox.io/reddit/mcp), some are the vendor’s own server (mcp.linear.app/sse, mcp.notion.com/sse). The distinction does not change anything about how you use it.
per_page is capped at 20 by the server, whatever you ask for. Page through with page=, or use the search box in the app.

Adding one

Click the card. You get a page that shows what the server is, the URL it lives at, and a form for the one thing Splox does not already know — who you are on the other side.
Connecting Linear over OAuth

An OAuth entry asks for a name; the authorization happens at the provider

The Connection name is yours — it is how the server appears in your own list afterwards, and it matters when you connect the same provider twice for two different accounts.

Adding a server that is not in the catalog

Add MCP server takes a URL instead of an entry. You choose the transport yourself, and authentication is either none or custom headers.
The Add custom MCP server form

Any MCP endpoint, by URL, with headers you name

The app posts what you typed:
That id is the point of the whole exercise. It is what an agent’s tools entry names.

What you have afterwards

The server shows up under Your MCP servers, with its transport, its auth type and a trash icon that removes it.
The Your MCP servers tab with one connected server

A connected server: this is where its uuid comes from

Ask the platform what it exposes:
Then give it to an agent, by uuid, in programs/<name>/main.py:
No file in the checkout lists your servers, so from inside a run the way to find the uuid and the slugs is to ask:
Get a slug wrong and git push origin main refuses the publish, naming the file and the slug — which is the cheapest place to find out. See Publishing a version.
The v2 API has the same two questions as GET /v2/tool-servers, with system:* ids for the platform packages and uuids for yours. Use that one from outside the product; the /api/v1 paths above are what the app itself calls.