About walt.id Docs
walt.id Docs is a public, read-only remote MCP server for searching and reading official documentation on the walt.id Community and Enterprise Stacks. It helps developers consult stack-specific guidance without calling walt.id APIs or using an API key.
Key features
- 01Search docs by stack
- 02Fetch documentation pages as Markdown
- 03Retrieve LLMs index pages
- 04List public OpenAPI document links
- 05Compare Community and Enterprise Stacks
Use cases
- 01Find setup guidance for a walt.id stack
- 02Read a specific integration documentation page
- 03Check differences between the two product lines
- 04Locate public OpenAPI specifications
MCP support
Exposes documentation search, page retrieval, index and OpenAPI links, and a product-line comparison to MCP clients. It does not call walt.id APIs.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://docs.walt.id/mcpclaude mcp add --transport http id-walt-docs https://docs.walt.id/mcp{"mcpServers":{"id-walt-docs":{"type":"http","url":"https://docs.walt.id/mcp"}}}Open in Cursor{"servers":{"id-walt-docs":{"type":"http","url":"https://docs.walt.id/mcp"}}}Open in VS Code{"mcpServers":{"id-walt-docs":{"type":"http","url":"https://docs.walt.id/mcp"}}}{"mcpServers":{"id-walt-docs":{"serverUrl":"https://docs.walt.id/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEwalt.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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.