Get the free letter
Get the free letter

My AI stack

The apps, connections and workflows behind the work.

This page grows with the setup: the apps I run, the connections that let AI work inside those apps, and the skills and workflows that tie them together.

Ink and brass illustration of five app windows connected by hairlines to a single point of control

01 / Apps

The tools themselves.

15 tools. 9 free. Each one earns its place by the job it does. Pick a tool to see its job.

Pick a tool to see the job it does for me.

02 / App Connections

Tools that let AI work inside my apps.

An assistant that can only talk is homework. These are the connectors that let it do the work. Composio is the first one I am researching.

Exploring · via MCP

Composio: one connection between your AI and your apps

A man at a desk facing floating app screens, all connected by one beam of light from his laptop

ChatGPT and Claude can already reach some apps on their own. The pain starts when you want more than that. Each assistant has its own connector list, its own login flow, and its own plan limits, and the app you need is rarely on every list. Wire Gmail into one assistant and you still have to wire it into the next one.

Composio sits in the middle as one shared connection point. You ask your assistant for something real, the assistant passes the request to Composio through MCP (the standard protocol for AI tools), and Composio makes the actual call to the app and brings back the result in a form the model can use. It also manages your logins in the background, so you connect an app once instead of repeating the setup in every compatible assistant you use.

Why it earns a spot

  • Connect an app once, then use it from Claude, ChatGPT, Cursor, and other assistants that can reach an MCP server. Each client still has its own transport, sign in, and plan rules.
  • More than 1,000 apps behind one connection: Gmail, Notion, Slack, GitHub, Linear, HubSpot, and the rest.
  • The first time the assistant needs an app, Composio hands you an approval link in your browser. After you approve, Composio stores and refreshes the login for you, until you revoke it or the app lets it expire.

How to set it up

01

ChatGPT. Turn on Developer mode in settings (this needs a paid plan), add Composio as a custom MCP server with its connection URL, then switch it on inside each chat where you want it.

02

Claude. Add the same URL as a custom connector and sign in. Every Claude plan allows custom connectors, and the free plan allows one. Claude Code skips the connector route and uses the Composio plugin instead.

What it could do, end to end

Example: you ask to summarize unread invoices, your assistant calls Composio, Composio reads Gmail, and the summary appears in your chat. A note marks your approval rule before anything sends.

Illustrative example, not a test I ran: a read only inbox summary. The approval step is my workflow rule, not a Composio feature. Tap an image to open it full size.

The part to watch

Actions run as you. If Claude sends an email through Composio, that email went out from you. Same for deletes, edits, and invites. So keep your own approval step for anything with side effects, and read what you actually granted: the Composio dashboard lists each connected account with the exact permissions you handed over. You can cut an app off there, or inside the app itself, and the connection stops working until you reconnect.

One connection does not mean identical access everywhere. Each app grants its own permissions, each assistant has its own plan limits, and Composio's free tier has its own monthly caps. Worth five minutes in the dashboard before you let an agent loose.

AI does the job, humans orchestrate. This is what orchestration looks like in practice: your assistant gets hands, you keep the keys.

My take

One connection

Connect an app once. Give compatible assistants a way to act.

A brass keyring holding matte black and brass app tags on dark slate under a spotlight: your assistant gets hands, you keep the keys

Tap an image to open it full size.

03 / Skills & Workflows

Reusable instructions and agent workflows.

Nothing listed yet. This is where the playbooks my agents follow will live, once I curate them.

A playbook is a standing instruction: how I want email triaged, how a draft gets written, what never sends without my yes. Write it once, and it gives every agent a repeatable starting point. The curation is the real work, so I am doing it slowly and on purpose.

In curation

Instructions that outlive the conversation.

A stack of three cloth playbooks embossed Email Triage, Drafting and Approvals on travertine stone in hard sunlight

Playbooks in curation. Tap an image to open it full size.

Using means it runs my day. Exploring means I am researching it, not using it yet. Nothing on this page is a recommendation to buy.

Back to the homepage