Skip to main content
Glama
withoneai

pica

by withoneai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to pica

No user-submitted related servers found.

    Related Servers

    • Ethora MCP Server

      dappros
      A
      license
      A
      quality
      A
      maintenance
      Enables integration with the Ethora platform through user authentication, registration, and application management operations. Supports creating, updating, deleting, and listing applications within the Ethora service.
      89
      187 npm
      6
      MIT

    • Pega DX MCP Server

      marco-looy
      A
      license
      B
      quality
      C
      maintenance
      Transforms complex Pega Platform interactions into intuitive, conversational experiences by exposing Pega DX APIs through the standardized Model Context Protocol, enabling AI applications to interact with Pega through natural language.
      67
      15 npm
      22
      Apache 2.0

    • GitHub-Jira MCP Server

      KronosWasTaken
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables secure integration between GitHub and Jira with permission controls, allowing users to manage repositories, create issues and pull requests, and handle Jira project workflows through natural language. Supports OAuth authentication and comprehensive security enforcement for both platforms.
      MIT

    • Figma MCP Server

      bbalakriz
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables integration with Figma through the Model Context Protocol, allowing users to interact with Figma designs and files using their Personal Access Token. Provides containerized deployment options and Server-Sent Events endpoint for real-time communication.
      1,225 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

    A4.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose in the Pica workflow: list_pica_integrations discovers available platforms, get_pica_platform_actions shows actions for a specific platform, get_pica_action_knowledge provides documentation for an action, and execute_pica_action performs the actual operation. There is no overlap or ambiguity between these functions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case: list_pica_integrations, get_pica_platform_actions, get_pica_action_knowledge, and execute_pica_action. The naming is predictable and readable throughout.

    Tool Count5/5

    With 4 tools, this server is well-scoped for its purpose of managing integrations and actions on third-party platforms. Each tool serves a specific role in the workflow, and the count is neither too thin nor excessive for the domain.

    Completeness5/5

    The tool set provides complete coverage for the Pica domain: it allows listing integrations, discovering platform actions, retrieving action knowledge, and executing actions. This covers the full lifecycle from discovery to implementation, with no obvious gaps for the intended workflow.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources