APIs & Authentication
What is the Model Context Protocol?
An open protocol from Anthropic for connecting LLMs to external tools, data sources, and prompts through a standardized client/server interface.
Also known as: MCP
MCP (Model Context Protocol) standardizes the wiring between an LLM-powered client (Claude Desktop, an IDE, a custom agent) and the resources it needs to do work: file systems, databases, APIs, search indexes, custom tools. Before MCP, every integration was a bespoke function-calling implementation; with MCP, a tool author writes one server and any compliant client can talk to it.
The protocol itself is JSON-RPC over stdio or HTTP-with-SSE. Servers expose three primitives: tools (callable functions with typed inputs and outputs), resources (readable data the client can pull into context), and prompts (parameterized templates the user can invoke). Capability negotiation at handshake time tells the client what the server supports.
For brand-data and scraping use cases, MCP is the natural way to expose Brand.dev-style APIs to an agentic workflow. An agent that can call a "lookup brand by domain" MCP tool and a "scrape a page as markdown" MCP tool can compose research flows that previously required custom glue code per integration.
In the wild
- →Claude Desktop connecting to a local filesystem MCP server to read project files
- →An IDE exposing its symbol index to the agent via an MCP server
- →A SaaS shipping an MCP server so its customers' agents can query the product without bespoke API plumbing
How Brand.dev uses mcp (model context protocol)
Endpoints in the Brand.dev API where this concept comes up directly.
FAQ
How is MCP different from a REST API?
REST is a transport pattern; MCP is a higher-level protocol over JSON-RPC with model-aware semantics for tools, resources, and prompts. You can wrap a REST API as an MCP server, but the inverse takes more work.
Who can use MCP?
Any LLM client and any tool author. The spec is open and there are SDKs in TypeScript, Python, and a growing list of other languages.
Is MCP only for Anthropic models?
No. Anthropic published it, but it is provider-neutral. Several non-Anthropic clients and open-source agent frameworks have started consuming MCP servers.
Related terms
An Application Programming Interface, a contract that lets one program request actions or data from another in a stable, documented way.
An API that follows REST conventions, using HTTP methods on resource URLs to model create/read/update/delete operations.
A user-defined HTTP callback, your URL gets POSTed to whenever an event happens in someone else's system, instead of you polling for changes.
JavaScript Object Notation, a lightweight text format for representing structured data, supported natively by every modern language.