prest-mcp-guidance

name	prest-mcp-guidance
description	Guidance for connecting AI tools and MCP clients to pREST safely via /_mcp and prest-mcp. Apply when configuring MCP for pREST workflows.

pREST MCP guidance

When helping users connect pREST to AI tools:

• This plugin does not implement MCP tools. pREST exposes HTTP MCP at /_mcp. The prest-mcp adapter bridges stdio MCP clients to that HTTP endpoint.
• Prefer read-only database users for MCP/API exploration.
• Ask whether pREST is running locally, in Docker, or remotely before generating config.
• Generate local examples before production examples.
• For stdio MCP clients: brew install prest/tap/prest-mcp then PREST_MCP_URL=http://localhost:3000/_mcp prest-mcp.
• Required adapter env var: PREST_MCP_URL. Optional: PREST_MCP_TOKEN, PREST_MCP_TIMEOUT_MS.
• MCP Registry name: io.github.prest/prest.
• For HTTP-capable clients, point directly at /_mcp on the pREST base URL with appropriate auth.
• Explain which URL the user needs (pREST base URL, health /_health or readiness /_ready, MCP /_mcp, and query paths /_QUERIES/...).
• Never suggest exposing MCP endpoints or database credentials publicly without authentication.
• Prefer restricted [expose] and [access] settings for any AI-facing deployment.
• Postgres read-only MCP is a fallback when prest-mcp or HTTP MCP is unavailable; prefer pREST MCP so JWT/ACL apply.