MCP

Raised as a usability problem by 15 people on Hacker News over 2 years (2025–2026), in 15 threads.

People raised many different problems with MCP, but no single problem has yet been raised by 3 people in 3 different months and threads.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 15 complaints

Forces a separate OAuth server handshake instead of simple cookie-based login2026-06-19
Must edit config files by hand to install an MCP server2026-03-17
Spec docs change fast and are hard to digest for implementers2025-11-24
Average users find MCP too unfriendly, since it is built for developers rather than everyday users2025-11-23
Enabling connections is unintuitive compared to opening an app, and users must pull content2025-10-07
Must hand-edit JSON config files, and one typo breaks everything2025-09-08
Protocol is confusing; users must read official docs to understand it2025-06-26
Original MCP spec and SDK were confusing and complicated to use2025-06-24
Sidebar text is nearly unreadable in dark mode due to low contrast2025-06-17
Setup needs half an hour of searching, hidden settings, and hand-editing a JSON file2025-05-15
Took a long time to figure out how client, server and host differ2025-05-07
Claude connects to GitHub or writes local files even when told not to, so users must manually disable servers2025-05-06
Must name the tool in the prompt to get reliable results2025-05-05
Tool search works on mobile but fails on desktop with errors2025-04-23
Installing MCPs requires Python and Node setup that many users lack2025-03-08