Welcome to nthbouncer
Introduction
nthbouncer gives agents and teammates access to PostgreSQL or MySQL. They work from real tables and columns for more accurate results, without putting database passwords on every laptop. Each pool holds the credential and admits in-flight queries up to your concurrency limit.
Agents connect at https://nthbouncer.com/mcp.
There is no token to paste. Scripts call the pool hostname on
*.nthpool.cloud or take a concurrency lock. HTTPS APIs
use the same pool model when a vendor or your own service has a hard shared
limit.
nthbouncer is not an API gateway and not an LLM gateway. Proxy when you want nthbouncer to call upstream. Use locks when you front a public endpoint or keep the origin client in your process. For SaaS origins with account-level concurrency limits, see the knowledge base.
How it fits together
- Create a pool and point it at one or more allowed origins.
- Choose managed custody (nthbouncer holds and signs upstream credentials) or pass-through (your client sends upstream auth; nthbouncer relays it).
- Mint a pool key and call
https://‹pool›.nthpool.cloud/...with that key. - Tune concurrency, queue depth, RPM, retries, and optional response cache on the pool's Concurrency settings.
- When several pools share one origin concurrency limit, put them on a Capacity budget. Fixed caps each pool at its allocation. Auto keeps reserved pins local and moves float toward load.
- Use the pool's Metrics tab for admit/queue/reject proof. Billing remains the place for request allowance.