Model Context Protocol

Earendil has published a blog post titled 'You Said No MCP', which is drawing strong discussion on Hacker News. The piece appears to address the Model Context Protocol, the emerging standard for connecting AI assistants to external tools and data, and the company's position on adopting it. Readers are debating the arguments in the comments.

The Model Context Protocol project maintains a collection of reference servers that connect AI applications to external data sources and tools. The repository, written primarily in TypeScript, is currently among the most viewed projects on GitHub, reflecting continued developer interest in building integrations for the open protocol introduced by Anthropic to standardize how AI models access context.

Mario Zechner, creator of the pi.dev coding assistant, spent over a year publicly refusing to support Anthropic's Model Context Protocol, calling the stance a matter of philosophy rather than an unfinished feature. The pi.dev homepage once declared outright that Pi does not support MCP. That position has now changed, with MCP support added despite the earlier dismissals.

Earendil has published a new post explaining why its Pi.dev product does not support MCP, the Model Context Protocol that has become a common standard for connecting AI assistants to external tools. The piece defends the decision to skip the protocol, and the argument is drawing attention and debate among developers following the discussion.

Engineers are discussing a core challenge in agentic AI: while connecting an AI agent to a database is technically straightforward, making the data genuinely usable and reliable for the agent is far more difficult. One write-up describes building an agentic data factory using Parquet, DuckDB and the Model Context Protocol, arguing that data engineering foundations matter more than credentials or access alone.

Earendil's Pi, an AI coding assistant, previously declined to support the Model Context Protocol on its own website but is now integrating it into its core. The shift has prompted discussion of what MCP is and how the assistant's position on the open protocol changed, drawing interest from developers following AI tooling standards.

A developer has published a guide for building a Model Context Protocol (MCP) server that serves documented basketball player data through a typed Sportmicro API integration, written in TypeScript. The tutorial walks through exposing the player insights endpoint so MCP clients can query structured basketball statistics. It is drawing attention from developers interested in connecting sports data to AI tooling.