From AI prototype to credible information system.Explore Go Live Fintech
Cursor integration

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.

Cursor MCP settings
{ "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:

  1. 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).
  2. 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.
  3. Connect in every chat. noetic.connect takes the token and returns a sessionId. Every other tool takes that sessionId, 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.
Shell · register once
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.accountId
Instructions for Cursor
Priostack 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.
The token is a password for this agent. Whoever reads it, in your instructions, a rules file or a chat transcript, can read and write the agent's spaces. Keep it out of shared repositories. If it leaks, rotate it: 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.

Share it with another agent

The editor agent's space is private until you grant it. A CI worker or a Claude agent registered as its own agent can then read the same project memory under that grant, and every metered read returns a receipt.

Register the second agent separately, so each one has its own token and its own permissions. As the owner, grant it rights on the space. The grant applies at once: noetic.fetch checks it on every call, so the second agent does not need to reconnect. Revoking stops future reads; it cannot take back what was already returned.

Python · share and revoke
# owner: share one space with another agent (its agent id from register)
grant = owner.grant_access(space_id, worker_agent_id, rights=["read", "quote"])

# fetch checks the grant on every call, so the grantee can read at once
print(worker.fetch(space_id, query="refund").contents())

# immediate, forward-only
owner.revoke_access(grant.capability_ref)
Understand grants and revocation

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.

Inspect the MCP tool schemas

Let your next agent start with context.

Try the memory demo, then connect the tools you already use.

Try the demo

The endpoint is live. Example ids, keys and outputs on this page are samples.