Every provider

105 providers, each one command. This page groups them by what connecting actually asks of you, because that is the only difference between them that costs you anything.

If what you want is not here, add your own: any MCP server, REST API, IMAP or CalDAV host, or local folder, in one command.

Nothing to set up

The vendor registers Lanes Link at the moment you run connect. A browser opens, you approve, and it is live. There is no console to visit and no client to create.

Browser sign-in, through a client we operate

A browser opens and you approve. The OAuth client is operated by Lanes, so no client secret of theirs is stored on your machine. --own-client opts out and uses one you registered.

Needs an application of your own

These offer no dynamic registration, so you register an application once in the vendor's console. lanes link setup plan <id> prints the steps, the values, and the command.

A token or key you paste

No browser at all, which also means these work over SSH and inside a container. An agent with a shell can do the whole setup non-interactively.

An app password

Mail, calendars, and contacts over IMAP, CalDAV, and CardDAV. One app password often covers all three for the same account.

On your own machine

A folder that is already there. Nothing to authenticate to.

Its own handshake

A keypair and a signed exchange rather than an OAuth flow.

Guides that cover a vendor rather than a provider

Google and iCloud each serve several providers from one account, so the console work and the app password are done once for all of them:

Google covers Gmail, Drive, Sheets, Docs, Calendar, Tasks, and Contacts. iCloud covers Mail, Calendar, Contacts, and Drive.

About the 84 marked †

† means untested. The manifest is right in every way the code can check: it validates, its tools generate inside the budget, its scopes are described, and its endpoint answered a probe. Nobody has yet connected it to a real account, which is the part only a real account proves.

The mark is on the page too, and it comes off when somebody reports connecting it.

Before you start

$ lanes link setup plan --profile personal --workspace local               # every provider, connected or not
$ lanes link setup plan icloud_mail --profile personal --workspace local   # the steps, the values, the command

An agent connected to your endpoint can read the same thing, so it can hand you the exact command rather than guessing at one. That surface is read-only: connecting, credentials, and permissions stay in the CLI.

Next: Connections for what a connection is, or Scopes and permissions for narrowing one.