Inlay

Inlay is a remote MCP server: there is nothing to install. Its endpoint is https://inlay.dev/api/mcp/{site_key}, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

It also lists an endpoint on the older SSE transport https://inlay.dev/api/mcp/{site_key}. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.

The URL contains placeholders to fill in before connecting: {site_key}.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect