A newcomer asks which existing protocol the MCP specification names as an inspiration for its ecosystem-wide approach to integration. Which answer is correct?
Select an answer to reveal the explanation.
Short Explanation
Remember how one language server can light up autocomplete in lots of different editors? That's the move MCP borrows: you build an integration once and every compatible AI app can use it. ODBC, OpenAPI and gRPC are real standards, but they're not the one the spec names.
Full Explanation
The MCP specification states that it takes some inspiration from the Language Server Protocol. LSP standardizes how support for a programming language is added across an entire ecosystem of development tools: a language server implemented once works in every editor that speaks LSP. MCP applies the same idea to AI applications, standardizing how additional context and tools are integrated so that one server can serve many hosts. The Open Database Connectivity standard is a reasonable analogy for uniform access to data stores, but it is not the protocol the specification cites, and MCP covers tools and prompts rather than only data queries. The OpenAPI Specification describes REST endpoints for documentation and code generation; MCP does not describe existing APIs but defines its own JSON-RPC message set. gRPC is an RPC framework with its own serialization and transport, whereas MCP uses JSON-RPC 2.0 over stdio or Streamable HTTP. Exam caveat: the comparison is about ecosystem structure, not wire format, so the LSP link does not mean MCP reuses LSP messages. Operational check: when explaining MCP to a team, use the LSP comparison to show why a server written once becomes usable in many hosts without host-specific adapters.