MCP-First Tools: Claude Plugins, Skills and Apps

Most of what I build today starts from one idea: MCP-first. Every tool, app or workflow is designed so it can be used from Claude in plain language. Interfaces like dashboards, forms or a WhatsApp agent come on top, as extra doors to the same core, not as the only way in.

That way a team can ask, update and get things done from one place, and the same rules and data apply no matter where the request comes from.

The team repeated the same manual work every day: looking up CRM records, triaging lead replies, building performance reports and searching internal docs for procedures. I built a set of Claude plugins and skills that turn each of those workflows into a simple request.

CRM skill: reads and updates contacts, timelines, tags and lists through the CRM's REST API.

Reply triage: pulls recent lead replies, classifies them (warm leads, booking threads, declines, opt outs) and returns a prioritized action list.

Reports: branded HTML reports on performance, generated on request.

Knowledge base lookup: finds the right procedure in the team's documentation and links to the source.

AI agent tuning and ops: builds an AI agent's config from real conversation data, tests intent routing with evals, and manages versions and rollbacks.

Credentials were replaced with configurable placeholders, so the plugins can be packaged and reused by other teams.

Finu: a finance app you can use from the web, from WhatsApp through an n8n agent, or straight from Claude through its MCP server.

A notes and tasks app where I delegate tasks to Claude and it delivers them back.

A portfolio tracker where trades, positions and rebalancing are managed by talking to Claude.

Tasks that used to take a CRM search, a spreadsheet and a few clicks now take one sentence, and every new tool I build is usable from Claude or your AI from day one.