Free
$0
- 2 sources · 10 concurrent
- 25k requests to start, no card
- 1 Work project
- Sales
- Support
- Ops
- Finance
- Marketing
- Engineering
The production context layer for agents.
Sales, support and finance should be working from live data, not waiting days for someone to pull it. swarmvia gives every person, and every AI assistant they run, one safe way in to your databases, tools and APIs.
- Flat per-org price, unlimited members
- 25k requests included
- No credit card
Your people, and the agents they run
Sales
Support
Ops
Finance
Marketing
Engineering
swarmvia
The CTO’s agent passes the same five checks as the intern’s.
- whoOAuth, by name
- may theygroup access
- how manylimit, then queue
- as whomread-only role
- recordlogged by name
Your systems
PostgreSQL
MySQL
Snowflake
NetSuite
HubSpot MCP
Your APIs
Your people, and the agents they run
- Sales
- Support
- Ops
- Finance
- Marketing
- Engineering
swarmvia
- whoOAuth, by name
- may theygroup access
- how manylimit, then queue
- as whomread-only role
- recordlogged by name
- PostgreSQL
- MySQL
- Snowflake
- NetSuite
- HubSpot MCP
- Your APIs
No password or token leaves swarmvia
Nobody in sales should have to know which database the answer lives in.
Sales
“Brief me on Acme before my 2pm call.”
app_db · hubspot
Support
“Why can’t Acme’s admin log in since this morning?”
app_db · sentry
Ops
“Which orders shipped late this week, and which carrier was it?”
orders · carrier API
Finance
“Which invoices over $10k are more than 30 days overdue?”
netsuite
Marketing
“Which campaigns brought in accounts that are still active?”
app_db
Engineering
“Which accounts turned on bulk export but never ran one?”
app_db · from Cursor
Setup
Set the rules once, then get out of the gatekeeping business.
- 01
Connect a source
PostgreSQL, MySQL, Snowflake or NetSuite through a driver you supply, a remote MCP server, or an HTTPS API. swarmvia encrypts the credential on save.
- 02
Choose who can see it
Groups choose which teams reach each source. A read-only database role and a tool allow-list set what they can do there.
- 03
Hand everyone one URL
On Claude Team or Enterprise an owner adds it for the whole company, and people click Connect. Everyone else pastes the URL once.
claude mcp add --transport http swarmvia https://swarmvia.com/mcpNo token to paste. The first call opens a consent screen where each person picks which sources this app may use.
The database decides what an agent can read, not a parser guessing at its SQL.
Extra calls wait in a queue
You set how many calls run at once. The rest wait their turn instead of piling on.
Your database enforces read-only
A write fails at the database, and the refused statement is logged.
Revoke one person, rotate nothing
Credentials stay encrypted in swarmvia, so removing someone never means changing a password.
Every call has a name
Every call, with the statement and row count, kept for up to a year.
Priced per company, so nobody has to ration seats.
Every plan, Free included, comes with unlimited members, groups, read-only roles and IP policies. You pay for more sources, more requests and a longer log history.
Starter
$49 / org / mo
- 6 sources · 50 concurrent
- 500k requests
- 5 Work projects
- 1 origin per source
- 30-day logs
- then $6.00 per 100k requests
Team
$99 / org / mo
- 20 sources · 50 concurrent
- 1M requests
- 25 Work projects
- Async admission
- 5 origins per source
- 90-day logs
- then $6.00 per 100k requests
Business
$199 / org / mo
- 50 sources · 50 concurrent
- 5M requests
- Unlimited Work projects
- Everything in Team
- 8 origins per source
- 1-year logs
- then $5.00 per 100k requests
Requests past the included amount are billed under a monthly spending limit you control. Need SSO or more than Business? Talk to us.
What a CTO asks before saying yes
How is read-only enforced?
By the database, not by parsing SQL. Agents connect as a role you create with only the grants they need, and swarmvia shows how many tables that role can see when you add the source. Anything the role cannot do fails at the database, and the refused statement is logged.
Does anyone ever see the password?
No. swarmvia encrypts the credential on save and decrypts it only inside an isolated sandbox to reach your MCP server, database, or API. The dashboard never keeps the secret, not even a hash. People and agents carry short-lived keys that expire on their own.
What happens when fifty agents ask at once?
Each source has a limit you set on how many calls run at once. Calls above it wait in a queue instead of reaching your database. On Team and Business, a call that waits too long can carry on as a background job.
Does swarmvia store my query results?
Results pass through swarmvia and are never written to the access log. The log keeps who ran each query, the statement (truncated), the row count, and timing. A long query that finishes in the background keeps its result for an hour by default so the agent can fetch it, then it expires.
Which AI apps work with it?
Claude, ChatGPT, Cursor, Claude Code, Codex, VS Code, and anything else that connects to a remote MCP server. Each person adds https://swarmvia.com/mcp and signs in. There is no token to paste, and they see only the sources their group allows.
Can I put MCP servers behind swarmvia?
Yes. Add a source from a remote MCP server's URL. swarmvia holds its token or OAuth connection, shared or per member, and you choose which read and write tools callers see. Agents reach those tools through the one swarmvia connection they already have.
How does my team control access?
Groups decide which members see each source, and a connected agent never sees more than the person who approved it. Read-only keys block writes, MCP tools can be hidden one by one, and every call is logged with who made it.
Can it front an HTTP API?
Yes. Add your own HTTPS origin or a provider's API as a source. swarmvia attaches the upstream credential. Callers carry an access key, not the vendor secret.
How does swarmvia fit with my API gateway?
Your gateway publishes APIs to the outside world. swarmvia is the layer your own agents and teammates use to reach production: it decides who sees each source, holds the credential, logs every call, and limits how many run at once, so you can share the database without sharing the password.