Connect an MCP client
One server address for the tools in your toolset.
The client lists and calls the tools exposed by Vela.
find_customerREADget_available_slotsREADread_order_statusREADYour path, in three steps.
- 01
Copy the MCP configuration
The toolset page provides the server address and configuration to adapt to your client.
- 02
Configure authentication
Use the toolset token with Authorization: Bearer. This token differs from an individual connector key.
- 03
Check exposed tools
Check the tool list in the client and start with a read. Toolset restrictions still apply.
Want to go deeper?
Open just the topic you need.
Overview
A Toolset is an MCP server over Streamable HTTP. If you are using Claude Desktop or Cursor, the AI assistants page is enough — this is for wiring it into something you wrote yourself.
find_customerREADget_available_slotsREADread_order_statusREADConnecting
{
"mcpServers": {
"vela": {
"url": "https://api.example.com/mcp/{toolsetId}",
"headers": { "Authorization": "Bearer vela_ts_…" }
}
}
}The two failures everyone hits
The header value must start with Bearer — without it no token is read and every call is refused with a 401. And the URL is the API host, not the dashboard host: the address in your browser bar answers 404 and explains nothing.
Methods
| Method | Behaviour |
|---|---|
initialize | Negotiates the protocol version, advertises the tools capability. |
tools/list | The enabled, live connectors of this Toolset. Input schemas come from each connector's own contract. |
tools/call | Runs one. A connector that refused returns a tool result with isError: true rather than a JSON-RPC error — the model is what has to react to a wrong date. |
ping | Answers {}. |
notifications/* | 202, empty body. |
Annotations
| Annotation | Reading connector | Acting connector |
|---|---|---|
readOnlyHint | true | false |
destructiveHint | false | true |
idempotentHint | false | false — a booking placed twice is two bookings |
openWorldHint | true | true |
These are hints your client may ignore. The enforceable control is the Toolset's read-only switch, which hides acting connectors from tools/list and refuses them in tools/call — the second matters because an agent may be working from a list it fetched earlier.
What a call actually does
It runs the connector through the same path your own code would use, so it keeps the rate limit, the session handling, the execution history and the automatic repair. An agent call is an execution and is billed as one.
Tokens
- The Toolset token is not a connector key. Revoking it breaks no direct integration.
- It is stored hashed and can be rotated; the old one stops working immediately.
- A wrong token and an unknown Toolset return the same message, so the endpoint cannot be used to discover which Toolsets exist.
Group the right actions into an MCP toolset.
↗Your situation doesn’t match the guide?
Talk to the team ↗