AttendBeacon

com.attendbeaconPublished by attendbeacon.comOfficial publisherv1.0.0Updated Nov 1, 2026

Event platform: events, tickets, attendees, agenda, check-in, speakers and sponsors.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote AttendBeacon MCP endpoint that lets an assistant work with event data: events, tickets, attendees, agenda, check-in, speakers and sponsors.

What you can do
  • Work with events and their tickets
  • Manage attendees and check-in records
  • Handle agenda items, speakers and sponsors
  • No tool list is published, so the exact actions available are not documented; expect read and possibly write access to the event platform's records.
When to use it
Useful when you run events on AttendBeacon and want an assistant to look up or update event details, attendee and ticket information, agendas, check-in status, speakers or sponsors without switching to the web app.
Requirements
A remote MCP endpoint at attendbeacon.com over streamable HTTP. OAuth authentication is required, so you need an AttendBeacon account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to your AttendBeacon account, so the assistant can reach whatever that account can see. Because no tool list is published, it is unclear whether tools can create, change or delete events, tickets or attendee records; check permissions before connecting. Attendee and ticket data is personal data sent to the model provider.

Installation

In SourceWeft

  1. Open AttendBeacon in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.attendbeacon%2Fattendbeacon/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "attendbeacon": {
      "type": "http",
      "url": "https://attendbeacon.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 31, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.