Context from production
Connect once at https://nthbouncer.com/mcp and let agents work from live tables and columns for more accurate answers.
agent session
LiveDatabase password never left the pool2/4 in flight
One shared layer
Put every agent and teammate on the same layer without sharing the database password. Revoke one person without rotating it for everyone.
Safe for production
Keep every caller within the concurrency limit you set. Anything above the limit waits or goes async.
Keep answers tied to production under one concurrency limit
One path to the data source for every caller.
Agents, teammates, and jobs share one path to the database, so answers come from production tables while traffic stays within the limit you set.
Live admission path
Callers
AgentMCP client
Backend APIService client
Data syncQueued job
NTHBOUNCER POOL
production
Requests in flight
3/ 4
Hard limit
Limit = 4
AgentIN FLIGHT
Backend APIIN FLIGHT
Data syncIN FLIGHT
AvailableOPEN SLOT
OVER LIMIT
Anything above the limit waits or goes async. Your origin never sees a fifth request.
ORIGIN
PostgreSQL, MySQL, or API
Credential never reaches callers
How the layer works
Real tables for more accurate results
Password on the laptop
Laptop config
postgresql://nth:[email protected]:5432/warehouse
Database password in the agent config
postgresql://nth:[email protected]:5432/warehouse
Through nthbouncer
Pool
POST warehouse.nthpool.cloud
Short-lived pool key on the caller
Authorization: Bearer nb_live_8Kd2...
The pool attaches the database password upstream.
01
Credentials stay at the edge
Callers work with short-lived keys while the pool attaches the real credential at request time, so agents never see the database password or vendor secret.
02
PostgreSQL and MySQL first
The pool gives agents SQL access to real PostgreSQL or MySQL tables for more accurate results. Other callers share the same concurrency limit without holding the origin credential.
03
Concurrency limits
Set max concurrency once, or let adaptive mode learn it from upstream 429s. Every caller draws from the same slots. Anything above the limit waits or goes async.
04
Async admission
A pool can accept the work and post a signed webhook when the origin responds.
Simple pricing
Per organization, billed monthly. Start a free trial on any plan with 10k requests. No card until you subscribe.
Starter
One origin, first pools
$49/ org / mo
- 8 pools · 10 concurrent
- 100k requests
- 0 custom domains
- Unlimited users
- 1 origin per pool
- then $10.00 per 100k requests
Team
Shared origin across apps
$99/ org / mo
- 20 pools · 20 concurrent
- 500k requests
- 10 custom domains
- Unlimited users
- Async admission + access gates
- Origin capacity budgets
- then $8.00 per 100k requests
Business
Org capacity + auto balance
$199/ org / mo
- 40 pools · 50 concurrent
- 2M requests
- 50 custom domains
- Unlimited users
- Everything in Team
- Auto-balance capacity
- then $5.00 per 100k requests
On every plan
- Unlimited members per organization
- Fixed + adaptive concurrency
- HTTP, PostgreSQL, or MySQL backends
- Bounded queue + wait budget
- RPM limit
- Retry on upstream 429
- Response cache
- Pool keys + inbound HMAC
- Upstream credentials
- Concurrency locks API
- Metrics + email alerts
- Access logs + tags
- Spend caps + usage emails
- Organizations + invites
Plan tiers set your pool and concurrency limits. Request overage applies after the monthly allowance.
Need more?
Higher concurrency, more pools, or longer log retention. We'll size a custom plan.
Can Claude or Cursor query my Postgres?
Yes. Add https://nthbouncer.com/mcp. There is no token to paste. Agents query the same tables you do with short-lived keys and never receive the password.
Does it work with PostgreSQL and MySQL?
Yes. Point a pool at PostgreSQL or MySQL. Callers send SQL over HTTP to the pool hostname and never receive the database credential.
Do agents ever receive the database password?
No. The dashboard never keeps the secret, not even a hash. The pool encrypts it on save and decrypts it only inside an isolated sandbox to reach your origin.
Can it front a third-party API?
Yes. Point a pool at the provider's HTTPS API. The pool attaches the upstream credential. Callers carry a pool key, not the vendor secret.
Can it front my own API?
Yes. Point a pool at your HTTPS origin, then route each caller through the pool endpoint. Nothing changes but the hostname.
How is this different from a rate limiter or an API gateway?
A pool limits requests in flight and queues the rest. A rate limiter limits requests per window, and a gateway publishes APIs. Use a pool when you want to share the database without sharing the password, and the origin has a hard concurrency limit.
Ready for live production context?
10k free requests to try a plan. Early access. No credit card until you subscribe.