Getting Started
DocShark is installed with Bun and can be used as an MCP server across various AI clients.
Setup
Recommended install path
Use `bunx` for ad hoc runs. Switch to a global Bun install only if your team
benefits from a shorter command name.
Installation
# Install globally (optional)
bun add -g docshark
# Or run on the fly
bunx docshark [command] Works with standard clients
Claude Desktop, Cursor, and VS Code can all launch DocShark through command-based MCP config.
No daemon required
Run `docshark start --stdio` directly from the client command; no extra service management needed.
IDE & Desktop Integrations
Claude Desktop
Edit your claude_desktop_config.json:
- macOS/Linux:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"docshark": {
"command": "bunx",
"args": ["-y", "docshark", "start", "--stdio"]
}
}
} Cursor
- Go to Settings > Models > MCP
- Add a command-based server:
- Name:
docshark - Command:
bunx -y docshark start --stdio
- Name:
VS Code (Copilot)
Add to your workspace .vscode/settings.json or .vscode/mcp.json:
{
"mcpServers": {
"docshark": {
"command": "bunx",
"args": ["-y", "docshark", "start", "--stdio"]
}
}
} Basic Usage
# Add a documentation site
bunx docshark add https://svelte.dev/docs
# List indexed libraries
bunx docshark list
# Search across all docs
bunx docshark search "component lifecycle"
# Search within a specific library
bunx docshark search "runes" --library svelte-dev
# Get a specific page
bunx docshark get svelte-dev /docs/svelte/overview Available Tools
Once connected as an MCP server, DocShark exposes these tools to your AI assistant:
| Tool | Action | Parameters |
|---|---|---|
manage_library | Add, rename, refresh, remove, inspect | action, url, name, version, max_depth, current_name, new_name, library |
search_docs | Search indexed docs | query, library, limit |
list_libraries | List all indexed libraries | status |
get_doc_page | Read a specific page | url, library, path |