// Pricing
Simple, transparent pricing. No surprises.
Pay As You Go
From $2/mo
- First 2 connections: $2/ea
- Additional connections: $1/ea
- On-demand token refresh
- Dashboard access
- Email support
Enterprise / Teams
Custom
- Unlimited connections
- Multi-user team accounts
- Centralized billing
- Dedicated support
- Custom SLAs
- SSO integration
// Plan comparison
| Feature | Free Trial | Pay As You Go | Enterprise |
|---|---|---|---|
| Connections | 1 | Unlimited | Unlimited |
| Pricing | Free | $2/mo ea. first 2, $1/mo each 3+ | Custom |
| Duration | 24 hours | Monthly | Annual |
| On-demand token refresh | Yes | Yes | Yes |
| Dashboard | Yes | Yes | Yes |
| URL revocation | Yes | Yes | Yes |
| Team members | 1 | 1 | Unlimited |
| SSO | — | — | Yes |
| Support | Community | Dedicated | |
| SLA | — | — | Custom |
| Credit card required | No | Yes | Invoice |
// FAQ
Can I change plans?
Yes. Add or remove connections at any time from your dashboard. Changes take effect immediately and billing is prorated.
What happens when my trial ends?
Your connection stops proxying requests. Your configuration is preserved for 30 days, so if you subscribe, everything picks up right where you left off. No data is lost.
Do you store my data?
All OAuth tokens are encrypted at rest with AES-256-GCM. By default (client-side keys mode), the encryption key exists only in your secret URL and Bindify can never access your tokens. Advanced users can opt into managed refresh mode, where Bindify holds a server-derived key to refresh tokens daily in the background. We do not log or inspect MCP request content. See our security page for details.
How does token refresh work?
OAuth tokens expire. Bindify refreshes them on-demand when your connection is used — no manual reconnection needed. If you opt into managed refresh (advanced), tokens are also renewed daily in the background, which protects long-idle connections.
What is client-side keys mode?
The default for all connections. Bindify never holds your encryption key — it exists only in your secret URL. This provides zero-knowledge security: even a full infrastructure compromise cannot expose your tokens. Tokens are refreshed on-demand when you use your connection.
What if Anthropic fixes OAuth?
If Claude natively supports persistent OAuth connections, you may no longer need Bindify. We will not lock you in. Cancel anytime with no penalty. We believe the convenience of a managed proxy will remain valuable regardless.
Can I use Bindify with Claude Desktop, Claude Code, and other MCP clients?
Yes. Bindify works with any MCP client that supports remote server URLs, including Claude.ai, Claude Desktop, Claude Code, Cursor, and others. Claude Desktop uses an SSE URL in your config file. Claude Code uses a streamable HTTP URL with an API key header. See our setup docs for client-specific instructions.
Does Bindify work with non-Claude MCP clients?
Yes. Bindify works with any MCP client that supports remote server URLs. While our docs focus on Claude (the most popular MCP client), users have successfully connected Bindify with Cursor, Open WebUI, and other MCP-compatible tools.
Which authentication methods does each service support?
| Service | OAuth | API Key |
|---|---|---|
| Linear | Yes | Yes |
| Todoist | Yes | Yes |
| GitHub | Yes | Yes |
| Figma | Coming Soon | |
| Atlassian | — | Yes |
| Notion | Yes | — |
Do I need to rotate my credentials?
All connections refresh tokens on-demand when used. Connections should be rotated annually for security. Click "Re-authorize" in your dashboard before the 1-year mark to keep your connection active.
// Ready for MCP connections that just work?
Start your free 24-hour trial. No credit card required.
Start Free Trial