Best of mcp — February 2026

1. 1
   Article

   Nordic APIs·10w

   Why It’s Good to Be API-First in the AI Era

   API-first design provides structural advantages for AI systems by creating efficient, well-documented, and standardized interfaces that AI agents can consume effectively. This approach improves agentic workflows through better discovery, error handling, and decision-making while reducing infrastructure costs. Standardization enhances security and auditability across multi-call workflows, and simplified data structures give organizations control over AI data access. API-first systems are naturally positioned to adopt emerging standards like Model Context Protocol (MCP), enabling structured tool invocation. The paradigm effectively makes organizations AI-ready by prioritizing clarity, discoverability, and consumability.

   79

   3
2. 2
   Article

   Product Hunt·7w

   PeonPing: Stop babysitting your terminal

   PeonPing is a developer productivity tool that sends sound and desktop notifications when AI coding agents (Claude Code, Cursor, Codex, etc.) finish tasks, encounter errors, or need approval. It features 100+ game-themed sound packs (Warcraft, StarCraft, GLaDOS, TF2), an animated desktop Orc Tamagotchi, and an MCP server that lets agents choose their own sounds — helping developers stay in flow without constantly watching the terminal.

   55

   3
3. 3
   Article

   Nx·8w

   Why we deleted (most of) our MCP tools

   Nx shifted from MCP tools to agent skills for AI assistants after recognizing that modern agentic workflows made many MCP tools redundant. Agents can now execute CLI commands directly and process outputs themselves, making context-dumping MCP tools token-inefficient. Skills provide domain-specific knowledge about when and how to use Nx features, while MCP remains valuable for authenticated APIs and process communication. Benchmarks show skills outperform MCP-only approaches, especially for smaller models, with agents using generators more consistently and validating their work more often.

   41

   4
4. 4
   Article

   LangChain·7w

   How we built Agent Builder’s memory system

   LangSmith Agent Builder uses a filesystem-based memory system to give task-specific agents persistent, evolving knowledge across sessions. Memory is stored as files in Postgres but exposed to the agent as a virtual filesystem, mapping to COALA's memory taxonomy: procedural (AGENTS.md, tools.json), semantic (skill files, knowledge files), with episodic memory planned. Agents update their own memory in-the-hot-path as they work, with human-in-the-loop approval to guard against prompt injection. Key learnings include: prompting is the hardest part, agents need help compacting generalizations, and explicit memory commands are still useful. Future work includes background memory processes, a /remember command, semantic search over memory, and user/org-level memory scopes.

   23
5. 5
   Article

   Laravel Dev·10w

   Let agents find packages for you, mcp server for laraplugins.io

   Laraplugins.io has launched an MCP (Model Context Protocol) server that enables AI agents to search, inspect, and check the health status of Laravel packages. This integration allows developers to use AI assistants to discover and evaluate Laravel packages programmatically.

   14

   4