Play

Everything you can call from outside

Five ways in: the STYGION REST API, the same capabilities over MCP for AI assistants, the local API inside every Keystone server, Play links for your own website, and the MCP of every STYGION Panel. This page lists only what's public.

Open the OpenAPI document Open the API reference

Pick your way in

  • STYGION API

    Server status, players, releases, docs and your own account over plain HTTP.

    https://stygion.eu/api/v1

    • The OpenAPI document describes every public operation, generated from the code that answers it.
    • Errors always come back as code, message and requestId. Anything a person reads follows accept-language.
    • Calls about your own account are marked with the scope they need.
    Open the API reference

  • MCP

    The same capabilities for an AI assistant. Sign in once, and it can only do what your account can.

    https://mcp.stygion.eu/mcp/v1

    • Sign-in is OAuth 2.1 through Discord.

  • Keystone

    Every server running Keystone has its own API: scoped keys, an OpenAPI document it writes from its own routes, an event stream and MCP.

    • It runs on the server, not with us.
    • A key: keystone key new <name> <scopes>
    • For add-ons in the JVM: keystone-api
    Read the Keystone API docs

  • Play links

    A Play button for your website that installs your pack and joins your server.

    • The button page: stygion.eu/play/{token}
    • The image: stygion.eu/b/{token}.svg
    • The launcher: stygionlauncher://play/{token}
    Make a Play button

  • STYGION Panel

    Your own panel speaks MCP, under a key the owner hands out.

    • It runs on the owner's panel, not with us.
    Drive your panel over MCP

The API reference

Every public operation has its own page in the documentation: parameters, answer, scope, samples in curl, JavaScript and Python, and the same call as an MCP tool. Generated from the OpenAPI document, so it is what the API itself says it answers.

Read the reference of all 83 operations