Model Context Protocol (MCP)
An open protocol (modelcontextprotocol.io) for wiring an LLM to external data and
tools via standardized MCP servers. It is a bridge node: it connects this wiki’s
knowledge-management cluster (A) with the agent tooling now in the sibling
agentic-tooling-wiki (B) — which is why it stays here and is linked cross-wiki.
Where it shows up
- In the agent tooling (agentic-tooling-wiki): claude-financial-services uses MCP to reach 10+ data providers (Daloopa, Morningstar, FactSet, Moody’s, LSEG, …); claude-skills-ppc frames skills × MCP = agency (live Google Ads data + the ability to execute changes).
- In the knowledge-management cluster (here), qmd ships as an MCP server so an LLM can use it as a native search tool over a markdown wiki.
- gbrain exposes 30+ tools over MCP (stdio + HTTP with OAuth 2.1) to a wide range of clients (Claude Code, Cowork, Cursor, ChatGPT, Perplexity) — making it the clearest example in the wiki of MCP as the universal agent-to-knowledge interface.
Why it matters here
MCP is the common substrate beneath both clusters: the standard way an LLM agent gets access to external knowledge/tools. For the llm-wiki pattern specifically, an MCP-exposed search tool (qmd) is the recommended upgrade path once the index-file approach stops scaling.
Related
qmd · gbrain · claude-financial-services · claude-managed-agents