Shared memory for
Cursor.
Keep project decisions available across coding sessions, and share them with your other agents.
Add the server by URL
In Cursor's MCP settings, add the endpoint. Cursor connects to a Streamable HTTP server directly; if your build has no URL support, use the mcp-remote form from the Claude page instead.
{ "mcpServers": { "priostack-acn": { "url": "https://priostack.com/mcp" } } }Once connected, the noetic tools appear in the agent's tool list. Listing them needs no API key.
Keep one agent across sessions
Over MCP the model itself makes the calls, and it remembers nothing between chats. Without a saved identity, every new chat registers a new agent with an empty memory. Give it one agent and one space to come back to:
- Register once. Run the call below and save the token: it is shown once. An agent registered with curl, an SDK or an MCP client is permanent. You can also create and keep an agent on /start: it is then bound to your Priostack account, you can reveal or rotate its token from your account, and its hosting and reads are paid from your credits (see pricing).
- Create the space once. In a first chat, ask Cursor to connect with the token and call
noetic.create_space, and note the space id it returns. - Connect in every chat.
noetic.connecttakes the token and returns asessionId. Every other tool takes thatsessionId, not the token. Put the instruction below in a Cursor rule that is not committed to your repository (a user rule, not a file under .cursor/rules) so each chat starts this way.
curl -s https://priostack.com/mcp -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"noetic.register","arguments":{"displayName":"cursor-agent"}}}'
# -> data.token (shown once), data.agentId, data.accountIdPriostack memory: at the start of each conversation, call noetic.connect
with {"token": "<your agent token>"} and keep the sessionId it returns.
Pass that sessionId to every other noetic tool. Project memory lives in
space "<your space id>": save decisions there with noetic.store and look
them up with noetic.fetch, using one word as the query.noetic.rotate_token returns a new token and ends the agent's other sessions, and an agent bound to your account can be rotated from your account.Save one useful fact
Begin with a decision you otherwise repeat: a review rule, a project convention or an approved policy. Store a decision as a declaration and a measured fact as an observation, then retrieve it by a word it contains. Stored objects cannot be edited: store a newer fact and say which one it replaces.
Questions
Is a Priostack account needed?
No. The agent registers itself in one call and gets its own token. Create it from your account instead when you want to manage its token there.
Can I use the same memory from Claude Desktop?
Yes. Connect both clients with the same agent token, or give the second agent a grant.
What if my Cursor version cannot add a URL server?
Use the mcp-remote bridge configuration shown on the Claude page; it works with any client that launches a local command.
Let your next agent start with context.
Try the memory demo, then connect the tools you already use.
The endpoint is live. Example ids, keys and outputs on this page are samples.