Riccardo Catalano

AI, Strategy, Europe.

I use Claude Code for everything now.

Last week I needed to audit my business expenses. Asked it to line up invoice file names with Excel line entries and organise them. It read the files, matched them, done.

Yesterday I needed Trello integration for a WhatsApp assistant I'm building (post to follow). The official Trello integrations don't do what I need. So I built a 35-tool MCP server and published it to npm. Twenty minutes.

I needed three things:

  1. An OpenAPI spec (Trello publishes theirs)
  2. Claude Code
  3. Knowledge that Anthropic has an mcp-builder skill

I gave Claude Code the spec, told it what I wanted. It built the server. Tool naming, error handling, SDK choice, code structure. It knows MCP patterns because Anthropic taught it.

src/
├── index.ts              # registers everything
├── services/
   └── trello-client.ts  # auth + HTTP
└── tools/
    ├── boards.ts         # 6 tools
    ├── cards.ts          # 16 tools
    ├── lists.ts          # 6 tools
    └── ...

Cards have CRUD, search, comments, attachments, labels, member assignment. Everything works.

npm install -g trello-mcp

None of these tasks justified hiring someone. None of them had off-the-shelf solutions that fit. Before, they'd sit on a todo list forever or I'd waste hours doing them manually.

Now I describe what I want and it happens. Organize files. Audit expenses. Build integrations. The task doesn't need to be worth a developer's time. It needs to be worth describing.

The Model Context Protocol lets you give Claude Code access to any service with an API. The skills repo has mcp-builder baked in. But even without MCP, Claude Code runs on your machine. It can read your files, run scripts, do the tedious stuff.

Custom software used to require mass-market appeal or a budget. Now you can just do things.