Where MCP Stands
MCP (Model Context Protocol) was open-sourced by Anthropic in November 2024. By March 2026 the SDK was hitting 97 million monthly downloads. Anthropic donated the protocol to the Agentic AI Foundation in December 2025, making it vendor-neutral.
The July 2026 spec update added stateless operation mode, which removes the requirement for persistent server connections. This makes MCP servers cheaper to host and easier to deploy on serverless infrastructure.
Tools That Ship Native MCP
These tools now ship their own MCP server, maintained by the tool vendor:
- **Notion** (`@notionhq/notion-mcp-server`) reads and writes pages, databases, and blocks
- **Figma** (`figma-developer-mcp`) reads component and design data, exports assets
- **Linear** native MCP for issue management and project tracking
- **GitHub** official MCP server for repo operations, PRs, and issues
- **Firecrawl** (`firecrawl-mcp`) for web scraping and search with structured output
- **n8n** (`n8n-mcp`) for triggering workflows and reading execution status
All of these install via npx and configure the same way: add to your agent's MCP server list with the required API key.
What This Means for Agent Builders
A year ago, connecting an agent to Notion or Figma required a custom integration. Now you add three lines to your config and restart.
The ecosystem is still fragmented. Not every MCP server is maintained equally. Some have authentication gaps. Before adding a community MCP server to a production agent, read the source code. The official vendor-maintained ones (Notion, Figma, GitHub) are more reliable.
The Stateless Spec
The July 2026 stateless spec matters for deployment. Previously, MCP servers needed to maintain a persistent stdio connection. Stateless mode lets you deploy MCP servers as HTTP endpoints that handle one request at a time. This works better on serverless platforms (Vercel Functions, Cloudflare Workers) and simplifies scaling.
Most existing MCP servers do not support stateless mode yet. It will take months for the ecosystem to catch up.
Comments (0)