Engraphy MCP Server

Self-hosted MCP memory server: a typed knowledge graph on Postgres 16 and pgvector.

Local serverstreamable-http

What is the Engraphy MCP Server?

Engraphy is an MCP integration. Self-hosted MCP memory server: a typed knowledge graph on Postgres 16 and pgvector.

Packages and local setup

The published oci package is ghcr.io/devon-clarkk/engraphy:0.3.0. Its declared MCP transport is streamable-http.

The package declares ENGRAPHY_DATABASE_URL (required): libpq connection string for a Postgres 16 database with the pgvector extension, reached as the non-superuser engraphy_app role. Required: the server refuses to start without it, and refuses to start if the schema is behind (run engraphy-admin migrate first).; ENGRAPHY_BIND_HOST: Interface the server binds. Containers reach their own loopback only, so a published container sets 0.0.0.0 and puts the boundary at the port publication and the reverse proxy.; ENGRAPHY_BIND_PORT: Port the server binds inside the container, matching the port in the transport URL..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.3.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related databases MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
ENGRAPHY_DATABASE_URLlibpq connection string for a Postgres 16 database with the pgvector extension, reached as the non-superuser engraphy_app role. Required: the server refuses to start without it, and refuses to start if the schema is behind (run engraphy-admin migrate first).Yes
ENGRAPHY_BIND_HOSTInterface the server binds. Containers reach their own loopback only, so a published container sets 0.0.0.0 and puts the boundary at the port publication and the reverse proxy.Optional
ENGRAPHY_BIND_PORTPort the server binds inside the container, matching the port in the transport URL.Optional