Seventy-five connectors
to the tools you already use.

Notion, Linear, GitHub, Supabase, Stripe, Cloudflare, Hugging Face and seventy more — over the Model Context Protocol, from the vendors’ own published listings.

Image pending · plugins-hero

The plugins page in the app: the shelf of connectors with real logos, install and connect states visible.

16/9

Connected, not integrated-in-theory

Every listing comes from the vendor

The catalogue is generated against the official MCP registry, not written by us. Each connector’s address, package, version and credentials come from what the vendor published. Nothing on the shelf is a description of a hoped-for integration — if it is listed, the vendor shipped it.

Image pending · plugins-shelf

The shelf, scrolled, showing the range and the real logos.

4/3

Eighteen work with nothing to set up

No key, no sign-in, no account. Install and use. For the rest, signing in happens through the provider’s own login — you are not pasting long-lived tokens into a text field, and Eshlon never sees your password.

Image pending · plugins-connect

A connector going from install to connected — including the provider consent screen.

4/3

Idle connectors cost you nothing

Connected tools normally load their entire schema into every message, whether you use them or not — tens of thousands of tokens before you type a word. Eshlon keeps idle connectors down to a single line each and loads the real tools only when a connector is actually used. Rebuilding the tool list every turn is what makes that possible.

A plugin is more than a connection

A connector gives an agent the ability to call an API. What makes it useful is knowing when to. Plugins can carry authored workflows — the shape of a triage pass, a cycle plan, a status update — so a connected tool arrives knowing how the work is normally done.

Image pending · plugins-skills

A plugin’s bundled workflows listed on its page.

4/3

What people connect first

Notion

Meeting notes, specs and knowledge capture, written where the rest of the team already looks.

Linear

Triage, cycle planning and status updates against real issues.

GitHub

Issues, pull requests and code review on the repositories you actually work in.

Cloudflare

Docs and platform data, with no sign-in needed at all.

FAQ

How many connectors are there?

Seventy-five today, and the catalogue is generated from the official registry rather than hand-written, so it grows as vendors publish.

Which ones work with no setup?

Eighteen need nothing at all — no key and no sign-in.

Does connecting a plugin slow everything down?

No. Idle connectors contribute a single line each. The full tool list for a connector loads only when it is used.

Are there tools you cannot connect?

Yes, and it is worth being straight about it: several large vendors have not published an MCP server at all. If it is not on the shelf, it usually does not exist rather than having been left out.