| name | setup-mcp |
| description | Connect OpenClaw or other AI tools to pREST MCP safely. Use when setting up prest-mcp, /_mcp, or read-only agent database access. |
Set up AI / MCP access for pREST
When to use
- User wants an agent to work with a pREST-backed PostgreSQL API
- User asks for MCP configuration with pREST
- User wants a read-only local AI-safe setup
Important: what this plugin does not do
This plugin provides guidance only. It does not run pREST or implement MCP tools. pREST exposes the actual HTTP MCP endpoint at /_mcp. The prest-mcp adapter bridges stdio MCP clients to that HTTP endpoint.
Ask first
- Where is pREST running? (local binary, Docker, remote URL)
- Is the goal schema exploration, querying via
/_QUERIES, MCP tools, or all of the above?
- Can they create a read-only Postgres role?
- Does their MCP client need stdio (use
prest-mcp) or can it connect to HTTP /_mcp directly?
Recommended approach
A. pREST HTTP MCP (preferred)
pREST exposes MCP at /_mcp on the running instance. Point HTTP-capable clients at:
http://localhost:3000/_mcp
Use authentication (JWT, token, or network isolation) in every non-local deployment.
B. stdio bridge with prest-mcp
For stdio MCP clients (including many OpenClaw embedded setups):
brew install prest/tap/prest-mcp
PREST_MCP_URL=http://localhost:3000/_mcp prest-mcp
Environment variables:
