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

    • freebuff-mcp

      Praket7
      A
      license
      B
      quality
      A
      maintenance
      Enables MCP clients to safely interact with a locally installed Freebuff Desktop orchestrator, providing verified read access to projects, threads, messages, and project files while keeping credentials local and write operations read-only when unsupported.
      14
      115 npm
      15
      MIT

    • 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.
      1
      MIT

    • ChatGPT Gateway MCP Nyan

      wada-qualia
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agent clients to safely connect to tools and execution resources through MCP with authorization, approvals, audit, chat-context isolation, SSH/Docker access, and long-running command session tracking.
      MIT
    • MCPilot by Farfive

      MCPilotofficial

      Farfive
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables an agent to search approved MCP integrations and expose only the tools a given task needs, signing the user in once via browser-based OAuth and enforcing scopes, effects and budgets in code. It also acts as a single gateway connection so existing hosts can reach many servers with per-tenant isolation and audit events.
      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

    ActivityMaintained
    ResponsivenessNo issues

    Resources