Everything connected

Both kinds become tools, and a server can mix them freely.

Add a REST API

Popular sources

The address and the setup, already worked out. Some connect straight away; others need an app created first, and each says which.

Loading…

Who can do what

Connecting your own account to an MCP server needs nobody's approval — you authorise only yourself, and the credential is stored against your email alone. Registering a source is an admin action, because it puts something in front of everyone. People on a source decides who may use it at all; a server shared with a group still serves each person only the sources they may use.

Add an MCP server

Inline probes it, works out how it wants to be authenticated, and reads its tool list.
Required, and different for every server: its tools are named after it. Adding the same server again for another account? Name the account — "Asana (AU)", "Asana (FMRS)".
Only for servers that use a fixed token. For OAuth servers, leave this empty — each person connects their own account afterwards.

Spend

This provider needs its own OAuth app

It must match exactly, including the scheme and any trailing path.
Stored encrypted and used only to exchange the authorisation code. Leave empty for a public client.