Priostack
MCP memory server

An MCP memory server your agents connect to by URL.

Priostack's Agent Context Network is a standards MCP server on the Streamable HTTP transport. Any MCP client connects to one endpoint, discovers its tools, and gets persistent, permissioned, shared context: memory that stays put across sessions and is shared only with the agents you allow.

Endpoint: https://priostack.com/mcpTransport: Streamable HTTPTools: 40, discoverable
01

Connect Claude Desktop or Cursor

Add the server to your client's mcpServers. Claude Desktop reaches a remote server through the mcp-remote bridge; recent Cursor connects by URL directly. The client calls initialize, lists the tools, and your agent can register itself, create spaces, store and fetch context, and manage grants from inside the conversation.

claude_desktop_config.json
{
  "mcpServers": {
    "priostack-acn": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://priostack.com/mcp"]
    }
  }
}
Cursor MCP settings
{ "mcpServers": { "priostack-acn": { "url": "https://priostack.com/mcp" } } }
02

Discover the tools yourself

The endpoint answers the three standard methods. initialize negotiates the protocol version, tools/list returns the catalogue, tools/call runs a tool. Every tool call returns the same envelope: ok, an outcome, and data.

shell
curl -s https://priostack.com/mcp -H 'Content-Type: application/json' -H 'Accept: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | jq '.result.tools | length'   # 40
03

What kind of memory it is

Not a scratchpad the model overwrites, and not a transcript. An agent registers once and gets its own account; it creates spaces, stores typed context in them, and reads it back with noetic.fetch. Other agents see a space only through a grant the owner controls, and every metered read leaves a receipt. The same server serves an agent in Cursor, one in a Python worker, and one on a different model.

04

Use it without an MCP client

The transport is plain HTTP, so a script can drive the same tools with curl or the Python SDK. The register tutorial walks through the two calls that take an agent from nothing to a live session.

shell
export ACN="https://priostack.com/mcp"
curl -s "$ACN" -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
  "params":{"name":"noetic.register","arguments":{"displayName":"my-agent"}}}'
# -> data.token (shown once), data.agentId, data.accountId
05

Questions people ask

Which MCP clients work?
Any client that speaks the Model Context Protocol over Streamable HTTP, including Claude Desktop (through mcp-remote) and Cursor. The /acn/rpc path remains a working alias for older configurations.

Is a session or API key needed to discover tools?
No. initialize and tools/list are open. Calling tools that touch a space needs a session, which an agent gets by registering (one call, no dashboard) and connecting with its token.

Does the server stream?
Yes. A POST is answered as JSON or, for clients that ask for it, as a server-sent event, and GET opens the server-to-client event stream the transport defines.