Piia MCP Server

AI identity layer — syncs who you are across Claude Code, Codex, Cursor and any MCP tool.

Local serverstdioPython

What is the Piia MCP Server?

AI identity layer — syncs who you are across Claude Code, Codex, Cursor and any MCP tool.

What the server does

Tell AI once who you are, how you work, and what "good" means. Claude Code, Codex, Cursor, Windsurf, and other MCP-compatible tools can start from the same AI work identity layer — local files you own, no cloud account, no hidden memory you cannot inspect.

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
CodexMCP over stdio
CursorMCP over stdio
HermesMCP over stdio
OpenClawSOUL.md / MEMORY.md / USER.md import and export
WindsurfMCP over stdio
ClineMCP over stdio
AugmentMCP over stdio
ZedMCP over stdio
TraeMCP over stdio
get_user_contextStartup — Load identity + knowledge at session start (supports token_budget for context size control)
wrap_up_sessionSession end — Save insights + sync at session end
memory_storeWriteback — Unified write endpoint: routes to add_lesson / add_decision / add_playbook by kind
add_lessonStore a reusable lesson learned
add_decisionRecord a key decision with reasoning
add_playbookRecord an operational playbook (multi-step procedure with trigger keywords)
search_knowledgeRetrieval — Search lessons, decisions, and playbooks (supports filters_json for domain/tier/date filtering)
get_relevant_knowledgeFind knowledge relevant to current project
get_recallReturn one structured identity + recent activity + relevant knowledge recall payload
get_knowledge_historyRead one item's revision history (superseded snapshots; exact by-version lookup)
get_identity_cardOwner-gated export: write and return a Markdown identity card for non-MCP tools
update_identityUpdate profile, preferences, or quality standards
get_project_contextRead a saved project snapshot
save_project_snapshotPersist project state for future sessions
get_recent_contextRecover lost session context after restart
get_daily_logRead a human-friendly project timeline for a day
get_resume_briefBuild a cross-session/cross-tool resume brief
doctorRun memory system self-diagnosis
register_toolOptional local integration governed write: register a local tool, runtime, or CLI to the environment map
find_toolOptional local integration: look up a registered local tool by name
list_toolsOptional local integration: list registered local tools (optionally filter by category)
save_agent_contextSave AI session checkpoint (also runs automatically)
list_agent_sessionsBrowse saved session records across tools
refresh_quick_contextRefresh local quick_context.md snapshot for offline/cross-tool use
get_identity_facetsRead identity facets via facet: profile, preferences, trust_boundaries, work_style, quality_standards, domains, or all
user_portraitaction: get / save / compare the AI-maintained user portrait
preview_context_governanceAdvanced owner-gated preview: build safe-context, freshness/conflict, replay, or evidence proposals without applying changes
get_playbooksPlaybook reads via mode: list, get (full content), recent, management (incl. archived/deleted metadata)
manage_playbookPlaybook lifecycle via action: update, archive, delete, restore (mutations stay confirm-gated)
playbook_executionGuided execution via action: prepare a step plan, update_step, status rollup (passive reference; no auto-execution)
get_lessonsList reusable lessons learned
get_decisionsList key decisions; thread_seed_id / history_question reconstruct decision threads and revision history
get_knowledge_inheritanceBuild cross-project knowledge starter pack
list_projectsList saved project snapshots
extract_session_insightsExtract lessons and decisions from session text
ingest_notesParse free-form notes into structured knowledge
update_knowledgeUpdate a lesson or decision by ID
archive_knowledgeArchive a lesson or decision by ID
confirm_knowledgeOwner-only confirmation stamp via human, test, or anchor provenance
onboard_repoOwner-only repo scan: create staging repo-fact candidates from anchors
onboard_acceptOwner-only accept: validate a candidate anchor and promote it to verified
check_anchorsOwner-only revalidation for existing anchor-backed facts
merge_knowledgeMerge a duplicate into the primary item
manage_relationaction: link / unlink — manage typed relations between knowledge items (decision threads)
explore_knowledgeKnowledge graph exploration via mode: related, similar, merge_candidates
get_knowledge_overviewKnowledge digest, health report, stale checks
get_stale_knowledgeList items that need review
review_stagingStaging review hub via action: list pending, batch decisions, review_item, apply_text review results
export_knowledge_reportOwner-gated export: write a readable Markdown knowledge report
request_outline_reviewOwner-gated export: generate an interactive local HTML review page
export_engramOwner-gated export: write a full backup (format="openclaw" for OpenClaw-compatible files)
import_engramOwner/admin import: use dry_run=True first for a metadata-only merge/conflict preview (format="openclaw" supported)
read_web_contentFetch a user-provided URL: prefers a local sidecar if running, otherwise uses the self-contained built-in reader (pip install "piia-engram[reader]")
get_audit_logGet recent audit log entries
start_projectStart a project with inherited knowledge
get_permission_profileView all callers' trust levels and access boundaries
manage_caller_trustOwner/admin action: grant / revoke a caller's trust level
export_feedback_reportMaintainer feedback: generate an anonymous aggregate feedback report

How to install the Piia MCP Server

{
  "mcpServers": {
    "piia-engram": {
      "command": "piia-engram-mcp",
      "args": [
        "--transport",
        "stdio"
      ]
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Example prompts to try

  • “Use Piia to Codex.”
  • “Use Piia to Cursor.”
  • “Use Piia to Hermes.”

Frequently asked questions

AI identity layer — syncs who you are across Claude Code, Codex, Cursor and any MCP tool. Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.