Add Elasticsearch MCP server for PeaceLink site search #9

Open
opened 2026-08-20 14:37:56 +00:00 by francesco · 1 comment
Owner

Sibling repo, mirroring mcp-guardian. New ../mcp-elasticsearch/ FastMCP server exposing search over the existing ES cluster that indexes the full PeaceLink website. Register via MCP_SERVER_ELASTICSEARCH (or a dedicated MCP_ELASTICSEARCH_URL), add elasticsearch to the relevant research profiles' mcp_servers (start with RICERCA/CAMPAGNE, not all intents).

Open question to resolve during design: this ES index overlaps with the peacelink-* RAG sources already in pgvector (import_docs.py --source peacelink). Decide how to avoid the agent getting redundant hits for the same article from both paths — e.g. position ES as the fresher/complementary real-time source (like Guardian vs. static RAG) rather than a duplicate, or scope it to content/recency the RAG import doesn't cover.

Reference: RAG improvement discussion, [current conversation] — MCP recommended over the Wikipedia-style in-process tool because per-intent scoping and a potentially multi-operation surface (filter by category/date, fetch by ID) both fit the MCP pattern better.

Sibling repo, mirroring mcp-guardian. New ../mcp-elasticsearch/ FastMCP server exposing search over the existing ES cluster that indexes the full PeaceLink website. Register via MCP_SERVER_ELASTICSEARCH (or a dedicated MCP_ELASTICSEARCH_URL), add elasticsearch to the relevant research profiles' mcp_servers (start with RICERCA/CAMPAGNE, not all intents). Open question to resolve during design: this ES index overlaps with the peacelink-* RAG sources already in pgvector (import_docs.py --source peacelink). Decide how to avoid the agent getting redundant hits for the same article from both paths — e.g. position ES as the fresher/complementary real-time source (like Guardian vs. static RAG) rather than a duplicate, or scope it to content/recency the RAG import doesn't cover. Reference: RAG improvement discussion, [current conversation] — MCP recommended over the Wikipedia-style in-process tool because per-intent scoping and a potentially multi-operation surface (filter by category/date, fetch by ID) both fit the MCP pattern better.
Author
Owner

Related to peacelink/pck3s#40

Related to https://git.peacelink.it/peacelink/pck3s/issues/40
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
peacelink/ai-assistant#9
No description provided.