SwarmTix

io.github.nichovskiPublished by GitHub account nichovskiv1.0.0Updated Oct 26, 2026

Event ticketing: create and publish events, read orders, attendees and sales analytics.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for SwarmTix event ticketing that lets an assistant create and publish events and read orders, attendees and sales analytics.

What you can do
  • Create and publish events on SwarmTix.
  • Read orders placed for events.
  • Look up attendee information.
  • Review sales analytics for events.
When to use it
Useful when you manage events on SwarmTix and want an assistant to draft or publish listings and pull order, attendee or sales figures without switching to the web dashboard.
Requirements
A remote streamable HTTP endpoint at swarmtix.com; no local package or runtime needed. Authentication is OAuth and required, so a SwarmTix account with access to the relevant events is needed.
Before you install
The server can create and publish events, which changes public-facing listings, and it exposes order and attendee data, which is personal customer information. Review anything the assistant publishes before it goes live and be mindful of who can see attendee details.

Installation

In SourceWeft

  1. Open SwarmTix 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/io.github.nichovski%2Fswarmtix/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": {
    "swarmtix": {
      "type": "http",
      "url": "https://swarmtix.com/mcp/v1"
    }
  }
}

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 17, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • 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.