Skip to main content
Glama
Sign In

EasyJur

by io.github.mcp-dir
OverviewDiscussionsAdmin

Server Details

Wrapper for the official EasyJur API (legal practice management): cases (with parties, claims, finan

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
mcp-dir/easyjur-mcp
GitHub Stars
0
Server Listing
EasyJur
ChatGPT
–
Claude
–

TDQS

C2.8/5.0

Scored across 47 tools

Disambiguation5/5

Each tool targets a distinct resource or sub-resource with clear CRUD actions. The easyjur_ tools are separated by entity (agenda, processo, pessoa, etc.) and by action (create, get, list), while sub-resource tools like easyjur_processo_partes or easyjur_agenda_comentarios have unambiguous scopes. Platform tools (authenticate, connect, marketplace) serve disjoint meta-purposes, so no ambiguity.

Naming Consistency3/5

Most easyjur_ tools follow a consistent verb_noun pattern (create_agenda, get_processo, list_despesas), but several break it with noun_subresource names (easyjur_agenda_comentarios, easyjur_processo_financeiros) and the platform tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) use plain nouns without the prefix. This mixture of conventions makes the set less predictable.

Tool Count2/5

47 tools is well above the threshold for a focused MCP server, even for a comprehensive legal management domain. The inclusion of platform meta-tools inflates the count, and many entities (agenda, processo) have multiple sub-resource readers. This volume risks overwhelming agents and slowing tool selection.

Completeness2/5

The tool surface provides create, get, and list for each entity, but there are no update or delete operations for any entity. Sub-resources (documentos, partes, mensagens, etc.) are read-only. The only workaround mentioned is creating agenda items to record movements, which is a workaround, not a real update. This is a significant gap that will cause dead ends for workflows requiring modification or removal.

Available Tools

47 tools
authenticateA
Idempotent
Inspect

MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header Authorization: Bearer <token> for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "" } after the user pastes, or with no args to get the link.

Inputs: token.

connectA
Read-onlyIdempotent
Inspect

Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

Inputs: no named parameters.

easyjur_agenda_comentariosD
Read-onlyIdempotent
Inspect

Comentários de um item de agenda.

Inputs: id_agenda (required), query.

easyjur_agenda_envolvidosB
Read-onlyIdempotent
Inspect

Envolvidos em um item de agenda.

Bulk support: accepts agenda_ids for batched execution.

Inputs: agenda_id (required), query, agenda_ids.

easyjur_agenda_etapasB
Read-onlyIdempotent
Inspect

Etapas de workflow de um item de agenda.

Bulk support: accepts agenda_ids for batched execution.

Inputs: agenda_id (required), query, agenda_ids.

easyjur_api_statusA
Read-onlyIdempotent
Inspect

Status da API EasyJur do escritório autenticado (identidade + limites).

Inputs: query.

easyjur_create_agendaAInspect

Cria item de agenda. Obrigatórios: tipo, id_advogado. Vincule a um processo (campo processo) para registrar uma movimentação/atualização.

Inputs: tipo (required), id_advogado (required), data, extra, +8 more.

easyjur_create_oportunidadeCInspect

Cria oportunidade. Obrigatórios: nome, status, responsavel, cliente.

Inputs: nome (required), status (required), cliente (required), responsavel (required), +3 more.

easyjur_create_pessoaAInspect

Cria uma pessoa. Obrigatórios: nome, fisica_juridica.

Inputs: nome (required), fisica_juridica (required), cpf, cnpj, +4 more.

easyjur_create_processoAInspect

Cria um processo. Obrigatórios: numero, id_advogado. (A API oficial não tem update — para registrar movimentação use easyjur_create_agenda vinculada ao processo.)

Inputs: numero (required), id_advogado (required), extra, id_cliente, +4 more.

easyjur_get_agendaA
Read-onlyIdempotent
Inspect

Busca um item de agenda por ID.

Bulk support: accepts agenda_ids for batched execution.

Inputs: agenda_id (required), query, agenda_ids.

easyjur_get_despesaA
Read-onlyIdempotent
Inspect

