You connect Inline decides Agents get REST API an OpenAPI spec + a key you hold MCP server Asana, Notion, your own Inline one plane: per user, per tool every call logged A scoped MCP endpoint its own URL, its own tool list A scoped key for code that speaks HTTP

A server is a named handful of tools at its own address — never more than you can already reach, so handing one to an agent gives away less than handing over your own account.

A server can mix both kinds. An agent cannot tell which is which — Inline picks the right credential per call. Endpoints from a registered REST API are served on a server or a key that names them, and left out of the plain /mcp address, where one API's ninety-odd endpoints would crowd out everything else.

—
Sources connected
—
Tools you can call
—
Servers
—
Calls logged

Connect an agent

Add one of these as a connector. You will be asked to sign in, and you get exactly what you are allowed.

Serves tools from every MCP server you have connected. A server has its own address instead; find those under Servers.
A separate service, with its own address. APIs you register are reached here, not through the gateway above.

Recent activity

See all