Dedalus MCP Documentation Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Dedalus MCP Documentation Server search for rate limiting configuration in the docs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Dedalus MCP Documentation Server
An MCP server for serving and querying documentation with AI capabilities. Built for the YC Agents Hackathon.
Quick Start (Local Development)
# Install uv package manager (same as Dedalus uses)
brew install uv # or pip install uv
# Install dependencies
uv sync --no-dev
# Configure API keys for AI features
cp config/.env.example .env.local
# Edit .env.local and add your OpenAI API key
# Test
uv run python tests/test_server.py
# Run
uv run mainRelated MCP server: Dedalus MCP Documentation Server
Deploy to Dedalus
What Dedalus Needs
pyproject.toml- Package configuration with dependenciesmain.py(root) - Entry point that Dedalus expectssrc/main.py- The actual MCP server codedocs/- Your documentation files
Deployment Steps
Set Environment Variables in Dedalus UI:
OPENAI_API_KEY- Your OpenAI API key (required for AI features)
Deploy:
dedalus deploy . --name "your-docs-server"How Dedalus Runs Your Server
Installs dependencies using
uv syncfrompyproject.tomlRuns
uv run mainto start the serverServer runs in
/appdirectory in containerDocs are served from
/app/docs
Features
Serve markdown documentation
Search across docs
AI-powered Q&A (with OpenAI)
Rate limiting (10 requests/minute) to protect API keys
Ready for agent handoffs
Tools Available
list_docs()- List documentation filessearch_docs()- Search with keywordsask_docs()- AI answers from docsindex_docs()- Index documentsanalyze_docs()- Analyze for tasks
Documentation
See docs/ directory for:
License
MIT
Available Tools
5 toolsanalyze_docsC
Analyze documentation for specific tasks (foundation for agent handoffs)
Args:
task: Analysis task (e.g., "find_gaps", "generate_outline", "check_consistency")
docs: Optional list of specific documents to analyze
output_format: Output format (summary, detailed, structured)
Returns:
Analysis results ready for agent handoff
Inputs: task (required), docs, output_format. Returns: result
ask_docsC
Answer questions about documentation using AI
Args:
question: The question to answer
context_docs: Optional list of document paths to use as context
max_context_length: Maximum characters of context to include
user_id: Optional user identifier for rate limiting
Returns:
AI-generated answer with sources
Inputs: question (required), context_docs, max_context_length, user_id. Returns: result
index_docsB
Index or re-index all documentation for improved search
Args:
rebuild: Whether to rebuild the entire index from scratch
Returns:
Indexing statistics
Inputs: rebuild. Returns: result
list_docsB
List all available documentation files
Args:
directory: Optional subdirectory to list (relative to docs root)
Returns:
List of document metadata
Inputs: directory. Returns: result
search_docsA
Search documentation using keyword matching (semantic search ready)
Args:
query: Search query string
max_results: Maximum number of results to return
search_content: Whether to search in document content
search_titles: Whether to search in document titles
Returns:
List of matching documents with relevance scores
Inputs: query (required), max_results, search_content, search_titles. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: analyze_docs performs analysis tasks, ask_docs answers questions via AI, index_docs handles indexing, list_docs enumerates files, and search_docs performs keyword searches. The descriptions reinforce these distinct roles, making tool selection unambiguous for an agent.
All tools follow a consistent verb_noun pattern with snake_case naming (e.g., analyze_docs, ask_docs, index_docs, list_docs, search_docs). This predictable structure enhances readability and usability, with no deviations or mixed conventions across the set.
With 5 tools, this server is well-scoped for documentation management, covering core operations like listing, searching, indexing, analyzing, and querying. Each tool earns its place without redundancy, making the count appropriate for the domain's typical workflows.
The tool set provides complete coverage for documentation management, including CRUD-like operations (list, search, index) and advanced AI functionalities (analyze, ask). There are no obvious gaps; agents can perform end-to-end tasks from discovery to analysis without dead ends.
Maintenance
Related MCP Connectors
Team docs served to AI agents over MCP - search, Markdown reads, version pinning, read audit.
Versioned documentation registry and semantic search for AI tools and coding assistants.
Docs Q&A: search 169 data and AI guides, fetch any page as markdown. Read-only, keyless.
Ingest, manage, and retrieve documents for RAG-powered AI applications
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables serving and querying documentation with AI capabilities, allowing users to search, ask questions, and get AI-powered answers from their documentation files. Built for seamless deployment on the Dedalus platform with OpenAI integration for enhanced document analysis.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI-powered querying and serving of markdown documentation with search, Q\&A capabilities, and document analysis. Built for the YC Agents Hackathon with OpenAI integration and rate limiting protection.MIT
- AlicenseNot gradedqualityDmaintenanceEnables serving and querying documentation with AI-powered capabilities including markdown file serving, keyword search, and intelligent Q\&A using OpenAI integration.MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to navigate and query hierarchical documentation structures, supporting markdown files with YAML metadata and OpenAPI 3.x specifications. It features intelligent full-text search, metadata filtering, and a built-in web interface for both human and AI-driven documentation access.6MIT