Busca uma despesa por ID.

Bulk support: accepts despesa_ids for batched execution.

Inputs: despesa_id (required), query, despesa_ids.

easyjur_get_grupoB
Read-onlyIdempotent
Inspect

Busca um grupo por ID.

Bulk support: accepts grupo_ids for batched execution.

Inputs: grupo_id (required), query, grupo_ids.

easyjur_get_oportunidadeA
Read-onlyIdempotent
Inspect

Busca uma oportunidade por ID.

Bulk support: accepts oportunidade_ids for batched execution.

Inputs: oportunidade_id (required), query, oportunidade_ids.

easyjur_get_pessoaA
Read-onlyIdempotent
Inspect

Busca uma pessoa por ID.

Bulk support: accepts pessoa_ids for batched execution.

Inputs: pessoa_id (required), query, pessoa_ids.

easyjur_get_processoA
Read-onlyIdempotent
Inspect

Busca um processo por ID (dados completos).

Bulk support: accepts processo_ids for batched execution.

Inputs: processo_id (required), query, processo_ids.

easyjur_get_receitaA
Read-onlyIdempotent
Inspect

Busca uma receita por ID.

Bulk support: accepts receita_ids for batched execution.

Inputs: receita_id (required), query, receita_ids.

easyjur_get_timesheetA
Read-onlyIdempotent
Inspect

Detalha um lançamento de timesheet.

Bulk support: accepts ids for batched execution.

Inputs: id (required), ids, query.

easyjur_get_tokenA
Read-onlyIdempotent
Inspect

Consulta um token de API por ID.

Bulk support: accepts token_ids for batched execution.

Inputs: token_id (required), query, token_ids.

easyjur_get_userA
Read-onlyIdempotent
Inspect

Busca um usuário por ID.

Bulk support: accepts user_ids for batched execution.

Inputs: user_id (required), query, user_ids.

easyjur_list_agendaB
Read-onlyIdempotent
Inspect

Lista itens de agenda (prazos, compromissos, tarefas).

Inputs: page, query, page_size.

easyjur_list_agenda_grupoC
Read-onlyIdempotent
Inspect

Lista agenda de um grupo.

Bulk support: accepts grupo_ids for batched execution.

Inputs: grupo_id (required), page, query, grupo_ids, +1 more.

easyjur_list_despesasC
Read-onlyIdempotent
Inspect

Lista despesas.

Inputs: page, query, page_size.

easyjur_list_despesas_grupoC
Read-onlyIdempotent
Inspect

Lista despesas de um grupo.

Bulk support: accepts grupo_ids for batched execution.

Inputs: grupo_id (required), page, query, grupo_ids, +1 more.

easyjur_list_gruposC
Read-onlyIdempotent
Inspect

Lista grupos (pastas/áreas).

Inputs: page, query, page_size.

easyjur_list_oportunidadesB
Read-onlyIdempotent
Inspect

Lista oportunidades (CRM/pré-venda).

Inputs: page, query, page_size.

easyjur_list_oportunidades_grupoA
Read-onlyIdempotent
Inspect

Lista oportunidades de um grupo.

Bulk support: accepts grupo_ids for batched execution.

Inputs: grupo_id (required), page, query, grupo_ids, +1 more.

easyjur_list_pessoasC
Read-onlyIdempotent
Inspect

Lista pessoas (clientes, contrários, terceiros).

Inputs: cpf, cnpj, nome, page, +2 more.

easyjur_list_pessoas_grupoA
Read-onlyIdempotent
Inspect

Lista pessoas de um grupo.

Bulk support: accepts grupo_ids for batched execution.

Inputs: grupo_id (required), page, query, grupo_ids, +1 more.

easyjur_list_processosA
Read-onlyIdempotent
Inspect

Lista/busca processos. Filtros úteis: numero, nome_parte, cpf, cnpj, advogado_nome, status, comarca, uf, data_inicio, data_fim, movimentacao, dias_movimentacao. Demais filtros via query.

Inputs: uf, cpf, cnpj, page, +11 more.

