Back to Directory/Documentation

io.github.ACTA-Team/docs-mcp

Read-only MCP server for the official ACTA verifiable credentials documentation.

DocumentationTypeScriptv0.1.3

ACTA Docs

The documentation site for ACTA: verifiable credentials and decentralized identity on Stellar. It is the single reference for everything an issuer, holder, verifier, or integrator needs to build on ACTA, from the REST API and the SDK to the Soroban contracts and the dApp.

About ACTA

ACTA issues W3C-style verifiable credentials anchored on Stellar and Soroban:

  • did:stellar identities resolved from an on-chain registry, decoupled from any single wallet (key rotation, portability).
  • Single-tenant credential vaults, one Soroban contract per owner, deployed by a vc-vault-factory. Status and revocation are publicly verifiable on Stellar; issuance fees settle on-chain in USDC.
  • A prepare/submit flow so the user's Stellar wallet signs every transaction; the services never hold keys.

What this site documents

Bilingual (English / Spanish) content for:

  • Welcome: introduction, architecture, getting started.
  • API Reference: vault, credential, contract-info, sponsored-vault, and health endpoints (prepare/submit XDR).
  • SDK (@acta-team/credentials): useVault, useCredential, useVaultRead, sponsored vault.
  • Contracts: vc-vault-factory, single-tenant vc-vault, did-stellar-registry, and contract errors.
  • dApp: features and usage of the web app.
  • MCP: the docs MCP server for AI assistants.

Tech stack

  • Next.js (App Router), React, TypeScript, Tailwind CSS.
  • Content is authored as typed DocPage modules (not Markdown files), which keeps it type-checked and lets the build generate a machine-readable index.
  • @acta-team/docs-mcp (in packages/docs-mcp): an MCP server that exposes the docs to AI assistants, built from a generated docs-data.json.

Quick start

npm install
npm run dev

The site runs at http://localhost:3000/.

Scripts

ScriptWhat it does
npm run devStart the dev server
npm run buildGenerate the docs index and build the site
npm run startRun the production server
npm run lintRun ESLint
npm run formatFormat with Prettier
npm run mcp:generate-docsRegenerate the MCP docs-data.json from content

Content structure

  • src/content/docs/modules/<module>/<lang>/<page>.ts - one DocPage per page (slug, title, section, tocItems, content). <lang> is en or es.
  • src/content/docs/navigation/{en,es}.ts - sidebar navigation per language.
  • src/content/docs/locales/ - UI strings.
  • packages/docs-mcp/ - the MCP server and the generated docs-data.json.

After editing content, run npm run mcp:generate-docs so the search index and MCP data stay in sync.

License

Dual-licensed, split by what the thing is:

WhatLicense
Software — the Next.js app, @acta-team/docs-mcp, scripts, configMIT
Documentation content — the prose, guides and reference pagesCC BY 4.0
ACTA name, logo and brand assets under public/Neither. Trademarks of ACTA, all rights reserved.

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y @acta-team/docs-mcp

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "io-github-acta-team-docs-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@acta-team/docs-mcp"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

@acta-team/docs-mcpnpm

Compatible MCP Clients

io.github.ACTA-Team/docs-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More