Tokens
Design tokens and theme variables
How to use this capability
Ways to interact with this capability — pick a path to jump to the relevant section below.
SDK
Call actions from Node or React apps using the Ossy SDK — typed payloads and workspace context built in.
View section ↓
MCP
Connect Cursor to http://localhost:3006/mcp when MCP tools are available for tokens.
View section ↓
HTTP
Call actions over HTTP with Bearer token authentication — create a token in Profile for scripts and automation.
View section ↓
Background tasks
Event-driven and scheduled handlers run in the background — triggered by the platform, not invoked like actions.
View section ↓
Aggregates
Domain entities and bounded-context models exposed by this capability for reads and composition.
View section ↓
Actions
Invokable intents — call directly via SDK, POST /actions, or MCP tools. This is the agent-facing surface, not background jobs.
Get
@ossy/tokens/actions/get
sdk.invoke('@ossy/tokens/actions/get', { … })POST /actions
{ "action": "@ossy/tokens/actions/get", "payload": { … } }Background tasks
Background and scheduled handlers — triggered by events or cron, not called via SDK, POST /actions, or MCP. Ids use the tasks/ path (distinct from actions/).
Get
@ossy/tokens/tasks/get
Aggregates
Domain aggregates and bounded-context entities.
Token
Token
Resource types
Structured entities and templates registered for resources.
Token
@ossy/tokens/schema/token