@arabold/docs-mcp-server 1.7.0 → 1.9.0

package/README.md

@@ -25,6 +25,7 @@ The server exposes MCP tools for:
 - Listing indexed libraries (`list_libraries`).
 - Finding appropriate versions (`find_version`).
 - Removing indexed documents (`remove_docs`).
+- Fetching single URLs (`fetch_url`): Fetches a URL and returns its content as Markdown.
 
 ## Configuration
 
@@ -250,11 +251,31 @@ npx -y --package=@arabold/docs-mcp-server docs-cli --help
 ```bash
 docs-cli scrape --help
 docs-cli search --help
+docs-cli fetch-url --help
 docs-cli find-version --help
 docs-cli remove --help
 docs-cli list --help
 ```
 
+### Fetching Single URLs (`fetch-url`)
+
+Fetches a single URL and converts its content to Markdown. Unlike `scrape`, this command does not crawl links or store the content.
+
+```bash
+docs-cli fetch-url <url> [options]
+```
+
+**Options:**
+
+- `--no-follow-redirects`: Disable following HTTP redirects (default: follow redirects)
+
+**Examples:**
+
+```bash
+# Fetch a URL and convert to Markdown
+docs-cli fetch-url https://example.com/page.html
+```
+
 ### Scraping Documentation (`scrape`)
 
 Scrapes and indexes documentation from a given URL for a specific library.
@@ -268,7 +289,7 @@ docs-cli scrape <library> <url> [options]
 - `-v, --version <string>`: The specific version to associate with the scraped documents.
   - Accepts full versions (`1.2.3`), pre-release versions (`1.2.3-beta.1`), or partial versions (`1`, `1.2` which are expanded to `1.0.0`, `1.2.0`).
   - If omitted, the documentation is indexed as **unversioned**.
-- `-p, --max-pages <number>`: Maximum pages to scrape (default: 100).
+- `-p, --max-pages <number>`: Maximum pages to scrape (default: 1000).
 - `-d, --max-depth <number>`: Maximum navigation depth (default: 3).
 - `-c, --max-concurrency <number>`: Maximum concurrent requests (default: 3).
 - `--ignore-errors`: Ignore errors during scraping (default: true).
@@ -471,13 +492,14 @@ This project uses [semantic-release](https://github.com/semantic-release/semanti
 **How it works:**
 
 1.  **Commit Messages:** All commits merged into the `main` branch **must** follow the Conventional Commits specification.
-2.  **Automation:** The "Release" GitHub Actions workflow automatically runs `semantic-release` on pushes to `main`.
+2.  **Manual Trigger:** The "Release" GitHub Actions workflow can be triggered manually from the Actions tab when you're ready to create a new release.
 3.  **`semantic-release` Actions:** Determines version, updates `CHANGELOG.md` & `package.json`, commits, tags, publishes to npm, and creates a GitHub Release.
 
 **What you need to do:**
 
 - Use Conventional Commits.
-- Merge to `main`.
+- Merge changes to `main`.
+- Trigger a release manually when ready from the Actions tab in GitHub.
 
 **Automation handles:** Changelog, version bumps, tags, npm publish, GitHub releases.