Your rhythm.
Your way to build.

01 / YOUR DATA, A LITTLE MORE CONNECTED

A small connection.
A world of your own ideas.

Read your synced agenda, build your own workflows or connect an assistant through MCP. Personal tokens give each connection read-only or read-and-write access to your account.

02 / MAKE YOUR FIRST CONNECTION

One token.
Your little corner, connected.

1. Connect your account and sync.

   Open Solsty and connect an account. Only data synced to that account is available through API and MCP; browser-only data stays local.

2. Create a personal token.

   Go to Settings → API & MCP → Manage tokens. Name the connection, choose Read only or Read and write, select an expiry and choose Create token.

3. Copy once. Connect privately.

   The full token is shown only once. Store it securely and send Authorization: Bearer YOUR_TOKEN. Start with a read-only token and GET /resources to discover your data.

# Create a token in Settings > API & MCP > Manage tokens.
# Set SOLSTY_API_TOKEN in your private environment first.
$apiBase = 'https://api.solsty.net/v1/api'
$apiToken = $env:SOLSTY_API_TOKEN
if (-not $apiToken) { throw 'Set SOLSTY_API_TOKEN first.' }
$headers = @{ Authorization = "Bearer $apiToken" }

# Discover the available resources and writable columns.
Invoke-RestMethod "$apiBase/resources" -Headers $headers

# Read a page of your synced tasks.
$page = Invoke-RestMethod "$apiBase/records/todos?limit=100" -Headers $headers
$page.rows

# If has_more is true, continue with next_cursor.
# Download your synced account data as JSON.
Invoke-RestMethod "$apiBase/export" -Headers $headers

// Run server-side. Keep your personal token private.
const apiBase = 'https://api.solsty.net/v1/api';
const token = process.env.SOLSTY_API_TOKEN;
if (!token) throw new Error('Set SOLSTY_API_TOKEN first.');

const response = await fetch(apiBase + '/records/todos?limit=100', {
  headers: { Authorization: 'Bearer ' + token },
});
if (!response.ok) {
  throw new Error('Request failed: ' + response.status);
}

const { rows, has_more, next_cursor } = await response.json();
// Use rows in your workflow. If has_more is true, pass next_cursor
// as the cursor query parameter to retrieve the next page.

03 / THE ESSENTIALS

A map of what’s here.

All paths below are relative to https://api.solsty.net/v1/api and require a personal API token.

Read a page, then the next.

Record lists and sync pulls accept limit from 1 to 500 (default 100). While has_more is true, continue with next_cursor. Use each cursor only with its original endpoint. For the first sync pull, use since=1970-01-01T00:00:00Z.

Write with the sync contract.

Push accepts up to 500 items in an operations array. Each item carries id, table, rowId, op and queuedAt, plus payload for an upsert. IDs are UUIDs, the timestamp is RFC3339, and the operation is upsert or delete.

Discover writable columns with /resources first. Upserts require a full row, not a partial PATCH; preserve the record ID and natural key on updates. Each batch is atomic. Deletions leave tombstones and cannot be undone with an upsert.

04 / YOUR ASSISTANT, MEET YOUR DAY

Connect a compatible MCP client to Solsty using Streamable HTTP and a personal token. Choose read-only access to browse your agenda, or read-and-write access to allow changes.

✳Your assistant

↔

⌘MCP

↔

Solsty

1. Create a token in Solsty.

   Follow the token steps above. Use a separate named token for each connection so you can revoke them individually.

2. Add a remote MCP server.

   Select Streamable HTTP, enter https://api.solsty.net/mcp and add an Authorization header containing Bearer YOUR_TOKEN. Your client must support custom HTTP headers; OAuth-only connections are not supported.

3. Connect and discover the tools.

   Run your client’s connection check, then try list_resources or list_records with table: "todos". Read-only tokens expose four tools; write tokens also expose push_changes.

{
  "url": "https://api.solsty.net/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_SOLSTY_API_TOKEN"
  }
}

These are connection fields, not a universal client configuration file. Place them in the remote-server section your client expects. No local Solsty package or legacy /sse connection is needed.

05 / A FEW USEFUL DETAILS

You keep the keys.