From zero to first tool call in four minutes
Connect one app, mint one scoped key, add one MCP server to your client. This page is the whole path; the rest of the docs are detail.
Install the CLI
Everything below is also available in the dashboard and the REST API. The CLI is shown because it scripts cleanly into CI.
npm install -g @vectorhub/cli
vectorhub loginConnect an app
Authenticate the service once. OAuth opens a consent screen in your browser; key and password auth prompt in the terminal. The credential goes into the vault encrypted and never comes back out to a client.
vectorhub connect salesforce --auth oauth
# → opens consent screen, stores refresh token
vectorhub connect stripe --auth api-key
# → prompts for the key, stores it encrypted
vectorhub connect internal-billing --auth basic \
--base-url https://billing.internal.acme.com
vectorhub connections list
NAME AUTH TOOLS STATUS
salesforce oauth2 88 connected
stripe api-key 92 connected
internal-billing basic 46 connectedMint a scoped key
Keys start with no access. Grant exactly the connectors and tools one agent needs: scoping works at tool level, so a key can read tickets without being able to delete them.
vectorhub keys create support-bot \
--connectors salesforce,stripe \
--tools "salesforce.case.*,stripe.invoice.read" \
--expires 90d
vh_live_9f2c4a71e8b3… # shown once: store it now
# later, if it leaks:
vectorhub keys revoke support-botConfigure your client
One URL, one header. Every client reduces to the same three values, and a connector you enable tomorrow needs no client-side change.
claude mcp add vectorhub \
--transport http \
https://mcp.vector-hub.org/v1 \
--header "Authorization: Bearer $VECTORHUB_KEY"Make a call
Ask the agent for something that needs a real system. Discovery picks the working set, the gateway checks scope and injects the credential, and the call lands in your log.
> Which enterprise cases have been open more than 5 days,
and what are those customers paying us?
⚒ salesforce.case.search 187ms
⚒ stripe.invoice.read 142ms
Four cases are past 5 days. Two are on annual plans
(ACME Corp, Northwind), so I've listed them first.
$ vectorhub logs tail --key support-bot
12:04:31 salesforce.case.search 187ms ok
12:04:32 stripe.invoice.read 142ms okCore concepts
Six words that appear throughout the rest of the documentation.
- Connection
- An authenticated link to one service. Created once, shared by every key you scope to it. Holds the credential; never exposes it.
- Connector
- The versioned package describing a service: its tools, schemas, auth binding and error mapping. Managed by VectorHub, or generated from your own API.
- Tool
- One callable operation inside a connector, with a typed input schema. Scoping happens at this level, not just at connector level.
- Key
- What an agent actually holds. Bound to an allowlist of connectors and tools, optionally expiring, revocable in one operation.
- Environment
- An isolated set of connections and keys. A dev agent pointed at a sandbox cannot reach the production connection of the same service.
- Working set
- The subset of tools discovery exposes for the current task: typically around eighteen, drawn from a catalog of 25,000.
Where to go next
The rest of the platform, in the order most teams need it.
Quickstart
Connect, scope, configure, call: the full path in four minutes.
Authentication
OAuth, API keys, basic auth and custom schemes upstream; scoped bearer tokens downstream.
Client setup
Exact configuration blocks for Claude, Codex, Cursor, Windsurf, LangChain and the SDK.
API to MCP
Generate a private connector from an OpenAPI or GraphQL schema.
Tool discovery
How the working set is chosen, and how to pin tools that must always be present.
Observability
Reading call logs, replaying failures and exporting traces.
Need a key to try this?
Early access accounts are provisioned within a day. Tell us what you are building.
No credit card required · Free tier available · Self-host on request