Other MCP clients

Any MCP client that supports remote servers over Streamable HTTP with a custom request header can use Link in Seconds. Look for a “remote”, “HTTP” or “URL” server option and a place to add headers.

Settings to enter#

Most clients use a JSON shape like this one:

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

Clients that only support OAuth#

Some apps only connect to remote servers that sign you in with OAuth and have no field for a header. Our server uses API keys, so those apps can't connect directly yet. Use a client that supports headers, or call the HTTP API from your own code.

Test the connection yourself#

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

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"}}}'

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.