All spotlights
Tool DropMay 4, 2026

Cline 3.0 — MCP-native coding agent

Native MCP support is the headline. The actual story is that Cline is now the most extensible coding agent for solo devs willing to wire things up themselves.

See Cline tool entry

Cline 3.0 dropped in March, and it's quietly become the most interesting coding agent for developers who want extensibility over polish.

What it is

Cline is a VS Code extension that turns your editor into an autonomous coding agent. You tell it what to do, it plans, it executes. Same category as Claude Code or Cursor's agent mode — different tradeoffs.

What's new in 3.0

Native Model Context Protocol (MCP) support. This sounds like plumbing, and it is — but it changes what's possible:

  • Database access without glue code. Point Cline at any MCP server (Postgres, Supabase, etc.) and it can query during code generation.
  • Browser automation built in. Combine with a Playwright MCP server and Cline can debug UI issues by actually loading the page.
  • Custom tools without writing TypeScript. Spin up a small MCP server in any language and Cline picks it up.

Who it's for

Solo developers who:

  • Already have a paid API key (any provider — Cline is BYOK)
  • Want to combine multiple tools (DB, browser, file system) in one agent
  • Don't mind a less polished UX in exchange for broader integration

Who it's not for

  • Teams wanting a single integrated experience (Cursor wins here)
  • People allergic to setup steps (Claude Code is more turnkey)
  • Anyone whose workflow doesn't benefit from MCP integrations (then it's just a less polished Cursor)

The catch

Cline 3.0's UX is still rougher than Claude Code's. The MCP server ecosystem is real but young — expect to write your own for niche tools. And running it well means understanding what an MCP server is, which is a small but real cost.

Worth trying if

You've been frustrated by how isolated Cursor or Claude Code feel from the rest of your stack. Cline's bet is that the next wave of agent capability comes from integrations, not bigger context windows. That's a defensible bet.

More spotlights: See the archive →