Repository navigation
Releases: salesforcebob/sf-doc-scraper
Releases · salesforcebob/sf-doc-scraper
Release list
v1.3.4 - Fix Heroku Managed Inference Compatibility
Fix
Heroku Managed Inference Support
Fixed transport mode mapping to work correctly with Heroku Managed Inference and Agents:
| Command | Before | After |
|---|---|---|
serve |
HTTP Server ❌ | STDIO Server ✅ |
web |
HTTP Server | HTTP Server (unchanged) |
| (no args) | STDIO Server | STDIO Server (unchanged) |
Procfile Update
Renamed MCP process type to follow Heroku convention:
web: node dist/mcp-server.js web
mcp-sf-docs: node dist/mcp-server.js serve
How It Works Now
- Local npm usage:
npx @salesforcebob/sf-docs-mcp-serverruns STDIO (Cursor, Claude Desktop) - Heroku web dyno: HTTP server for SSE/toolkit URL
- Heroku Managed Inference: STDIO mode for tool execution in one-off dynos
Full Changelog
v1.3.3 - Improved Heroku Puppeteer Support
Improvements
Heroku Buildpack Configuration
- Updated
app.jsonto use the official jontewks/puppeteer-heroku-buildpack from GitHub - Buildpack order: Puppeteer buildpack first, then Node.js
- Updated Chrome executable path for buildpack compatibility
Puppeteer Launch Options
- Added
--disable-dev-shm-usageflag for better Heroku compatibility - Server now respects
PUPPETEER_EXECUTABLE_PATHenvironment variable - Enables use of Chrome installed by Heroku buildpack
One-Click Deploy
Full Changelog
v1.3.2 - Clean up repo
Cleanup
- Removed
node_modules/anddocs/folders from git tracking (they were committed before being added to .gitignore)
Full Changelog
v1.3.1 - Update Procfile process name
v1.3.0 - Heroku Deployment & Enhanced Documentation
What's New
🚀 Heroku Deployment Support
One-click deploy to Heroku with the new Deploy button in the README. The server now supports both stdio (local) and HTTP (remote) modes.
HTTP Server Mode
Run the server in HTTP mode for remote access:
npx @salesforcebob/sf-docs-mcp-server serveEndpoints:
GET /health- Health checkGET /docs- DocumentationPOST /mcp- MCP HTTP endpoint
📚 Enhanced Documentation
- Added badges (npm version, Node.js, License, MCP Server)
- Comprehensive table of contents
- Troubleshooting guide
- Disclaimer section
- Updated AGENT_GUIDE with all page types
New Files
Procfile- Heroku process definitionapp.json- Heroku app configuration with Puppeteer buildpack
Supported Page Types (7 total)
guide- Guide pagesreference- Reference pages with markdownapi-reference- API summary pagesapi-type- Type definition pagesapi-method- Method/endpoint pagesapi-documentation- General API documentationoverview- Landing/overview pages
Full Changelog
v1.2.3 - Add overview/landing page support
What's New
New Page Type: overview
Added support for overview/landing pages that use dx-group-text and dx-features-list elements. These are the documentation landing pages like:
/docs/einstein/genai/docs/einstein/genai/overview
Supported Page Types (7 total)
guide- Guide pages (/guide/*)reference- Reference pages with markdown contentapi-reference- API summary pagesapi-type- Type definition pagesapi-method- Method/endpoint pagesapi-documentation- General API documentationoverview- NEW Landing/overview pages
Full Changelog
v1.2.2 - Add api-method-documentation support
What's New
New Page Type Support: api-method-documentation
Added support for API method/endpoint documentation pages like GraphQL's "Send Query" page. These pages have a different shadow DOM structure than other API reference pages.
Bug Fixes
- Fixed
api-type-documentationelement detection (was incorrectly namedapi-type-documentin v1.2.0) - Improved content extraction from deeply nested shadow DOMs
Supported Page Types
guide- Guide pages (/guide/*)reference- Reference pages with markdown contentapi-reference- API summary pagesapi-type- Type definition pages (ClientIdParam, CookieIdParam, etc.)api-method- NEW Method/endpoint pages (Send Query, etc.)api-documentation- General API documentation pages
Full Changelog
v1.1.0 - Add support for AMF API reference pages
Features
- Support for AMF API reference pages - Now handles deeply nested shadow DOM structures used by OpenAPI/RAML-based API documentation (like Einstein API docs)
- Traverse
doc-amf-reference→doc-amf-topic→api-summaryshadow DOM chain - Extract API title, version, overview, protocols, and base URL from API summary pages
Page Types Now Supported
| Page Type | Structure | Example |
|---|---|---|
guide |
doc-content-layout with shadow DOM slot |
/guide/* pages |
reference |
doc-amf-reference with .markdown-content |
Markdown-based references |
api-reference |
Nested shadow DOMs (api-summary) |
Einstein API Summary pages |
api-documentation |
Nested shadow DOMs (api-documentation) |
API endpoint pages |
Tested With
- Einstein Profile Connector API documentation
v1.0.1
SF Docs MCP Server v1.0.1
Features
- MCP server for scraping Salesforce developer documentation
- Converts docs to clean Markdown
- Supports guide pages and reference pages
- Handles shadow DOM and custom web components
TypeScript
- Full TypeScript conversion with type definitions
- Strict mode enabled
Installation
npm install -g @salesforcebob/sf-docs-mcp-server