Glossary

MCP (Model Context Protocol)

The Model Context Protocol (MCP) is an open protocol launched by Anthropic in November 2024 that standardizes how an AI agent (Claude, ChatGPT, Cursor) connects to external tools or data sources — comparable to USB-C for LLMs.

Also known as

  • MCP
  • Model Context Protocol

Before MCP, every integration between an agent and a tool was proprietary: a custom OpenAI GPT could not reuse a Claude connector, and a tool defined in Cursor was not portable elsewhere. MCP provides a common tool description schema (JSON Schema), standardized transports (stdio, SSE, streamable HTTP), and a discovery (`listTools`) + execution (`callTool`) + authentication (Bearer, OAuth 2.1) protocol.

In practice, an MCP server exposes a tool catalogue via an HTTP endpoint (typically `/mcp/sse` for SSE transport or `/mcp` for streamable HTTP), and any compatible client (Claude Desktop, Cursor, getchatsocial.com, ChatGPT via plugin) can call them. By 2026 it has become the de facto standard for exposing a tool catalogue to an AI agent.

In the getchatsocial.com product

getchatsocial.com is an MCP client that connects to the Brandyze MCP server (https://api.brandyze.fr/mcp/sse, 206 tools) via SSE. The same connection can be used from Claude Desktop or Cursor — the user chooses their preferred interface.

FAQ

  • Is MCP an open standard?

    Yes — the MCP specification is open-source (Apache 2.0) and the official SDKs (Python, TypeScript, Swift, Kotlin) are public. Anthropic designed it to be adopted across the entire industry.

  • Which MCP clients exist in 2026?

    The main ones: Claude Desktop (official), Cursor (official), Continue.dev, Cline, Windsurf, and numerous SaaS products that have integrated MCP as a client (including getchatsocial.com). ChatGPT has supported MCP since 2026 via plugins.

  • What is the difference between MCP and a classic REST API call?

    MCP standardizes tool descriptions and their orchestration by an agent. A classic REST call is an isolated endpoint. MCP adds the "agent discovers, selects, and chains" layer that doesn't exist natively in REST.