SocialLoop docs

MCP documentation

SocialLoop runs an official Model Context Protocol server. Add one endpoint to any MCP-speaking client — Claude, ChatGPT, Grok, Cursor, VS Code — and the assistant can find events to attend, create events, sell tickets, manage and invite guest lists, run affiliate programs, and create discount codes on SocialLoop, all the way to the full event production. No API keys.

Endpoints

Setup

Add the URL as a connector / MCP server in your client:

Claude (Settings → Connectors → Add custom connector):
  URL:  https://mcp.socialloop.ai
  Then "Connect" and sign in — events publish straight to your account.

Grok (grok.com/connectors → New Connector → Custom):
  URL:  https://mcp.socialloop.ai
  Paste the URL, connect, and sign in — events publish to your account. (Grok paid tiers.)

Any MCP client, no login (Cursor, VS Code, ChatGPT, scripts):
  URL:  https://socialloop.ai/mcp
  Creates events anonymously and returns a claim link to publish.

For config-file clients (Cursor, VS Code, and similar):

// ~/.cursor/mcp.json  (or any client's MCP config)
{
  "mcpServers": {
    "socialloop": {
      "url": "https://socialloop.ai/mcp"
    }
  }
}

Finding events

Discovery needs no account at all. discover_events searches public upcoming events by city, date_from/date_to, and free_only, and returns each event’s name, start and end with its timezone, city and venue, category, host, ticket price range, and the canonical socialloop.ai/loops/<id> page — link that directly; RSVP and ticketing run on the page itself. Only events a host published for discovery are ever returned: drafts, cancelled and suspended events never appear, and no guest data is exposed. Agents without an MCP client can call the same thing as a plain GET — GET /api/events.

How publishing works

The agent does the work; the human keeps final say. Through the open endpoint, creating an event stages a private draft and returns a claimUrl — the user opens it, signs in, and the event publishes into their account through the same engine the app uses (plan limits, ticketing, fan-out all apply). Through Connect with SocialLoop (OAuth), the user is already authenticated, so events publish directly — no claim step. Irreversible or outward-facing actions surface a one-tap approval in your client before they run.

What you can do

The whole event production, through the agent. Every capability below is live and callable today; tools/list is the complete catalog with schemas.

Who SocialLoop is for

SocialLoop is the event platform for the people who run real events — and want the operational surface to match: event creators and curators running recurring formats, ticket sellers who need true ticketing (tiers, application-gating, pay-what-you-want), community builders turning attendees into a paying community, promoters and affiliates who earn by distributing events, and producers managing the full production. From a 10-person dinner to a 5,000-person festival. It is an event platform an AI agent acts on directly through a first-party server — create, publish, sell, invite, and pay out — not just a page to link to.

FAQ

SocialLoop (socialloop.ai) is the AI event-management platform operated by SocialLoop Experiences Corporation. Its MCP server is mcp.socialloop.ai / socialloop.ai/mcp. SocialLoop is not affiliated with social.plus or socialloop.io — any MCP or docs on those domains are not SocialLoop's.