SimpleTicket Backoffice

online.ticketplatform.apiPublished by api.ticketplatform.onlineOfficial publisherv1.0.1Updated Oct 24, 2026

SimpleTicket merchant backoffice: events, ticket sales, transactions, mail and reporting.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for the SimpleTicket merchant backoffice, giving an assistant access to events, ticket sales, transactions, mail and reporting.

What you can do
  • Manage events and their ticketing setup in the merchant backoffice
  • Review ticket sales and transactions
  • Handle mail sent from the backoffice
  • Produce and consult reporting on sales and activity
  • No individual tools are documented, so exact actions depend on the live endpoint
When to use it
Useful for merchants already running SimpleTicket who want an assistant to look up or work with their events, sales, transactions and reports without switching to the backoffice UI.
Requirements
A remote streamable HTTP endpoint at api.ticketplatform.online; OAuth authentication is required, so a SimpleTicket merchant account with the appropriate access is needed. No environment variables or headers are declared.
Before you install
It operates on a live merchant backoffice, so actions may change events, sales records or send mail; confirm before anything that writes or sends. Access is granted through OAuth to a business account, so review the scopes requested. No tool list is published, so verify what it can do before relying on it.

Installation

In SourceWeft

  1. Open SimpleTicket Backoffice 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/online.ticketplatform.api%2Fbackoffice/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": {
    "simpleticket-backoffice": {
      "type": "http",
      "url": "https://api.ticketplatform.online/mcp?company=STNL"
    }
  }
}

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.1LatestOct 16, 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.