STYGION Documentation Search the docs

Finishes signing in and hands back a session

POST

/api/v1/auth/complete

Sign-in: No scope
Scope: None
MCP tool: identity.completeSignIn

Parameters

None.

Request body

Field	Type and meaning
`address`	`string`
`code` required	`string`
`device`	`string`
`state` required	`string`

Response 200

Field	Type and meaning
`accountId` always	`string`
`linked`	`boolean` Whether this joined a provider to an account that was already signed in.
`new` always	`boolean` Whether this sign-in created the account.
`session` always	`string` The session token. Shown once

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

curl -X POST https://stygion.eu/api/v1/auth/complete \
  -H 'content-type: application/json' \
  -d '{
    "code": "{code}",
    "state": "{state}"
  }'

The same over MCP

An assistant connected to the address below calls the tool identity.completeSignIn: 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.