Developer · Local MCP server

Piia Engram

Local-first AI identity for MCP coding tools. Lessons, decisions, and context you control.

Visit Piia Engram's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.Patdolitse/piia-engram
Version
4.21.2
Status
Active
Category
developer
Transport
stdio (local process)
Package
PyPI
Published
2026-09-26
Updated
2026-09-26
Publisher
Patdolitse (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/Patdolitse) · how
Website
github.com/Patdolitse/piia-engram
Repository
github.com/Patdolitse/piia-engram
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
PyPIruntime: uvxpiia-engram4.21.2stdioENGRAM_MCP_STARTUP_SYNC, ENGRAM_TOOLS, PYTHONIOENCODING

How to connect Piia Engram

Piia Engram runs locally from a Python package published to PyPI: piia-engram version 4.21.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx piia-engram. It reads these environment variables: ENGRAM_MCP_STARTUP_SYNC, ENGRAM_TOOLS and PYTHONIOENCODING; set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "piia-engram": {
      "command": "uvx",
      "args": [
        "piia-engram"
      ],
      "env": {
        "ENGRAM_MCP_STARTUP_SYNC": "<value>",
        "ENGRAM_TOOLS": "<value>",
        "PYTHONIOENCODING": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
PhysboundPhysical Layer Linter: validates RF and radar calculations against hard physical limits.Local · stdioPyPI: physbound
Physical Capability CloudDiscover, hire, and verify real-world physical capability through MCP.Remote · HTTPLive check: ✓ handshakecapability.network
Pi-hole MCP ServerManage Pi-hole v6: DNS blocking, domains, clients, query analysis, DHCP, and multi-instance sync.Local · stdioOCI image (Docker): ghcr.io/hexamatic/pihole-mcp:0.9.0
PiboxSelf-hosted MCP server: pi-coding-agent tools (run_prompt, file ops) over streamable HTTP.Local · HTTPOCI image (Docker): docker.io/psyb0t/pibox:v0.18.4
PikeletSearch self-contained.pikelet knowledge artifacts over MCP - no vector DB, no embedding API.Local · stdionpm: pikelet
PinAppAIVisual website feedback your coding agent applies: pin change requests on the live site over MCP.Remote & Local · HTTP, stdioLive check: ✓ handshakemcp.pinappai.com
PinbridgePublish and schedule Pinterest pins from any MCP client. Token refresh and retries handled.Remote · HTTPLive check: sign-in requiredmcp.pinbridge.io
PincerSecure grip for your agent's secrets - security-hardened MCP gateway with proxy token architecture.Local · stdionpm: pincer-mcp