easyjur_list_processos_grupoB
Read-onlyIdempotent
Inspect

Lista processos de um grupo.

Bulk support: accepts grupo_ids for batched execution.

Inputs: grupo_id (required), page, query, grupo_ids, +1 more.

easyjur_list_receitasC
Read-onlyIdempotent
Inspect

Lista receitas.

Inputs: page, query, page_size.

easyjur_list_receitas_grupoA
Read-onlyIdempotent
Inspect

Lista receitas de um grupo.

Bulk support: accepts grupo_ids for batched execution.

Inputs: grupo_id (required), page, query, grupo_ids, +1 more.

easyjur_list_timesheetC
Read-onlyIdempotent
Inspect

Lista lançamentos de timesheet.

Inputs: page, query, page_size.

easyjur_list_tokensB
Read-onlyIdempotent
Inspect

Lista os tokens de API da empresa.

Inputs: page, query, page_size.

easyjur_list_tribunaisC
Read-onlyIdempotent
Inspect

Lista tribunais/órgãos disponíveis.

Inputs: query.

easyjur_list_usersC
Read-onlyIdempotent
Inspect

Lista usuários do escritório.

Inputs: page, query, page_size.

easyjur_processo_documentosC
Read-onlyIdempotent
Inspect

Documentos de um processo.

Bulk support: accepts processo_ids for batched execution.

Inputs: processo_id (required), query, processo_ids.

easyjur_processo_financeirosC
Read-onlyIdempotent
Inspect

Lançamentos financeiros de um processo.

Bulk support: accepts processo_ids for batched execution.

Inputs: processo_id (required), query, processo_ids.

easyjur_processo_mensagensC
Read-onlyIdempotent
Inspect

Mensagens/andamentos de um processo.

Bulk support: accepts processo_ids for batched execution.

Inputs: processo_id (required), query, processo_ids.

easyjur_processo_partesC
Read-onlyIdempotent
Inspect

Partes de um processo.

Bulk support: accepts processo_ids for batched execution.

Inputs: processo_id (required), query, processo_ids.

easyjur_processo_pedidosC
Read-onlyIdempotent
Inspect

Pedidos de um processo.

Bulk support: accepts processo_ids for batched execution.

Inputs: processo_id (required), query, processo_ids.

easyjur_processo_vinculadosB
Read-onlyIdempotent
Inspect

Processos vinculados a um processo.

Bulk support: accepts processo_ids for batched execution.

Inputs: processo_id (required), query, processo_ids.

marketplaceAInspect

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/ link that opens without login.

Inputs: limit, query, action, mcp_id, +19 more.

report_bugA
Idempotent
Inspect

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

Inputs: message (required), context, conversation.

show_versionA
Read-onlyIdempotent
Inspect

Show the current MCP platform and adapter versions.

Inputs: no named parameters.

toolkit_infoA
Read-onlyIdempotent
Inspect

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • DataJud (CNJ)

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying public Brazilian court proceedings metadata and movements via the CNJ/DataJud API, covering multiple courts.
      4
      MIT

    • cnj-processual

      ACARVALHOSP
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Brazilian judicial case data through CNJ public APIs: fetching case metadata and movements via DataJud, searching publications and intimations from the national electronic justice gazette (DJEN) by case number or OAB, and downloading publication certificates as PDFs.
      -

    • MCP PJe Server

      KlrCe
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables interaction with Brazil's Electronic Judicial Process (PJe) system to search for legal processes, view case details, and download court documents. Supports secure JWT authentication and process lookup by CPF/CNPJ or party name.
      -

    • juris-br-mcp

      andrecccruz
      A
      license
      A
      quality
      C
      maintenance
      Enables natural-language queries of Brazilian court cases through the public DataJud and DJEN APIs, retrieving case details, movements, publications, and parties across 92 tribunals, and calculating procedural deadlines in business days. It also offers optional Domicílio Judicial Eletrônico tools for listing and acknowledging intimations.
      11
      MIT
    Try in Browser
    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

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources