Slice.js Documentation MCP
This MCP server provides Slice.js documentation access for listing, searching, retrieving, and bulk-loading docs.
List all available documentation sections/categories.
Search documentation by keyword/phrase with a configurable result limit.
Fetch full content for one or more documentation IDs, optionally with metadata.
Retrieve the complete documentation bundle for comprehensive LLM context, with a confirmation warning.
Use namespace-aware framework and component catalog tools (per README) to list/search/get docs from separate sources.
Integrates with GitHub to dynamically discover, index, and retrieve documentation files from repositories, managing API rate limits while fetching content.
Provides full-text search and retrieval capabilities for Markdown documentation, allowing AI tools to fetch specific sections or complete documentation bundles for context.
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., "@Slice.js Documentation MCP How do I handle routing in Slice.js?"
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.
Slice.js Documentation MCP
An MCP (Model Context Protocol) server that provides access to Slice.js documentation from the official GitHub repository. This server allows AI assistants and tools to query, search, and retrieve documentation seamlessly.
Features
Dynamic Documentation Discovery: Automatically discovers and indexes all documentation files from the GitHub repo
Intelligent Caching: Infinite session cache to minimize API requests and improve performance
Full-Text Search: Search across all documentation with keyword matching
Content Retrieval: Fetch specific documentation pages or the complete documentation bundle
Lazy Initialization: Docs structure is loaded on-demand when first needed
Related MCP server: Unified Docs Hub
Installation
Global Installation (Recommended)
npm install -g slicejs-mcpUsing npx (No Installation Required)
npx slicejs-mcpUsage
The MCP server runs as a stdio-based service, perfect for integration with AI assistants and MCP-compatible tools.
Basic Usage
npx slicejs-mcpIntegration with MCP Clients
This server is designed to work with MCP-compatible clients. When launched, it exposes the original framework tools plus namespace-aware tools for the Slice.js Components catalog:
Tools
1. list_docs
Returns a list of all available documentation sections and categories.
Parameters: None
Response: JSON array of documentation items with id, title, and path.
Example:
[
{
"id": "getting-started",
"title": "Getting Started",
"path": "markdown/getting-started.md"
}
]2. search_docs
Searches across all documentation using keywords or phrases.
Parameters:
query(string, required): Search termmax_results(number, optional, default: 5): Maximum number of results
Response: JSON array of search results with snippets and metadata.
3. get_doc_content
Fetches the full content of specific documentation page(s).
Parameters:
doc_id(string or string[], required): Documentation ID(s) to fetchinclude_metadata(boolean, optional, default: false): Include additional metadata
Response: JSON object(s) with document content, title, and optional metadata.
4. get_llm_full_context
Fetches the complete documentation bundle (~2000 lines) for comprehensive LLM context.
Parameters: None
Response: Complete documentation text
Note: This consumes considerable tokens but provides all documentation in one request.
Framework catalog tools
These tools make the documentation source explicit while preserving the original tools above:
slice_framework_list_docsslice_framework_search_docsslice_framework_get_doc
They read from slicejs_docs and return authored Markdown plus provenance metadata.
Slice.js Components catalog tools
These tools provide access to Visual and Service component documentation:
slice_components_list_docsslice_components_search_docsslice_components_get_doc
The Components tools read the catalog manifest published by slicejs-components and retrieve
the original Markdown document, including its examples and :::script blocks. They do not execute
documentation examples or modify the project.
The catalog manifest is expected at:
https://raw.githubusercontent.com/VKneider/slicejs-components/master/agent/docs-manifest.jsonExamples
List all documentation
// Via MCP client
await callTool("list_docs", {});Search for routing information
await callTool("search_docs", {
query: "routing",
max_results: 3
});Get specific documentation
await callTool("get_doc_content", {
doc_id: "getting-started/routing"
});Get full documentation context
await callTool("get_llm_full_context", {});Architecture
Framework source: Documentation fetched from https://github.com/VKneider/slicejs_docs
Components source: Markdown and manifest fetched from https://github.com/VKneider/slicejs-components
Caching: Infinite session cache prevents redundant API calls
Initialization: Lazy loading of document structure on first tool use
Rate Limiting: Optimized to stay within GitHub API limits (60 req/hour)
The two catalogs are separate because framework behavior and component APIs have different versioning and ownership. The MCP uses the same list/search/get pattern for both sources, while the authored Markdown remains the canonical content.
Environment overrides are available for local development and mirrors:
SLICE_FRAMEWORK_DOCS_BASE_URL
SLICE_FRAMEWORK_DOCS_REVISION
SLICE_FRAMEWORK_DOCS_API_BASE
SLICE_COMPONENTS_MANIFEST_URL
SLICE_COMPONENTS_RAW_BASE_URLDevelopment
Prerequisites
Node.js >= 18
npm or yarn
Setup
git clone <repo>
cd slicejs-mcp
npm install
npm run buildRunning Locally
npm start
# or
node dist/index.jsTesting with MCP Inspector
npx @modelcontextprotocol/inspector node dist/index.jsContributing
Contributions welcome! Please ensure:
All tools maintain backward compatibility
Cache behavior is preserved
Error handling is robust
License
MIT
Available Tools
4 toolsget_doc_contentC
Fetches full content of specific doc page(s)
Inputs: doc_id (required), include_metadata.
get_llm_full_contextA
Fetches the complete documentation bundle (~2000 lines, consumes considerable tokens but provides all documentation in one go). IMPORTANT: Ask the user for confirmation before executing this tool as it will add the entire Slice.js documentation to the context.
Inputs: no named parameters.
list_docsB
Returns available documentation sections/categories
Inputs: no named parameters.
search_docsC
Searches across all docs by keyword/phrase
Inputs: query (required), max_results.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: get_doc_content retrieves specific pages, get_llm_full_context fetches the entire bundle, list_docs shows available sections, and search_docs performs keyword searches. There is no overlap or ambiguity in their functions.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_doc_content, list_docs, search_docs). The naming is predictable and readable throughout the set.
With 4 tools, the count is reasonable for a documentation server, covering core needs like listing, fetching, and searching. It might be slightly thin for advanced use cases, but it's well-scoped for basic documentation access.
The toolset provides good coverage for documentation retrieval: listing, searching, and fetching content (both specific and full). A minor gap is the lack of update or management tools, but this is acceptable for a read-only documentation server.
Maintenance
Related MCP Connectors
Versioned documentation registry and semantic search for AI tools and coding assistants.
Tailor Platform for AI assistants: search, list and read the platform documentation.
Docsy gives AI assistants current, version-specific documentation for libraries, frameworks and SDKs. Resolve library IDs and versions, then search and fetch focused official documentation with original source links using five read-only MCP tools. Hosted Streamable HTTP with OAuth 2.1 sign-in.
Access and search Branch's official API documentation directly within any AI agent or client.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceTransforms any GitHub repository into a documentation hub for AI assistants, enabling access to up-to-date documentation and code to eliminate hallucinations. Supports repository-specific and dynamic endpoints with smart search capabilities.35 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with searchable access to documentation from 170+ curated repositories and 1000+ popular GitHub projects across 20+ categories including trading, AI/ML, DevOps, and web development.2MIT
- AlicenseNot gradedqualityCmaintenanceProvides AI coding agents with access to CleanSlice architecture documentation, rules, and conventions. It enables users to search documentation and retrieve essential patterns to help AI build applications correctly.18MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with direct access to local Markdown documentation libraries, enabling them to list, read, and search through docs on demand.MIT