Comprot: Processo vs Moxie Docs MCP
A side-by-side look at the Comprot: Processo and Moxie Docs MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Comprot: Processo for legal work over a hosted endpoint; choose Moxie Docs MCP for knowledge & memory. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Comprot: Processo when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
comprot_processo_consultar, show_version, report_bug.
Choose Moxie Docs MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- Its auth model fits you: OAuth 2.0.
- You want tools like
moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Knowledge & Memory |
| Quality signal | 39/100 · Fair | 76/100 · Great |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 2 |
| Directory activity | 1 views 0 installs 0 upvotes | 40 views 25 installs 4 upvotes |
| Tools | 7 | 12 |
| Full listing | View Comprot: Processo | View Moxie Docs MCP |
Tools & capabilities
Comprot: Processo tools 7
comprot_processo_consultarComprot: Processo, consulta em fonte oficial. Hospedado pela plataforma, sem credenciais da plataforma, pague por consulta com crédito pré-pago. Consulta informação de fontes e órgãos oficiais brasileiros (a mesma disponível ao cidadão), não é dado sigiloso. O cliente é o controlador dos dados e responde pela finalidade legítima (LGPD).show_versionShow the current MCP platform and adapter versions.report_bugReport a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.connectReturns 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.toolkit_infoReturns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.marketplaceThe 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/<slug> link that opens without login.authenticateMCP.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: "<jwt>" } after the user pastes, or with no args to get the link.
Moxie Docs MCP tools 12
moxie.get_ai_contextCompact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.moxie.get_doc_impactGiven the paths you're about to change (and any you're deleting), returns the conventions, gaps, and existing docs whose evidence overlaps them - and flags net-new/undocumented surfaces.moxie.get_api_contextGiven paths you're about to touch, returns structured context for any API endpoints they map to: method, path, schema, and known consumers/features.moxie.review_changeSelf-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docs, undocumented surface, and broken references.moxie.get_conventionsDiscovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.moxie.search_docsSemantic + keyword search over generated docs, conventions, gaps, and AI context.moxie.get_doc_gapsUnresolved documentation gaps with severity and the paths they concern.moxie.get_documentation_opportunitiesRecommended doc work: missing docs, drift repairs, and PR templates.moxie.get_documentation_patternsHow the repository organizes and maintains its docs (where new docs belong).moxie.list_docsPaginated, section-grouped table of contents of every generated doc.moxie.propose_doc_updateAdd or update a doc as part of your current change; returns the target path + Markdown to write into your branch.moxie.propose_doc_removalRemove a Moxie Docs-tracked doc your change makes obsolete; returns the path to delete in your branch.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Comprot: Processo
{
"mcpServers": {
"comprot-processo": {
"url": "https://api.mcp.ai/p_comprot_processo"
}
}
}
Moxie Docs MCP
No confirmed install command for Moxie Docs MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Comprot: Processo is categorized under Legal and uses a remote HTTP/SSE transport. Moxie Docs MCP belongs to Knowledge & Memory and uses an install path we have not confirmed yet. Pick Comprot: Processo for legal work and Moxie Docs MCP for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Moxie Docs MCP has no confirmed install command yet — follow its own setup instructions.
Comprot: Processo has no declared pricing — check the project's own site. Moxie Docs MCP is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add comprot-processo and moxie-docs-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Comprot: Processo has a quality signal of 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Moxie Docs MCP has 76/100 (Great) with 40 views, 25 installs and 2 GitHub stars.