STYGION Documentation Search the docs

Starts joining another provider to the account that asked

POST

/api/v1/account/links/begin

Sign-in: Token with a scope
Scope: identity.read
MCP tool: identity.linkProvider

Parameters

None.

Request body

Field	Type and meaning
`provider` required	`string` One of discord / microsoft / github / google.
`surface`	`string` site or workspace. Left out it is the site.

Response 200

Field	Type and meaning
`state` always	`string` Hand this back when they return.
`url` always	`string` Where to send the person to sign in.

Errors

Status	Type and meaning
`400`	The request was not understood.
`401`	Sign in and try again.
`404`	There is nothing here, or nothing you may see.
`429`	Too many requests.
`500`	Something on our side went wrong.

Every error comes back as { code, message, requestId }. Errors

Request

# Acts on the signed-in account (scope identity.read). From outside our apps, call it over MCP.
curl -X POST https://stygion.eu/api/v1/account/links/begin \
  -H 'content-type: application/json' \
  -d '{
    "provider": "{provider}"
  }'

The same over MCP

An assistant connected to the address below calls the tool identity.linkProvider: the same capability, the same answer.

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

Not an official Minecraft product. Not approved by or associated with Mojang or Microsoft.