MCP

A new essay titled "You Said No MCP" is drawing heavy attention on Hacker News, ranking near the top of the site with close to 600 upvotes. The piece, published by Earendil, weighs in on the debate around the Model Context Protocol, the emerging standard for connecting AI assistants to external tools and data. Commenters are actively debating its arguments about how and whether developers should adopt MCP.

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.

The Model Context Protocol organisation maintains a servers repository providing reference implementations of MCP servers in TypeScript, which let AI applications connect to external data sources and tools. Interest in the project continues as developers adopt the open protocol, originally introduced by Anthropic, to link large language models with files, databases and services.

Stablecoin issuer Tether has released beta command-line interface and MCP wallet tools that let users manage Tether holdings locally and keep custody of their own keys. The move is aimed at users who prefer self-custody over leaving assets on exchanges or custodial platforms, and the tools are available in beta while feedback is gathered from the crypto community.

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.

Developers are commenting on the overwhelming pace of open-source AI releases, with new agent frameworks, MCP servers and machine learning tools appearing every week. Discussion centres on which fast-growing projects are worth attention and how hard it has become for engineers and hobbyists to stay current in the field.

Flexport has launched an MCP Server that allows AI agents to book freight directly through its logistics platform. The move positions the freight forwarder at the front of efforts to automate supply chain booking with agentic AI, and was reported by FreightWaves. It could let corporate systems and AI assistants handle shipping arrangements without human brokers.

Model Context Protocol, or MCP, is being framed as the standard that lets AI agents plug into a company's APIs and tools. But commentary from The New Stack stresses that the protocol only provides access — it does not govern what an agent should or should not see once connected. That means questions of permissions, filtering and data exposure still fall on developers and platform owners rather than on MCP itself.

NorthCinder is an open-source MCP server that lets users compare products across stores of their choosing. According to its README, the tool requires a signed, single-use buyer approval tied to one exact offer before any checkout can proceed. The project is being shared in information security circles and discussed as an example of adding safety controls to AI agent purchasing.

A widely shared remark points out an irony in current AI automation: coding agents can now control a full desktop browser, yet smartphones still require a human thumb to operate. The post, tagged with Android, iOS, MCP and mobile development topics, links to further discussion on the gap between AI browser control and mobile automation.

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.