
pREST
io.github.prestPublished by GitHub account prestv0.1.3Updated Oct 24, 2026
Stdio MCP adapter bridging AI clients to pREST’s HTTP /_mcp endpoint for PostgreSQL APIs.
Overview
A stdio bridge that lets MCP clients reach a running pREST instance's HTTP MCP endpoint for PostgreSQL APIs.
- What you can do
- This adapter is a small transport bridge: it speaks newline-delimited JSON-RPC over stdio to the MCP client and forwards requests by HTTP POST to a pREST instance's /_mcp endpoint. It does not introspect schemas, generate SQL, or implement MCP tools itself; those capabilities live in pREST. Logs are written only to stderr.
- When to use it
- Use it when your MCP client or AI IDE only supports stdio servers but you want to work against a pREST instance that already exposes an HTTP MCP endpoint. It is not useful on its own without a running pREST deployment.
- Requirements
- A running pREST instance with the /_mcp route available, plus the required environment variable PREST_MCP_URL pointing at that endpoint. Optional: PREST_MCP_TOKEN when pREST auth is enabled, and PREST_MCP_TIMEOUT_MS (default 30000). Runs as a local process; can be installed from source with Go 1.26+ or pulled as an OCI image.
Installation
In SourceWeft
- Open pREST in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
pREST MCP Adapter
Official stdio adapter for pREST’s HTTP MCP endpoint.
This adapter lets MCP clients that require stdio connect to a running pREST instance exposing an HTTP MCP endpoint at /_mcp.
The adapter is a tiny transport bridge. It does not introspect schemas, generate SQL, or implement MCP tools. Those live in pREST.
Requirements
- A running pREST instance with the
/_mcproute available - Go 1.26+ (to build from source)
Environment variables
Install
From source
Docker / OCI
Local usage
With token
Docker usage
MCP client configuration
Cursor
Add to your MCP settings (e.g. .cursor/mcp.json):
Claude Desktop
Add to claude_desktop_config.json:
Generic MCP client
Any client that can launch a stdio MCP server:
Protocol messages are newline-delimited JSON-RPC on stdin/stdout. Logs go only to stderr.
Security recommendation
Use a read-only PostgreSQL user for AI/MCP workflows unless write access is explicitly required.
Do not expose unauthenticated MCP endpoints publicly.
Prefer local or private-network pREST MCP endpoints.
When pREST auth is enabled, set PREST_MCP_TOKEN to a valid JWT.
Development
License
MIT — see LICENSE.
Source: README.md at commit f35ab01
Tools
0Version history
1- v0.1.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts