LXAgents MCP Server
Delivers the LXAgents shared agent instruction set via MCP prompts and resources. It includes read-only tools for setting up and checking agent instructions in repositories.
README
mcp-server
The MCP server that delivers the LXAgents shared agent instruction set. A repository connects it as a connector and reads the conventions it needs — branching, commits, pull requests, task workflow, the creators, the directory architecture — instead of cloning or vendoring a copy of them.
- Server id:
lxagents-agents-base - Package:
@lxagents/agents-base - Surface: MCP prompts and resources, plus four read-only tools for clients that only enumerate tools.
Key features
agents-setupprompt — the full setup procedure that builds a repository'sAGENTS.md,.agents/tree, wiki, and memory.check-duplicate-agents-instructionprompt — finds instructions a repository duplicates from the shared set and removes them. Runs only when asked.- 25 instruction resources under
agents://, plusagents://manifest.jsonlisting every file with a content hash — one read instead of walking the set. - Four read-only tools —
agents_setup,agents_check_duplicate_instructions,agents_list_instructions,agents_read_instruction— delivering the same content as the prompts, for clients that surface tools only. - Many clients at once. Content is loaded once into a frozen registry; each request or session gets its own server instance, so nothing is shared and any process can serve any request.
Quick start
npm install
npm test
# Local, over stdio
npm start
# Remote connector surface, over streamable HTTP
npm run start:http # http://localhost:3000/mcp
With Docker:
docker compose up --build
Connect it
Add a custom connector pointing at https://<host>/mcp, named
lxagents-agents-base. Include the /mcp path — without it the handshake fails,
and clients report that as a sign-in error rather than a wrong address. For local development over stdio, see
wiki/guides/connect-a-repository.md.
Documentation
- Overview — what this serves and why it is a server.
- Architecture — registry, transports, concurrency.
- MCP surface — every prompt and resource.
- Local setup — running and testing it.
Working with agents
The instruction set this server delivers is also the instruction set this repository
follows. Start at AGENTS.md; the canonical content lives in
content/.
License
MIT — see LICENSE.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.