#mcp

Anthropic's own four-phase guide to building an MCP server — research, implement, review, then generate ten evaluations that test whether a model can actually use it.

Anthropic's Connectors Directory is a gated, vetted distribution channel with no published review clock — a reminder that shipping an MCP server isn't the same as getting it in front of users.

The 2026-07-28 spec drops MCP's session handshake, hardens auth, and ships day-one across four SDKs with six hyperscalers behind it — the protocol crossed from experiment to backed standard, which resets both the positioning window and the migration bill.

Agent Plugins 1.0.0 went public as an open, vendor-neutral packaging standard — a directory with a `plugin.json` manifest and fixed locations for Agent Skills and MCP servers — refined collaboratively by AWS, Anysphere, GitHub, Microsoft, OpenAI and Vercel, with a Technical Steering Committee drawn from the same set. ChatGPT, Codex, Cursor, GitHub Copilot, Kiro and VS Code support it at launch, which means a plugin author packages components once instead of repackaging the same skill for each client.

Okta announced the Cross App Access (XAA) protocol with more than 25 launch partners including Anthropic, Asana, Canva, Cloudflare, Datadog, Figma and Zoom, routing app-to-app authorization through the customer's own identity provider instead of point-to-point OAuth grants. Auth0 is enabling it natively in tenants as declarative dashboard configuration with no application code changes — Resource App support is available now, Requesting App support via Token Vault is slated for 2026-08-31 — and positions XAA as the foundation of the Enterprise-Managed Authorization extension to MCP.

Sinch launched Agent Tools: VS Code/JetBrains/Open VSX extensions, an MCP server exposing live Sinch API definitions, a Simulator Mode that tests integrations before an account exists, and "Sinch Skills" — structured implementation guidance for AI coding assistants including Claude Code, Cursor, GitHub Copilot and ChatGPT Desktop. It joins a growing roster of vendors making their platforms "agent-safe by design" rather than just documented for humans.

Y Combinator-backed Armature launched on Show HN with product analytics that wrap your MCP server to reconstruct agent sessions — user intent, agent reasoning, task success and failure — the way PostHog or Amplitude reconstruct a human click stream. It picked up 40 points, and it is not the first entrant: AgentCat (mcpcat.io) already sells the same "agent experience" category.

Developer Josh Symonds documented a dated timeline of his MCP connector submission to Anthropic's directory: filed 2026-03-22, told as late as 06-15 it was "in the review queue," then informed on 07-30 the queue had been discarded and he would need to resubmit — against OpenAI approving the same connector for its own directory in 29 days. It is a single account, not an Anthropic-confirmed pattern, but it is the first concrete stranded-integrator story since the MCP spec went stateless.

Unblocked published a piece arguing that raw MCP connectors do not replace a curated context layer — that giving an agent access to every system is not the same as giving it the right context. It landed at 8 points with no comments, in the same week MCP support consolidated into a baseline expectation across every major vendor.

GitHub moved Copilot code review's agent skills and MCP support from preview to general availability on 2026-07-29: a SKILL.md file under .github/skills steers the reviewing agent, MCP tool calls are deliberately restricted to read-only, and new per-comment attribution shows which skill or server produced each suggestion. Available across Copilot Pro, Pro+, Business and Enterprise.

Anthropic published its rollout of the 2026-07-28 MCP spec on 2026-07-29: MCP Apps live in Claude, enterprise-managed auth, observability dashboards for connector developers, tunnels in research preview, and a connectors directory past 950 servers. The post gives concrete shipped features but still no firm completion date for the full stateless cutover.

The new Model Context Protocol spec drops `initialize` and session IDs so any server instance can answer any request behind a plain load balancer, graduates Tasks and MCP Apps into a versioned extensions framework, and hardens auth with RFC 9207 issuer validation in place of Dynamic Client Registration. All four Tier-1 SDKs shipped support on publication day, with AWS, Cloudflare, Figma, Google Cloud, Microsoft and Netlify publicly committed.