
docs
id.walt/docs
Search and read official walt.id documentation for the Community Stack and the Enterprise Stack.
Documentation
walt.id Docs MCP
Search and read the official walt.id documentation from an MCP client. The server is remote, public, and read-only. It does not call walt.id APIs and it does not need an API key.
Endpoint: https://docs.walt.id/mcp
Documentation: Use the docs with AI
The server is hosted with the docs site. This repository is the public description used by the GitHub MCP Registry and Copilot. It does not contain the server implementation.
What it can do
The tools cover Concepts, the open-source Community Stack, and the commercial Enterprise Stack.
| Tool | What it returns |
|---|---|
search_waltid_docs | Matching pages. Optional stack: concepts, community, or enterprise. Community and Enterprise searches also include stack-agnostic concepts. |
get_waltid_doc_page | Raw markdown for one docs path, such as /community-stack/issuer2/getting-started. |
get_waltid_llms_index | The llms.txt page index, not the full text of every page. |
list_waltid_openapi_specs | Links to the public OpenAPI documents. The server does not call those APIs. |
get_community_vs_enterprise | The comparison of the two product lines. |
Resources:
https://docs.walt.id/llms.txthttps://docs.walt.id/llms-community-stack.txthttps://docs.walt.id/llms-enterprise-stack.txt
Prompt: pick-community-or-enterprise. Use it before writing integration code. The two stacks use different base URLs, paths, and auth.
Configure a client
No authentication headers are required.
Cursor
{
"mcpServers": {
"walt.id Docs": {
"url": "https://docs.walt.id/mcp"
}
}
}
VS Code and GitHub Copilot
{
"servers": {
"walt.id Docs": {
"type": "http",
"url": "https://docs.walt.id/mcp"
}
}
}
Claude
Add a custom connector with the remote URL https://docs.walt.id/mcp.
How to use it
- Ask the client to run
pick-community-or-enterprise, or read Community vs Enterprise. - Search with
search_waltid_docsandstackset tocommunityorenterprise. - Fetch the page you need with
get_waltid_doc_page.
Keep base URLs and API paths inside the stack you chose.
No installation packages available.