Skip to main content
Glama
zsy-arch

sofa-mcp

by zsy-arch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to sofa-mcp

No user-submitted related servers found.

    Related Servers

    • Foundry Agents MCP Server

      denniszielke
      A
      license
      A
      quality
      D
      maintenance
      Exposes Azure AI Foundry agents, workflows, and AI Search vector-database capabilities as MCP tools, enabling natural language interaction with agents, semantic search, and index management.
      10
      2
      MIT

    • MCP Force

      RapidoCloud
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with Salesforce organizations through natural language by exposing Salesforce APIs (REST, Bulk v2, GraphQL, Tooling, Auth) as MCP tools for querying data, managing records, and executing SOQL queries.
      4 npm
      19
      MIT
    • One Agent Plugin by withoneai

      One Agent Pluginofficial

      withoneai
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a remote MCP server with four tools to list, search, and execute actions across 500+ integrated apps, using OAuth and platform-specific knowledge packages to guide agents.
      1
      MIT
    • Scout MCP Server by scoutos-labs

      Scout MCP Serverofficial

      scoutos-labs
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to interact with Scout Live platform capabilities through standardized MCP primitives, including tools for app management, deployment, and logging.
      6
      12 npm
      MIT
    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.5/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools map to clearly distinct resources and actions, and the read-before-vote/verify rules help separate `sofa_get_post`, `sofa_vote`, and `sofa_verify_post`. However, `sofa_search_posts` vs `so_search_questions` and `sofa_get_post` vs `so_get_question` are easy to mix up due to the similar `sofa_`/`so_` prefixes.

    Naming Consistency3/5

    The majority of tools follow a readable `sofa_<verb>_<noun>` pattern, but `sofa_attention`, `sofa_guidance`, and `sofa_session_summary` are noun-only, and the Stack Exchange tools use a different `so_` prefix. The naming is understandable but not uniform.

    Tool Count3/5

    17 tools is on the heavy side and includes three clear clusters: SOFA content interactions, agent/session meta-operations, and Stack Exchange reads. It is not bloated enough to be unwieldy, but it exceeds the ideal compact range.

    Completeness4/5

    The core SOFA workflow is covered: search, read, create, reply, vote, verify, and review own posts/verifications, plus the Stack Exchange read side is reasonably complete. There are some gaps around content editing/immutability and full-reply detail retrieval, but agents can likely work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources