Skip to main content
Glama
bbpropulse

MCP PJe Pernambuco

by bbpropulse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP PJe Pernambuco

No user-submitted related servers found.

    Related Servers

    • browser-ai-rag

      ekiyo55
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables browser-based AI services to connect through remote MCP for internal document search, email checking and replies, timecard, sales/project, schedule/task, and operations tasks. It supports multiple AI clients via compatible remote MCP endpoints.
      Apache 2.0

    • keyhall

      luizgustavosaraiva
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to access remote and local MCP servers plus HTTP APIs through a single MCP endpoint, with per-consumer scoped tokens, tool-level permissions, and encrypted secret management.
      5
      PolyForm Noncommercial 1.0.0

    • mcp-gateway

      R0Wi
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables clients to access multiple backend MCP servers through a single endpoint, with OAuth 2.1 authorization, namespaced tools, and secure credential management.
      2
      MIT
    • PocketShell MCP by PocketShell-io

      PocketShell MCPofficial

      PocketShell-io
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables remote MCP clients to perform host, file, process, and DataOps operations through a persistent gateway without locally storing CLI logins, SSH keys, or host pins, using standard Streamable HTTP and OAuth.
      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

    C2.9/5.0

    Scored across 35 tools

    Disambiguation4/5

    Tool purposes are mostly clear because descriptions specify source (SICAJUD, DataJud, PJe, PJeDocs) and workflow phase (prepare, solicit, open, encerrar). A few pairs require close reading—listar_ambientes versus listar_tribunais_suportados, consultar_processo_publico versus consultar_metadados_processo, and the staged PJeDocs tools—so selection is not entirely automatic.

    Naming Consistency4/5

    The set overwhelmingly follows the Portuguese verb_noun imperative pattern, such as listar, consultar, baixar, and encerrar, and groups tools by subdomain. The two status_* names break the imperative pattern, and a few compound names are overloaded, but there is no mixed casing or random verbing.

    Tool Count2/5

    35 tools is a heavy surface for an MCP server, even for the broad PJe domain. The many prepare/request/list/download staging tools inflate the count and force an agent to navigate a large state machine when selecting the right operation.

    Completeness4/5

    Core workflows—environment diagnostics, public consultation, autos access, document extraction/download, PJeDocs, and CAP1G chat—are represented without obvious dead ends. Minor gaps include no explicit session logout/cleanup and no standalone document enumeration tool beyond the autos inspection and reading tools.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources