LangLa Server MCP
Related Servers
Alternatives to LangLa Server MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceServes documentation for Git repositories via MCP, providing tools to search docs, retrieve feature details, WIP status, and full context. Enables LLM agents to access human and LLM-optimized documentation through stdio or SSE transports.MIT
- AlicenseNot gradedqualityBmaintenanceRead-only MCP server for Markdown, MDX, and OpenAPI docs, exposing list, search, fetch, and OpenAPI spec tools over stdio.1MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for reading and listing JSON documents, designed to be used with Claude Haiku and Headroom compression to reduce token usage. It demonstrates an end-to-end MCP tool-use loop with stdio transport.-
- FlicenseNot gradedqualityBmaintenanceReusable, read-only MCP server that exposes a repo's knowledge files (backlog docs, decisions, design notes) as MCP resources over stdio.-
- FlicenseNot gradedqualityCmaintenanceEnables clients to interact with a bundled documentation corpus through MCP tools and resources over HTTP or stdio, and provides a trajectory evaluation harness for grading agent performance.1-
- AlicenseNot gradedqualityAmaintenanceServes a live code-graph workbench over stdio for MCP clients/agents, enabling Cypher queries and codebase analysis via KGLite tools.MIT
TDQS
Scored across 5 tools
Each tool targets a distinct access pattern: listing files, reading a whole file, searching free text, and looking up a specific MSG number. read_doc and get_msg overlap slightly since both return document content, but get_msg is clearly scoped to MSG-numbered entries, so an agent can choose reliably.
Four of five tools follow a clean verb_noun pattern (read_doc, list_docs, search_docs, get_msg). server_overview breaks the pattern by being noun-only, a minor but noticeable deviation.
Five tools is well-scoped for a documentation-retrieval server, with each tool covering a distinct lookup strategy. No redundant or filler tools.
The surface covers the core docs workflow: overview, listing, full read, free-text search, and targeted MSG lookup. Minor gaps exist, such as no way to enumerate all MSG entries or page through very large documents, but agents can work around these via search_docs.