protocol

Bilingual

Bringing MCP 2026-07-28 to Claude
2 months ago
- MCP 2026-07-28 introduces a stateless core, shifting from bidirectional stateful to request/response for serverless and edge deployment.
- Standardized extensions for MCP Apps and Tasks provide a formal path to add capabilities like interactive UIs and long-running work without core protocol changes.
- Authorization is hardened with production OAuth 2.0 and OIDC support, enabling integration with enterprise identity systems like Entra or Okta.
- MCP has surpassed 400 million monthly SDK downloads (4x increase this year) and is the industry standard for connecting AI agents to applications.
- Claude now lists over 950 MCP servers, with new features: MCP Apps for inline interactive UI, enterprise-managed auth via identity providers, observability dashboards for developers, and MCP Tunnels (research preview) for private network connections.
Beej's Bit Bucket
2 months ago
- WebSockets enable two-way communication with a web server, reducing HTTP overhead by keeping the connection open.
- A WebSocket connection starts as HTTP and then upgrades to the WebSocket protocol, avoiding repeated request-response cycles.
- WebSockets allow the server to push unsolicited data to the client, solving a limitation of traditional HTTP.
- They use the same port as the web server (port 80) to help with firewall traversal.
- Browser support is strong except for IE9 and earlier; fallback libraries like Socket.IO can be used for older browsers.
- Practical example: a simple chat server and client implemented in NodeJS using the WebSocket protocol.
- Custom higher-level protocols (e.g., beej-chat-protocol) can be defined using JSON messages with a type and payload.
- Connection establishment involves the client requesting an upgrade; the server can accept or deny based on origin or protocol support.
- Normal communication involves sending and receiving JSON packets, with events for data arrival, closure, and errors.
Why Twitter is a Big Deal
2 months ago
- Twitter is a new messaging protocol where recipients are not specified.
- New protocols that take off are rare; only a few common ones like TCP/IP, SMTP, HTTP exist.
- Twitter's protocol is owned by a private company, which is even rarer.
- The founders' slow monetization may be an advantage because they didn't over-control it, making it feel like previous protocols.
ACP v2 is available in Draft
2 months ago
- Moving beyond turn-based interaction: session/update notifications can occur anytime, prompt response acknowledges message not end of turn, agent idle state signals readiness.
- Messages, tool calls, and terminal output use stable IDs for uniform patching (omit, null, replace, append); tool calls can be streamed without buffering.
- Diff overhaul: replaced oldText/newText with structured file changes (add, delete, modify, move, copy, binary, non-text) plus optional git_patch.
- Permission requests have required title and optional description with extensible subject, decoupling from tool call content.
- Forward compatibility by default: enum-like values accept unknown variants with _ prefix for extensions, built into schema.
- v2 is a draft; implement behind feature flags, support v1 and v2 side-by-side, participate in feedback.

protocol

Bringing MCP 2026-07-28 to Claude

Beej's Bit Bucket

Why Twitter is a Big Deal

ACP v2 is available in Draft