Implement a common infraestructure to have MCP servers in Concon #13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add an MCP (Model Context Protocol) server to Concon as an agent-friendly access layer in front of the existing SPARQL, GSP, and HTTP endpoints. The goal is to give any MCP-compliant client (e.g., Claude, Cursor, internal agents, future tools) a uniform, self-describing, typed surface for reading corpora, fetching documents, querying the knowledge graph, and submitting named graphs, without bespoke per-client integration. Build it as shared deterministic infrastructure (auth, backend clients, validators, audit logging, error mapping) supporting a curated set of typed tools, rather than a loose collection of independent handlers—so that adding a new tool is a thin handler on top of the shared core.