
Docs Mcp
io.github.ACTA-TeamPublished by GitHub account ACTA-Teamv0.1.3Updated Oct 24, 2026
Read-only MCP server for the official ACTA verifiable credentials documentation.
Overview
Read-only MCP server that lets an assistant list, read and search the official ACTA verifiable credentials documentation in English and Spanish.
- What you can do
- List available ACTA documentation pages
- Read a specific page by slug and locale
- Search content inside the ACTA documentation
- Expose documentation pages as resources addressed by locale and slug
- When to use it
- Use it when you want an assistant to answer questions about ACTA — what it is, how credential issuance and verification work, or how to integrate with its API or SDK — from public, official documentation rather than general training data. It is meant for documentation and technical support, not for performing ACTA operations.
- Requirements
- Runs locally over stdio, typically started with npx from the npm package @acta-team/docs-mcp, so Node.js is needed. No authentication or API key. Network access to the ACTA documentation endpoint at startup; if that fetch fails, the copy bundled in the package is used. Optional variables: ACTA_DOCS_MCP_OFFLINE=1 to skip the remote fetch, and ACTA_DOCS_MCP_DATA_URL to point at a different docs JSON source.
Installation
In SourceWeft
- Open Docs Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
ACTA Docs MCP
ACTA Docs MCP is a read-only Model Context Protocol (MCP) server. MCP-compatible clients (for example Claude, Cursor, or other assistants that support MCP) can query the official ACTA documentation through it.
When to use it: whenever you want an assistant to answer questions about ACTA using public, official, and up-to-date documentation - not guesses from general training data alone.
What it is
This MCP server:
- Does not perform actions inside ACTA.
- Does not issue credentials.
- Does not sign transactions.
- Does not access wallets.
- Does not query private data.
- Does not modify smart contracts.
- Only provides read access to public ACTA documentation.
Quick installation
Run the server directly with npx:
Most users should use this command without changes.
MCP client configuration
Use this configuration in an MCP-compatible client:
After saving the configuration, restart or reload your MCP client.
Documentation updates
When it starts, the server loads the latest documentation from:
- If ACTA documentation changes, users do not need to update the npm package. Restarting or reloading the MCP client is enough for the server process to load the updated documentation.
- New npm versions are only needed when the MCP server code changes.
- If the remote endpoint fails, the server uses the documentation copy bundled in the npm package.
Advanced configuration
Use ACTA_DOCS_MCP_DATA_URL only if you completely trust the configured source. The AI client will use that content as context to answer questions about ACTA.
Available tools
Available resources
Documentation pages are exposed using this URI format:
Currently supported locales:
enes
When to use this MCP
Use this MCP to ask about:
- What ACTA is.
- How credential issuance and verification work.
- How to integrate with the ACTA API or SDK.
- How the documented ACTA architecture works.
- Which endpoints, flows, or concepts are explained in the official documentation.
This MCP is designed for documentation and technical support. It does not replace a direct integration with the ACTA API.
ACTA Docs MCP (Español)
ACTA Docs MCP es un servidor Model Context Protocol (MCP) de solo lectura. Los clientes compatibles con MCP (por ejemplo Claude, Cursor u otros asistentes con soporte MCP) pueden consultar la documentación oficial de ACTA a través de él.
Cuándo usarlo: cuando quieras que un asistente responda sobre ACTA apoyándose en documentación pública, oficial y actualizada, y no solo en conocimiento genérico del modelo.
Qué es
Este servidor MCP:
- No realiza acciones dentro de ACTA.
- No emite credenciales.
- No firma transacciones.
- No accede a wallets.
- No consulta datos privados.
- No modifica smart contracts.
- Solo proporciona acceso de lectura a documentación pública de ACTA.
Instalación rápida
Ejecuta el servidor directamente con npx:
La mayoría de usuarios debería usar este comando sin cambios.
Configuración del cliente MCP
Usa esta configuración en un cliente compatible con MCP:
Después de guardar la configuración, reinicia o recarga tu cliente MCP.
Actualizaciones de documentación
Al iniciar, el servidor carga la documentación más reciente desde:
- Si cambia la documentación de ACTA, normalmente no hace falta actualizar el paquete npm. Basta con reiniciar o recargar el cliente MCP para que el proceso del servidor cargue la documentación actualizada.
- Las nuevas versiones npm solo son necesarias cuando cambia el código del servidor MCP.
- Si el endpoint remoto falla, el servidor usa la copia de documentación incluida en el paquete npm.
Configuración avanzada
Usa ACTA_DOCS_MCP_DATA_URL solo si confías completamente en la fuente configurada. El cliente de IA usará ese contenido como contexto para responder preguntas sobre ACTA.
Herramientas disponibles
Recursos disponibles
Las páginas de documentación se exponen usando este formato de URI:
Los idiomas soportados actualmente son:
enes
Cuándo usar este MCP
Usa este MCP para preguntar sobre:
- Qué es ACTA.
- Cómo funciona la emisión y verificación de credenciales.
- Cómo integrarse con la API o SDK de ACTA.
- Cómo funciona la arquitectura documentada de ACTA.
- Qué endpoints, flujos o conceptos están explicados en la documentación oficial.
Este MCP está diseñado para documentación y soporte técnico. No reemplaza una integración directa con la API de ACTA.
Source: packages/docs-mcp/README.md at commit 1cd9302
Tools
0Version history
1- v0.1.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts