mcp-server-mcdev
Related Servers
Alternatives to mcp-server-mcdev
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Salesforce developers to create code and configuration using local documentation, with optional semantic search.4 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search and read offline documentation from synced libraries via MCP tools, providing hybrid keyword and semantic search without network calls.4 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables an AI agent to query a fully local, offline index of OpenKore's official wiki and Perl source code, answering configuration questions, retrieving symbol bodies and file:line references, and revealing options that exist in code but are not documented. Exposes nine MCP tools, including hybrid documentation search, source lookup, and gap analysis between the wiki and the codebase.-
- AlicenseAqualityCmaintenanceEnables AI agents to search, install, read, and navigate DevDocs documentation offline via MCP, with token-efficient search/read/toc tools and local caching.69 npmMIT
- AlicenseAqualityDmaintenanceScrapes, indexes, and serves Salesforce Architect documentation locally, enabling fast offline RAG-powered search and retrieval for AI coding assistants.9MIT
- FlicenseNot gradedqualityCmaintenanceProvides live-org context for AI assistants with tools to search skills, agents, templates, decision trees, and query Salesforce metadata (Apex, LWC, objects, fields, etc.) via MCP.23-
TDQS
Scored across 5 tools
Each tool has a fairly distinct purpose: docs search, config-key explanation, component checklist, metadata-type listing, and config reading. The only mild overlap is between mcdev_search_docs and mcdev_explain_config_key, since both address configuration concepts, but the search-vs-explain distinction is reasonably clear.
Four tools use a consistent mcdev_ prefix (mcdev_search_docs, mcdev_explain_config_key, etc.), but read_mcdev_project_config breaks the pattern by placing the prefix mid-name and using a different verb style. The mixed convention is still readable but not uniform.
Five tools is well-scoped for a documentation and configuration helper server. Each tool covers a distinct facet of assisting with mcdev/SFMC development without redundancy.
The surface covers the key helper workflows: searching docs, explaining config, authoring checklists, listing metadata types, and reading project config. Minor gaps exist (e.g. no config validation or write/migration helper), but the read-only assistance scope is largely covered.