Zed Document Integrity Validator check_document
How to: Zed Document Integrity Validator check_document
Add Document Integrity Validator to Zed
-
01
Open ~/.config/zed/settings.json and merge this in. Keep any servers already there.
{
"context_servers": {
"document-integrity-validator-mcp": {
"url": "https://document-integrity-validator-mcp-production.up.railway.app/mcp"
}
}
}-
02
Save the file and restart Zed.
-
03
Ask for something check_document does. Zed lists the server's tools on connect and calls check_document itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Document Integrity Validator's identifier in your config matches the one above exactly.
Merge this into your existing settings object — do not replace the file. Zed docs
Set these first
Document Integrity Validator will not start until these are set, so check_document never becomes available.
-
ANTHROPIC_API_KEY
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.