Your agenda, connected on your terms.

Start with a question you already ask

Think about a small job you repeat. “What is still on my list?” “Which tasks could I group together?” “Can I keep a separate copy of my synced data?” Choose one useful result before you start connecting tools.

For a first experiment, reading your task list is a good place to begin. You can see how the connection behaves without giving it permission to change anything. Keep the first version small enough to understand from end to end.

Choose the connection that fits your tool

The HTTP API lets your own scripts and applications request Solsty data. You send a request to an endpoint and receive JSON that your code can work with. The developer guide includes PowerShell and JavaScript examples to get you started.

MCP gives a compatible assistant a set of tools for working with your agenda. It can discover available resources, read records and pull changes. With a read-and-write token, it can also submit changes. Your assistant decides how to use those tools in response to your instructions.

Solsty’s MCP connection uses Streamable HTTP and a Bearer token. Your client needs to support a remote MCP URL and a custom Authorization header. Clients that only offer an OAuth sign-in flow cannot use this connection yet. No local Solsty MCP package is required.

Give each connection its own token

In the app, open Settings → API & MCP → Manage tokens. Give the connection a recognizable name, such as “My weekly review,” choose Read only and select an expiry. Copy the token when it appears; the complete value is shown only once.

Treat that token as a credential. Store it in your client’s credential settings or supply it to your own script through an environment variable. Keep it out of shared notes, public repositories and URLs.

A separate token for each connection makes it easier to recognize and revoke access later. If a tool no longer needs your agenda, return to the same screen and choose Revoke.

Try a review before you allow changes

Ask your connected assistant to list your open tasks and suggest a few groups. Or use a script to read the tasks endpoint and print the results. Check those results against your agenda and see whether the connection is useful to you.

One small connection can be enough.

If you later want a tool to create or update tasks, give that connection a read-and-write token deliberately. Start with a clearly named test task and inspect the result in Solsty. Scripts that write data should follow the documented sync format: an upsert sends a complete writable row, so sending only one changed field is not a partial update.

Know what the connection can see

The API and MCP work with data that has reached your Solsty cloud account. Changes still waiting on an offline device will not appear until that device reconnects and syncs. If your agenda is only stored locally, connect a cloud account before using these integrations.

API and MCP data access are free and do not use Solsty AI credits. Your chosen assistant or hosting provider may have its own charges and data policies. Solsty’s own future AI features are separate and are not available yet.

When you are ready, the developer guide has the live addresses, connection fields, permissions and request limits. Begin with one connection that makes your day a little easier, then decide what deserves a place beside it.