Popameeting

One server, five doors

Help me get my MCP connected

Local Event Hub is one MCP server at /mcp. Claude, Claude Code, VS Code, ChatGPT, and Microsoft Copilot Studio are five ways in. Each client discovers OAuth settings and registers itself—you do not create an OAuth app by hand.

Tools run as you: search_public_events, get_event, and register_for_event. Paid listings may return needs_checkout so you finish payment in the browser.

Server URL — paste into every door

Loading the server URL…

Create a Local Event Hub account first at Sign in. Connectors RSVP and act only for that user.

Door 1Claude

Claude Connectors call Local Event Hub from Anthropic’s cloud. Paste one URL. Dynamic client registration creates the OAuth client, then the browser asks you to sign in.

Add the connector

  1. In Claude, open Customize → Connectors → Add custom connector.
  2. Choose Web and paste the server URL below. Leave OAuth client id and secret blank.
  3. Save, then Connect. A browser tab opens the Local Event Hub sign-in page.
  4. Sign in and choose Allow.
  5. Enable the connector in chat. Ask Claude to search upcoming events near you, open one by id, or RSVP on your behalf.
Door 2Claude Code

The terminal client registers the same URL. The first tool call opens a browser for sign-in. After that, search_public_events, get_event, and register_for_event are available in the session.

Register the server

  1. From a terminal, run the command in the box below. Add -s project if you want the server in .mcp.json for the repo.
  2. When the browser opens, sign in to Local Event Hub and choose Allow.
  3. Run claude mcp list. local-event-hub should report connected.
  4. Ask Claude Code to list public events, fetch details for one event, or RSVP. Paid events return needs_checkout with a checkout URL.
Door 3VS Code Copilot

VS Code reads the discovery document from the URL. The workspace file is only the server address—no client secret or local callback port.

Add the workspace server

  1. Save the JSON below as .vscode/mcp.json in your project.
  2. Open the Command Palette and run MCP: List Servers.
  3. Start local-event-hub. VS Code fetches OAuth metadata, registers itself, and opens the sign-in page.
  4. After you allow access, use Copilot Chat or agent mode to search events and RSVP.
Door 4ChatGPT

ChatGPT can connect as an MCP connector (discovery + dynamic registration) or as a custom GPT that imports the OpenAPI document.

Option A — MCP connector

  1. In ChatGPT, open Settings → Connectors (or Apps) and add a custom connector.
  2. Paste the server URL below. Use Dynamic client registration; leave client id and secret blank. If discovery fails, choose Retry discovery.
  3. Continue. Sign in to Local Event Hub and choose Allow.
  4. Enable the connector in a chat and ask it to find events or RSVP for you.

Option B — custom GPT actions

  1. Create a GPT and open Configure → Actions → Import from URL.
  2. Import the OpenAPI document at the actions URL below.
  3. Set authentication to OAuth with the authorize and token URLs below, scope events.hub, and leave the client secret empty.
  4. Save and start a conversation. The first action opens the sign-in page.
Door 5Microsoft Copilot Studio

Copilot Studio calls Local Event Hub from Microsoft’s cloud. Use the public server URL above so discovery and dynamic registration work from their network.

Add the MCP tool

  1. Open copilotstudio.microsoft.com and pick an environment whose data policy allows events.paperiq.ai (or your self-hosted origin).
  2. Create → New agent, save, then Tools → Add a tool → Model Context Protocol.
  3. Paste the server URL below. Choose OAuth 2.0 with dynamic client registration; leave client id and secret blank.
  4. Create the connection, sign in to Local Event Hub, and choose Allow.
  5. Ask the agent to search public events or RSVP the signed-in user to an event.

If a door fails, check reachability first. A GET to /mcp with no token should return 401—the server is up and waiting for OAuth. A timeout means the URL is wrong or blocked. Dismissing the browser login looks like a dead connector. More detail: docs/mcp-connector.md in the repo.