Toolkits

Every tool your agent will ever ask for.

Connected once, signed in per user, every write held for a yes — and every count on this page rendered live from the registry.

80+TOOLKITS 1,200+TOOLS 60+TRIGGERS

The catalog, browsable.

SHOWING 48 · CLICK ANY TOOLKIT TO OPEN IT
1One box, three indexesToolkit names, tool keys, and trigger keys in one search. Picking a result scrolls to the tile, opens its panel on the right tab, and flashes the exact row.
POPULAR — EACH OPENS WITH A LIVE ASK
SHOWING THE FIRST 48 — THE FULL REGISTRY CARRIES 80+
2Everything opens in placeNo jump to a sub-page (Composio exiles you to one per toolkit): the panel expands inside the grid, right under the tile you clicked — see-it-work on the right, tools & triggers tabs on the left, close and keep browsing.
3The shrinking askOne story, no terminal soup: the three highlighted details physically fly out of the first ask into the memory panel. The short ask then runs with the panel flashing RECALLED. −74% is computed from the real strings (100 → 26 chars). The board below answers "what else does it remember" — grouped by how it helps, not by app.
Tools that remember

Say it once. It's remembered.

Your users explain themselves once. The details become memory — recalled on every ask after, for that user only.

claude code — acme agentStacklink connected
THE FIRST ASK — THE ONLY TIME ANYONE EXPLAINS
>Chase this month's unpaid invoices — start polite, amounts in INR, and drop the summary in #finance.
✓ 41 reminders sent · summary posted to #finance
EVERY ASK AFTER — NEXT WEEK, SAME USER
>Chase the unpaid invoices.
✓ 12 sent — still polite, still INR, summary in #finance
−74%of the typing.
Every detail still there — recalled, not retyped.
PRIVATE TO THIS USER
stacklink · memoryRECALLED · 12ms
Reminders start politethe “polite-14d” template — firm only after 30 days
Amounts shown in INRapplies to every invoice and payment tool
Summaries land in #financethe channel for anything money
learned from one ask — kept for every ask after
4The board is aliveA recall sweep runs left to right: every three seconds one fact lights up with its RECALLED chip, and the log line below narrates the actual run that used it — which client, which tool, and the ms it took. Numbers are one illustrative user's first month.
A month in

Your agent just knows.

Eight of the twenty-three facts one user's agent picked up in its first month — being recalled live, mid-run, private to that user.

0FACTS LEARNED
0APPS
0AVG RECALL
CONTINUOUSLY LEARNING
RECALLED · 9msHOW YOU LIKE ITReplies stay under five linesyou said it once — it stuck
Gmail
RECALLED · 11msWHERE THINGS GOEscalations ping @oncall in #eng-alertslearned from a 2 a.m. page
Slack
RECALLED · 14msWHO OWNS WHATThe Acme renewal is yoursso its briefs come to you first
HubSpot
RECALLED · 9msNEVER AGAINNothing books before 10:00declined twice — learned once
Google Calendar
RECALLED · 12msHOW YOU LIKE ITRelease notes follow your changelog stylelearned on v2.3 — applied on v2.4
GitHub
RECALLED · 8msWHERE THINGS GOVendor invoices forward to Priyalearned clearing Monday's inbox
Gmail
RECALLED · 10msWHO OWNS WHATPayment code waits for your reviewlearned from three PRs in a row
GitHub
RECALLED · 12msNEVER AGAINInvoice #1041 is never chasedit's disputed — you said so once
Zoho Books
watching recalls…
Personal to each user — never shared across them.
Off by default — you switch it on.
Every fact visible, editable, deletable.
OAuth, handled

Your users sign in.
You write none of it.

Every toolkit ships with its auth flow already built. The page on the right is the real one — wearing your logo, at your domain. You send a link; we handle consent, tokens, refresh and revocation.

01
You create a connect linkOne API call, or a click in the dashboard. No OAuth app to register, no redirect URIs to babysit, no provider quirks to read up on.
02
Your user approves — on this pageReal OAuth with the provider. They see exactly what's requested; the provider's own consent screen is final.
03
Your agent gets scoped toolsOnly that user's grant, only the tools you allow. Tokens stay server-side — your code never touches a credential.
Refresh, expiry and re-consent handled for you.
Revoke one user, one app, one click.
MCP OAuth too — including dynamic client registration.
stacklink Secure connect link

Stacklink wants to connect Slack

Authorize this connection so your tools can act on your behalf.

Slack
Stacklink requests the complete certified permission set for this Slack toolkit. Select all for the full toolkit, or unselect permissions on Slack to keep only the tools covered by the granted access.
Continue to Slack
Credentials are submitted with POST, never placed in the URL, and encrypted at rest
Stacklink requests the complete certified toolkit permission set; the provider consent screen is final
You can revoke access from your provider at any time
Secured by stacklink
THE REAL HOSTED CONNECT PAGE — ON YOUR BRANDING, AT YOUR DOMAIN

Every toolkit here is one connection away.

Plug in once — MCP or SDK — and hand your agent the whole catalog, guardrails included.

free tier · no card · first tool call before your coffee cools