Base de Conhecimento

Reviewed Jan 1, 2000.

• tools: 13 tools scanned
• metadata: scanned

No findings.

Tools (13)

• kb_search

  Busca semântica na base de conhecimento. Devolve os trechos (chunks) mais relevantes pra usar como contexto, com nome do arquivo de origem e score. Retrieval-only: você sintetiza a resposta a partir dos trechos.

• kb_list_documents

  Lista os documentos da base (id, nome, status, tamanho, nº de chunks).

• kb_get_document

  Metadados + status de um documento específico (sem o texto cru). Bulk support: accepts document_ids for batched execution.

• kb_add_text

  Adiciona um texto colado à base (vira um documento indexado e buscável). Útil pra notas, trechos, anotações.

• kb_ingest_url

  Baixa um arquivo de uma URL (.md/.txt/.docx) e o indexa na base. Bom pra ingerir um documento remoto sem upload manual.

• kb_remove_document

  Remove um ou mais documentos da base (apaga o original, os chunks e o índice). Aceita uma lista de ids.

• kb_list_accounts

  Lista as bases de conhecimento conectadas neste install. Retorna cada base com id, rótulo e um flag is_default (true quando só há uma — não precisa passar `account` nas outras tools). Com várias bases, toda kb_* aceita um `account` opcional (id ou rótulo).

• show_version

  Show the current MCP platform and adapter versions.

• report_bug

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

• connect

  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.

• toolkit_info

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

• marketplace

  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;

• authenticate

  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: "<jwt>" } after the user pastes, or with no args to get the link.