← All servers

LMGram

connects

api.lmgram.com

Consent-based human matchmaking for peer advice, collaboration, and practical help.

https://api.lmgram.com/mcpWebsiteOAuthMCP 2025-03-26v0.1.0last checked 3 Sep 2026spoke MCP on 3 of 3 checks (30 days)initialize in 306 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

Claude CodeConnects

The authorization server advertises RFC 7591 registration, so Claude Code can register itself and sign you in through the browser.

claude mcp add --transport http lmgram https://api.lmgram.com/mcp

Claude Code docs · read on 2026-08-30

Claude (claude.ai & Desktop)Connects

The authorization server advertises RFC 7591 registration, so Claude (claude.ai & Desktop) can register itself and sign you in through the browser.

Settings → Connectors → Add custom connector, then paste https://api.lmgram.com/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

ChatGPTConnects

The authorization server advertises RFC 7591 registration, so ChatGPT can register itself and sign you in through the browser.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://api.lmgram.com/mcp.

ChatGPT docs · read on 2026-08-30

CursorConnects

The authorization server advertises RFC 7591 registration, so Cursor can register itself and sign you in through the browser.

{
  "mcpServers": {
    "lmgram": {
      "url": "https://api.lmgram.com/mcp"
    }
  }
}

Cursor docs · read on 2026-08-30

VS Code (Copilot)Connects

The authorization server advertises RFC 7591 registration, so VS Code (Copilot) can register itself and sign you in through the browser.

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

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 3 Sep 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme
OAuth
Issuer
https://api.lmgram.com
Dynamic client registration
Advertised (RFC 7591)
Client ID Metadata Document
Not advertised
PKCE
S256
Grant types
authorization_code
Scopes
profile, match:read, match:write, chat:read, chat:write
Protected-resource metadata
Published (RFC 9728)
Anonymous access
Handshake succeeds; 6 tools listable
Documentation
https://api.lmgram.com/docs/connectors

What the probe found

6 tools usable without signing in

The server exposes a public surface before authorization: get_current_user, request_human_match, list_match_requests, start_chat, list_messages, send_message.

Tools

get_current_userlist_match_requestslist_messagesrequest_human_matchsend_messagestart_chat

Contract history

2 Sep 2026v0.1.0first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

MCP status badge for LMGram
[![MCP status](https://mcpi.app/servers/lmgram/badge.svg)](https://mcpi.app/servers/lmgram)