Labsco
MCP SERVER

PromptX

by Deepractice ↗

Give an agent named roles it can step into, each carrying its own knowledge and a memory that outlives the chat.

Prompts, Skills & Instruction Packs✓ Official source
Summary
A role the agent can pick up again tomorrow.

What it takes off you is the re-briefing. The persona, the working rules and whatever the role learned last time live on the role rather than in your prompt, so the next conversation starts by recalling them instead of pasting them back in.

What it is

A role and memory layer. Roles are declared at system, project or user level; activating one loads its persona, principles and knowledge, and what it learns is written into a memory network the same role reads back at the start of the next conversation.

What you get
  • The available roles and callable tools listed by where they come from — built in, project level, or your own
  • A role activated into the session, bringing its persona, working principles, knowledge and memory network with it
  • Knowledge written back to the active role's memory, and recalled from it by query rather than re-pasted
  • A project binding that registers the workspace root, which is what makes project-level roles and tools visible at all
  • A runtime for ecosystem tools, driven by a YAML document naming the tool, the mode and the parameters
  • Custom tools run inside a sandbox that resolves their declared dependencies itself and loads CommonJS and ES Module packages through one interface
  • In the desktop client, the memory made inspectable: the network drawn as a graph, individual entries edited or deleted, and the retrieval paths browsable
Requirements

Three ways to run it, and they differ in what you have to install. The desktop client for macOS or Windows runs the server for you and exposes streamable HTTP at http://127.0.0.1:5203/mcp, with no configuration beyond pasting that URL into your client; on Windows its agent feature also wants Git for Windows. With Node already on the machine, npx runs @promptx/mcp-server over stdio instead. For a server, the Docker image publishes the same port and wants ~/.promptx mounted, which is where roles and memory live. Project-level roles and tools stay invisible until the workspace root is bound, so that call comes before discovery whenever you have a project open.

Setup effort

One command — npx -y @promptx/mcp-server