mcp-server-mcdev
Related Servers
Alternatives to mcp-server-mcdev
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Salesforce developers to create code and configuration using local documentation, with optional semantic search.9 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.8 npm1MIT
- AlicenseAqualityBmaintenanceEnables developers to search official documentation offline, explain configuration files, look up CLI commands and REST/GraphQL APIs, and scaffold modules, plugins, observers, controllers, and database tables without network access or credentials.10151 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to search, install, read, and navigate DevDocs documentation offline via MCP, with token-efficient search/read/toc tools and local caching.627 npm1MIT
- AlicenseNot gradedqualityCmaintenanceProvides AI assistants offline fuzzy search, precise section retrieval, and section listing over bundled mobile-development documentation, enabling natural-language lookups of components, hooks, guides, and best practices.MIT
- AlicenseAqualityDmaintenanceScrapes, indexes, and serves Salesforce Architect documentation locally, enabling fast offline RAG-powered search and retrieval for AI coding assistants.9MIT
TDQS
Scored across 20 tools
Several tools read/diagnose the same .mcdevrc.json resource: read_mcdev_project_config, inspect_mcdev_project, diagnose_mcdev_project_config, and preview_mcdev_project_config all overlap heavily, and preview_mcdev_project_command vs diagnose_mcdev_project_config are easily confused. An agent will struggle to pick the right config-inspection tool, and warnings inside descriptions (e.g. 'use the visual MCDev Pipeline Builder FIRST') signal boundary problems rather than resolve them.
Two competing conventions coexist: a mcdev_ prefix pattern (mcdev_get_command, mcdev_list_commands, mcdev_search_docs) and a verb-first pattern (diagnose_mcdev_project_config, read_mcdev_project_config, inspect_mcdev_git_policy). The verb ordering is inconsistent across the set, so a predictable grouping is hard to infer even though everything is snake_case.
20 tools is in the heavy range for a server whose core purpose is mcdev project inspection and command execution. Many are narrow read-only variants (git_policy vs git_range, artifact inventory vs resolve vs read), which inflates the surface more than the domain complexity strictly requires.
run_mcdev_command gives a broad escape hatch for native operations, and doc/command discovery is reasonably covered. However the surface is read/diagnose-heavy with no clear write/apply path for config or artifacts (only previews), and many operations are explicitly declared out of scope, leaving notable gaps for a complete authoring lifecycle.