Skip to main content
Glama
Avinava

sf-docs-mcp

by Avinava
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to sf-docs-mcp

No user-submitted related servers found.

    Related Servers

    • Unified Salesforce

      TMTrevisan
      A
      license
      A
      quality
      C
      maintenance
      Enables LLMs to scrape, index, and search modern and legacy Salesforce documentation by piercing complex Shadow DOM and iframe structures. It supports hierarchical spidering of entire guides and local RAG capabilities using a SQLite database for offline querying.
      5
      2 npm
      3
      MIT

    • Crawl4AI RAG MCP Server

      adnan0758
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to crawl, index, and retrieve information from technical documentation using semantic search, with optional knowledge graph validation for code hallucination detection.
      MIT

    • Salesforce Object MCP Server

      davep-gh
      F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to explore Salesforce metadata by parsing object and field definitions, reducing hallucination when working with Salesforce repositories.
      7
      -

    • CodeXRay

      NeuralRays
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to query a pre-built semantic knowledge graph of code, reducing token usage and tool calls. Supports 16 tools for code exploration, analysis, and context building.
      5 npm
      7
      MIT

    • mcp-server-salesforce

      tomnagengast
      F
      license
      B
      quality
      D
      maintenance
      Provides AI agents with secure access to Salesforce data and operations, enabling natural language interaction with CRM for sales, marketing, and executive teams.
      6
      5
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target distinct resources (domains, topics, Apex, objects, errors, limits), but sf_search and sf_semantic_search both serve general search and could be confused; sf_apex_lookup also overlaps with sf_search for Apex-specific queries. Overall mostly clear.

    Naming Consistency3/5

    All tools share the 'sf_' prefix, but the action placement is inconsistent: some follow verb_noun (list_domains, read_topic, explain_error), others are noun phrases (apex_lookup, object_reference, limits, semantic_search). This mixed convention reduces predictability.

    Tool Count5/5

    12 tools is well within the ideal 3-15 range for a documentation server, covering various access patterns without being overwhelming.

    Completeness4/5

    The tool set covers discovery (domains, search), reading (topics, lookups), and specialized queries (code examples, errors, limits). A minor gap is the lack of an explicit tool to enumerate all topics within a domain, but graph_query and search mitigate this.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources