sf-architect-mcp
Scrapes, indexes, and serves Salesforce Architect documentation locally, enabling fast offline RAG-powered search and retrieval for AI coding assistants.
README
SF Architect MCP
An MCP server that scrapes, indexes, and serves the Salesforce Architect documentation locally — enabling fast, offline, RAG-powered search and retrieval for AI coding assistants.
Built with Model Context Protocol, cheerio, SQLite, and Turndown.
What it does
- Scrapes
architect.salesforce.comusing fetch + cheerio (the site is server-side rendered) - Indexes content into a local SQLite database with section-aware chunking
- Searches using multi-term keyword scoring with section and language filters
- Supports 17 languages mirroring the site's locale structure
- Exposes MCP tools, resources, and prompts so your AI assistant can navigate and query the docs naturally
Prerequisites
- Node.js ≥ 18
- No browser binary required — scraping uses plain HTTP requests
Installation
git clone https://github.com/morettimarco/salesforce_architect_MCP.git
cd salesforce_architect_MCP
npm install
npm run build
The compiled server will be at dist/index.js.
Setup in your coding agent
Replace /absolute/path/to/sf-architect-mcp with the actual path where you cloned this repo.
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"sf-architect": {
"command": "node",
"args": ["/absolute/path/to/sf-architect-mcp/dist/index.js"]
}
}
}
Claude Code (CLI)
claude mcp add sf-architect node /absolute/path/to/sf-architect-mcp/dist/index.js
Or edit ~/.claude/settings.json (global) or .claude/settings.json (project-level):
{
"mcpServers": {
"sf-architect": {
"command": "node",
"args": ["/absolute/path/to/sf-architect-mcp/dist/index.js"]
}
}
}
Cursor
Edit .cursor/mcp.json in your project root (or ~/.cursor/mcp.json for global):
{
"mcpServers": {
"sf-architect": {
"command": "node",
"args": ["/absolute/path/to/sf-architect-mcp/dist/index.js"]
}
}
}
Windsurf
Edit ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"sf-architect": {
"command": "node",
"args": ["/absolute/path/to/sf-architect-mcp/dist/index.js"]
}
}
}
VS Code (GitHub Copilot)
Edit .vscode/mcp.json in your workspace:
{
"servers": {
"sf-architect": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/sf-architect-mcp/dist/index.js"]
}
}
}
First-time setup
Once the server is running in your agent, use the scrape-docs prompt or call the tool directly:
scrape_full → language_filter: "en" (or your preferred language)
This fetches the sitemap, scrapes all pages with Puppeteer, converts them to Markdown, and stores them in a local SQLite database at ~/.sf-architect-mcp/sf-architect.db.
A full English scrape takes roughly 2–3 minutes (≈ 115 pages, 3 concurrent requests).
Tools
| Tool | Description |
|---|---|
scrape_full |
Wipe the database and re-scrape everything from scratch |
scrape_incremental |
Scrape only new, changed, or previously failed pages |
search_architect_docs |
Keyword search across indexed content with relevance scoring |
read_architect_page |
Read a page's full Markdown content by URL (supports max_chars) |
read_architect_page_summary |
Lightweight summary: title, headings, word count, 500-char preview |
get_section_summary |
Page count, total words, and title list for a section |
list_architect_sections |
List all indexed sections with page counts |
export_architect_section |
Export a full section to a single Markdown file on disk |
get_scrape_status |
Database stats: page counts, sections, last run, pending/failed URLs |
Resources
Attach these to your conversation context for orientation:
| URI | Description |
|---|---|
sf-architect://guide/usage |
Recommended workflows and tool usage tips |
sf-architect://data/languages |
All supported language codes with display names |
sf-architect://data/sections |
Live section index with current page counts |
Prompts
Pre-built workflow templates:
| Prompt | Arguments | What it does |
|---|---|---|
scrape-docs |
mode: full or incremental |
Presents available languages, asks which to scrape, then runs the appropriate tool |
research-topic |
topic: string |
Searches, summarizes relevant pages, and synthesizes findings with citations |
export-section |
section: string |
Verifies the section exists, shows a summary, then exports to Markdown |
Supported languages
| Code | Language |
|---|---|
en |
English (default) |
de |
German |
fr |
French |
jp |
Japanese |
zh-cn |
Chinese (Simplified) |
zh-tw |
Chinese (Traditional) |
dk |
Danish |
es |
Spanish |
fi |
Finnish |
it |
Italian |
kr |
Korean |
nl |
Dutch |
no |
Norwegian |
pt-br |
Portuguese (Brazil) |
ru |
Russian |
se |
Swedish |
es-mx |
Spanish (Mexico) |
all |
All languages |
Note: Not all languages are available for all sections. The sitemap at scrape time determines what's actually published.
Configuration
The database is stored at ~/.sf-architect-mcp/sf-architect.db by default.
Override with an environment variable:
SF_ARCHITECT_DB_DIR=/custom/path node dist/index.js
Exported markdown files go to ~/.sf-architect-mcp/exports/{section}-{language}.md unless you specify a custom path.
Architecture
src/
├── index.ts # MCP server — tools, resources, prompts
├── scraper.ts # fetch + cheerio scraper, concurrency pool
├── sitemap.ts # Sitemap fetching and URL filtering
├── types.ts # Shared TypeScript types
├── db/
│ ├── database.ts # sql.js SQLite, persistence, schema
│ ├── ingest.ts # Page upsert, chunk sync, scrape run tracking
│ └── queries.ts # Search, read, export, stats
└── utils/
├── chunker.ts # Section-aware text chunking (1500 chars, 200 overlap)
└── url-utils.ts # Language detection from URL path segments
Key design decisions:
- fetch + cheerio — the site is fully server-side rendered, no headless browser needed. ~10x faster and cross-platform with zero native dependencies
- sql.js (WASM SQLite) — in-process, zero native dependencies, serialized to disk after every 10 pages
- Section-aware chunking — detects both Markdown headings and bold-text markers (
**Definition:**) which the site uses instead of semantic HTML headings - LRU cache on search results (500 entries, 5-minute TTL)
- Content hash comparison for incremental scraping — only re-indexes pages whose content has actually changed
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。