Agent Setup
Connect an Agent to TokST Cloud MCP for durable memory, shared context, and knowledge governance. Cloud MCP is the standard memory path. The optional CLI Runtime connects devices and Agent bindings for Sessions, explicit Tasks, Communication, and diagnostics.
Connect Cloud MCP
Configure an OAuth-capable MCP client with the public endpoint:
{
"mcpServers": {
"tokst": {
"type": "streamable-http",
"url": "https://api.tokst.com/mcp"
}
}
}
The client opens TokST in a browser for approval. After approval, the Agent can use the complete Cloud MCP toolset for memory, context, knowledge bases, workspace governance, files, and account status.
Clients that use static MCP configuration can authenticate with a dedicated API key. Create one in Dashboard API Keys, store it in the client's protected configuration, and revoke it when the client no longer needs access.
{
"mcpServers": {
"tokst": {
"type": "streamable-http",
"url": "https://api.tokst.com/mcp",
"headers": {
"Authorization": "Bearer tk_live_your_api_key"
}
}
}
}
Add the TokST Skill
Copy this message into an Agent that supports Skills:
Read https://tokst.com/skill.md. Connect to TokST Cloud MCP at
https://api.tokst.com/mcp, complete authorization, search relevant context before
substantial work, and save only confirmed long-term information.
The Skill defines when to search, write, update, and archive durable knowledge. It is MCP-only and does not manage Runtime Sessions, Tasks, or Communication.
Advanced: Connect Local Agent Endpoints
Use the optional device tool when you want this computer to run created Agent bindings, participate in Communication, capture supported local Sessions, or execute Dashboard-assigned Tasks.
tokst start
tokst auto on --agent all
tokst status
tokst doctor
start connects the Runtime device and registers its available adapters. auto on explicitly installs and enables automatic-memory bridges. status reports device, binding, model, WSS, queue, Task, and Communication health.
doctor reports connection and configuration problems with recovery actions.
Verify the Connection
- Open the MCP client and confirm that TokST tools are available.
- Ask the Agent to search existing context before a substantive task.
- Ask it to save one confirmed, durable fact or decision through TokST MCP.
- Open Memories to confirm the result.
Use Cloud MCP for tool details, the Skill guide for Agent behavior, and CLI reference for device operations.
Troubleshooting
| Situation | Action |
|---|---|
| The client shows an authorization request | Complete the browser approval, then reconnect the MCP client. |
| The client has static configuration only | Create a dedicated API key and configure it as a Bearer token. |
tokst: command not found | Install the standalone CLI for local endpoints, then open a new terminal. |
| MCP tools do not appear | Confirm the URL is https://api.tokst.com/mcp and inspect the client's MCP log. |
| A local endpoint is unavailable | Run tokst doctor, then tokst auto on --agent <name> after resolving the reported condition. |