The MCP endpoint lets an AI assistant read Place to Mingle data on your
behalf, with your explicit authorization.
How it works
- Point your MCP client at the published endpoint URL.
- Your client discovers where to authenticate and sends you through a normal
sign-in. - You approve the connection. That approval is a distinct act — it is not a
side effect of signing in to the website, and signing in to the website does
not create one. - The assistant can then call the read tools until you disconnect it.
What an assistant can and cannot do
Can: read what you can read, through a small, hand-listed set of tools.
Cannot: post to this forum, send messages, RSVP on your behalf, or reach
dating data. The tool list is enumerated by hand rather than generated, so a
new endpoint never silently becomes a new assistant capability.
Disconnecting
Disconnect in the portal. That revokes the assistant's authorization at the
identity provider — it does not touch your API keys or your browser session,
which is the whole reason it is a separate credential.
When it does not work
The two common failures are worth checking before you post:
- The endpoint URL must match exactly, including or excluding a trailing
slash as published. It is compared literally. - The scopes your client requests must be ones your connection was granted.
A client that invents a scope gets a hard refusal on the first attempt,
before any token exists.
Include your client's name and version when you post — behaviour differs
between them more than you would expect.