Skip to main content
Glama
mcp-research

Pica MCP Server

by mcp-research
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to Pica MCP Server

No user-submitted related servers found.

    Related Servers

    • anyapi-mcp-server

      quiloos39
      A
      license
      Not graded
      quality
      D
      maintenance
      A universal MCP server that connects any REST API to AI assistants via OpenAPI or Postman specifications. It enables dynamic tool creation with GraphQL-style field selection and automatic schema inference for efficient data retrieval.
      2 npm
      6
      -

    • OmniForge MCP

      ankur-gaurav161418
      A
      license
      Not graded
      quality
      A
      maintenance
      An enterprise-grade MCP server that enables AI coding assistants to securely connect with external tools, APIs, databases, and cloud services through a unified interface, offering structured engineering workflows and multi-client support.
      MIT

    • Multi-MCPs

      TaylorChen
      A
      license
      C
      quality
      D
      maintenance
      Aggregates multiple third-party APIs into unified MCP tools, providing out-of-the-box access to 10 popular services including OpenWeather, Google Maps, GitHub, Notion, Spotify, and more. Enables users to interact with weather data, search places, manage repositories, create content, and access various web services through a single MCP server.
      34
      MIT
    • Spica MCP Server by spica-engine

      Spica MCP Serverofficial

      spica-engine
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents to interact with Spica servers, managing databases, serverless functions, storage, authentication, auditing, debugging, and version control.
      6 npm
      ISC
    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 distinct purpose in a clearly defined workflow: listing integrations, fetching platform actions, retrieving action documentation, and executing the action. There is no overlap or ambiguity.

    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, execute_pica_action). The verbs are action-oriented and match the tool's function.

    Tool Count5/5

    With 4 tools, the server is lean but covers the essential steps for discovering and executing actions on third-party platforms. Each tool earns its place; the number is appropriate for the scope.

    Completeness5/5

    The toolset provides a complete workflow: discover available integrations, explore platform actions, get detailed action knowledge, and execute the action. There are no obvious gaps or dead ends for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources