Other MCP clients

Connect any MCP client that supports remote Streamable HTTP servers, with OAuth sign-in or a custom Authorization header.

Any MCP client that supports remote servers over Streamable HTTP can use Link in Seconds. It can sign in with OAuth (no key, you approve it in the browser) or send an API key in a custom request header. Look for a “remote”, “HTTP” or “URL” server option.

Settings to enter#

FieldValue
Namelinkinseconds
Type / transportHTTP (Streamable HTTP)
URLhttps://linkinseconds.com/api/mcp
HeaderAuthorization: Bearer lis_YOUR_KEY

Most clients use a JSON shape like this one:

JSON
{
  "mcpServers": {
    "linkinseconds": {
      "url": "https://linkinseconds.com/api/mcp",
      "headers": { "Authorization": "Bearer lis_YOUR_KEY" }
    }
  }
}

Clients that sign in with OAuth#

Apps that connect to remote servers with OAuth and have no field for a header can connect too. Enter the server URL, choose OAuth, and the app finds our sign-in on its own: a 401 from the server points it to /.well-known/oauth-protected-resource, and it registers itself, sends you to a Link in Seconds page to approve it, and gets a token that only works on the MCP server. ChatGPT works this way; see the ChatGPT guide.

  • Authorization code with PKCE (S256), public clients, scope mcp.
  • Clients register themselves with dynamic client registration (RFC 7591), once per connection.
  • Access tokens last one hour; refresh tokens rotate on every use.
  • You can disconnect an app at any time under Connected apps on the API keys page.

Test the connection yourself#

This is the first request every client sends. A JSON reply with serverInfo means your key works:

Shell
curl -s -X POST https://linkinseconds.com/api/mcp \
  -H "Authorization: Bearer lis_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"test","version":"1"}}}'
ReplyMeaning
200 with serverInfoWorking.
401 UnauthorizedKey missing, mistyped or deleted. An OAuth client starts its sign-in from this reply.
403The account is suspended.
405 on GETNormal. The server only answers POST; it never opens a stream.

Protocol details#

  • Stateless: no session id, every request stands alone. Batched requests are accepted.
  • Protocol versions 2024-11-05 through 2025-11-25 are accepted; the server answers with the one you request.
  • Capabilities: tools only (no resources or prompts).
  • The server is also described by its server card.

Note

Using an MCP client in the browser? CORS is open on the server, and the key or OAuth token, not cookies, is what authenticates.

Last updated 21 October 2026. Something unclear or missing? Tell us.

Optional cookies for analytics, ads and session replay.