1,500+ integrations you do not have to build
Each connector is a maintained package of typed tools with auth attached. Enable it in the dashboard and every key you scope to it can call it immediately.
Every category your agents will ask for
The long tail matters more than the headline names: the tool an agent needs is rarely the one you predicted.
Productivity
18+Docs, tasks, calendars and notes.
CRM & Sales
12+Pipelines, contacts and revenue data.
Developer Tools
20+Repos, CI, incidents and deploys.
Communication
14+Chat, mail, meetings and calls.
Data & Analytics
16+Warehouses, BI and event streams.
Marketing
12+Campaigns, ads, SEO and content.
Finance & Billing
11+Payments, ledgers and invoicing.
Support
7+Tickets, help centers and CSAT.
Files & Storage
7+Object stores and file sync.
HR & Recruiting
8+ATS, HRIS and onboarding.
Commerce
7+Storefronts, orders and inventory.
AI & ML
9+Models, vector stores and evals.
A connector is more than a wrapped endpoint
Generated clients are easy. Connectors an autonomous caller can use correctly are not.
Typed tool schemas
Every tool carries a strict JSON Schema with enums, ranges and additionalProperties disabled, so models produce valid calls instead of plausible-looking ones.
Descriptions written for models
Tool descriptions are prompt text. Ours say what an operation does, when to use it and what it changes, not 'Updates the resource'.
Destructive ops gated
Deletes and irreversible writes are off by default and must be enabled deliberately per key.
Drift monitoring
Upstream schemas are diffed continuously. A changed field becomes a connector release, not a Friday-night page for you.
{
"connector": "zendesk",
"version": "2026.08.1",
"auth": { "type": "oauth2", "scopes": ["tickets:read", "tickets:write"] },
"tools": [
{
"name": "zendesk.ticket.search",
"description": "Search tickets by status, requester, tag or free text. Use before updating a ticket to confirm you have the right one.",
"input": {
"type": "object",
"additionalProperties": false,
"properties": {
"status": { "enum": ["new", "open", "pending", "solved"] },
"query": { "type": "string", "maxLength": 512 },
"limit": { "type": "integer", "minimum": 1, "maximum": 100 }
}
},
"destructive": false
}
]
}A sample of what is live today
141 of the most-requested connectors, with the rest of the catalog available in the dashboard.
Connector questions
What exactly is a connector?
A versioned package that describes one service: its tools, their input and output schemas, its auth binding, its rate-limit behaviour and its error mapping. Enabling a connector makes its tools callable through the gateway.
Who maintains the connectors?
VectorHub does. Schemas are monitored against upstream API changes, and updates ship centrally so a vendor's breaking change does not become your incident.
Can I restrict which tools inside a connector an agent can call?
Yes. Scoping works at tool level, not just connector level. A key can hold zendesk.ticket.read without holding zendesk.ticket.delete.
What if the service I need is not in the catalog?
Use the API to MCP converter. Point it at an OpenAPI or GraphQL schema and you get a private connector with the same scoping, logging and auth handling as a managed one.
How are connector versions handled?
Connectors are versioned and pinned per tenant. Upgrades are opt-in with a changelog and a deprecation window, so a schema change never silently alters agent behaviour.
Enable your first connector
Authenticate one app, scope a key to it, and watch an agent call it within the minute.
No credit card required · Free tier available · Self-host on request