LidmeoDevelopers

Cursor, VS Code and other clients

Any MCP client that speaks HTTP connects to Lidmeo, with OAuth or an API key.

The connector follows the MCP specification (HTTP transport, "Streamable HTTP"), including the older handshake some clients still use. Two ways to authenticate:

  • OAuth (recommended): the client opens Lidmeo's sign-in page. It discovers the authorization server on its own, and registers itself if it needs to.
  • An API key in the Authorization: Bearer … header, for a client without a browser. See authentication.

Cursor

In ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "lidmeo": { "url": "https://mcp.lidmeo.com/mcp" }
  }
}

With an API key:

{
  "mcpServers": {
    "lidmeo": {
      "url": "https://mcp.lidmeo.com/mcp",
      "headers": { "Authorization": "Bearer lid_live_…" }
    }
  }
}

VS Code

In .vscode/mcp.json:

{
  "servers": {
    "lidmeo": { "type": "http", "url": "https://mcp.lidmeo.com/mcp" }
  }
}

Any other client

Give it the address https://mcp.lidmeo.com/mcp and the HTTP transport. For a client that can only launch a local program ("stdio" transport), go through a bridge such as mcp-remote:

npx mcp-remote https://mcp.lidmeo.com/mcp

For client developers

  • Protected resource metadata (RFC 9728): https://mcp.lidmeo.com/.well-known/oauth-protected-resource/mcp.
  • Authorization server (RFC 8414): https://hub.lidmeo.com/.well-known/oauth-authorization-server. Authorization code with PKCE (S256), refresh tokens, dynamic registration (RFC 7591) and client metadata documents accepted.
  • A request without a token gets 401 and the WWW-Authenticate header pointing to this metadata.

On this page