Connect an agent over MCP
Point an MCP-speaking agent — Claude, or your own — at the swarmsDB endpoint. It discovers the catalogue and calls it as native tools. This is the path a keyless OAuth connector uses, so no API key changes hands.
Platform / Access
Two ways in. One surface.
You should not have to change how you build to adopt a data layer. swarmsDB meets your agent
where it already is — native MCP tools for an agent that speaks the protocol, a
plain REST call for everything else — and both reach the identical capability surface.
mcp: app.swarmsdb.ai/mcp · rest: bearer + select= Swarm phase Delivery — authorized transit: the canonical dataset flies to the agent; two ways in, one surface.
Or call the REST surface directly
Prefer plain HTTP? The same capabilities answer to a REST call with a bearer token and a projection. Nothing about the response changes — you still get typed sections, not a raw upstream blob.
# claude_desktop_config.json — no API key changes hands
{ "mcpServers": {
"swarmsdb": { "url": "https://app.swarmsdb.ai/mcp" }
} } grant
{ "key_material": null,
"grant": "workspace-bound",
"revocable": true }curl https://app.swarmsdb.ai/data/openalex/works \
-H "Authorization: Bearer $SWARMSDB_KEY" \
-G --data 'search=graph neural networks' \
--data 'select=id,doi,title,cited_by_count' typed section
{ "shape": "table", "rows": 25,
"fields": ["id", "doi", "title", "cited_by_count"] }# one call, many parameter sets — results by signed webhook
POST /bulk/requests
{ "endpoint": "eurostat/data",
"params": ["nrg_bal_c", "demo_gind", "prc_hicp"],
"schedule": "0 6 * * *" } queued
{ "bulk_request_id": "brq_9f2c…",
"webhook": "hmac-signed" } upstream 8,457,367 → 1,508 chars
More in this area
Built for agentsWhy an autonomous agent runs leaner here — less context, typed data, a brake.Typed sectionsProject the fields you need — only those cross the wire.Bulk & scheduled fan-outOne call across many parameter sets — results by signed webhook.Keyless OAuth connectorsA third party connects by grant. No API key changes hands.Org controls chainThe enforced chain — org → workspace → api_key — members configure it, the backend holds it on the serving path.Members & workspacesTwo levels of role — org and workspace — enforced on the write path.Keys & restrictionsScope a key to the providers, rate, origins and region it may use.Data residencyPin data to a region — validated, immutable, expand-only.
Point one agent at it.
Connect over MCP or REST. If your agents read more than one source, the context bill is the first thing you will see move.