If a service is not on the list, you can add it yourself. One command:
$ lanes link connect custom thing --connector http --auth api-key --auth-header X-Api-Key \
--base-url https://api.example.com/v1 --openapi https://api.example.com/openapi.json \
--profile personal --workspace localLeave out a value it needs and it asks.
The two choices
A provider is exactly two decisions: how the service is reached, and how you prove who you are.
--connector | For |
|---|---|
mcp | Any MCP server |
http | Any REST API with an OpenAPI description |
imap | Any mailbox |
dav | Any CalDAV or CardDAV server |
fs | Any folder on this machine |
--auth | For |
|---|---|
none | Anything public |
bearer | A token sent as Authorization: Bearer |
api-key | A key in a header you name with --auth-header |
header | Any other fixed header |
basic | A username and password |
oauth | A browser sign-in, where the vendor supports registration |
strategy | A handshake that needs code, like bunq's |
Both lists are closed. Everything else about a provider is data hung off the pair, which is why adding one takes no code.
What it writes
A fifteen-line YAML manifest in ~/.lanes-link/data/<profile>/providers.d/. That is the same kind of
declaration every built-in provider is, and it is yours to edit from there:
id: thing
name: Thing
connector:
kind: http
base_url: https://api.example.com/v1
openapi: https://api.example.com/openapi.json
auth:
kind: api-key
header: X-Api-KeyCapabilities are discovered rather than written: from the vendor's own MCP server, or from the OpenAPI document. There is nothing per-endpoint to declare.
Because it belongs to the profile, a manifest in one profile is invisible to another, and a deployed endpoint serves your custom providers the same way it serves the built-in ones.
Where to go next
- Creating a provider writes one by hand, including the cases that need more than the two lists above.
- Connectivity coverage is the honest account of which combinations work, which are closed on purpose, and what none of them reaches yet.
Next: Add it to your agent.