And even that acronym expansion doesn't help, IMHO, whereas "a standard that's a cross between Language Server Protocol and OpenAPI, targeting LLM consumers" (emphasis on the API not AI) is hopefully a little better -- depending on whether the reader is already familiar with the problems that LSP and OpenAPI are solving
As far as I know there's still missing the UDDI-ish "discoverability" piece, although maybe one of the upcoming MCP standard releases will include /.well-known/mcp-servers type thing, or a SRV record, or both
Me neither: MCP Servers are systems that provide context, tools, and prompts to AI clients. They can expose data sources like files, documents, databases, and APIs (https://mcp.so/)
(I didn't know what MCP was.)