Back
mcp-server-appwrite 0.4 fails on startup validation for tables_db with DatabaseList parsing errors
I’m trying to use mcp-server-appwrite against Appwrite Cloud and the server authenticates successfully, but fails during startup validation when probing tables_db.
Versions
mcp-server-appwrite:0.4appwritePython SDK:17.0.0
Environment
- Endpoint:
https://fra.cloud.appwrite.io/v1 - Running via:
uvx mcp-server-appwrite
What happens
The MCP server starts, loads config, registers services, and begins startup validation. It then fails on tables_db with a parsing error for DatabaseList.
Error
TypeScript
RuntimeError: Appwrite startup validation failed during the minimal startup probe.
- tables_db: Appwrite request failed: Unable to parse response into DatabaseList: 18 validation errors for DatabaseList
databases.0.policies.0.status
Input should be 'available', 'processing', 'deleting', 'stuck' or 'failed'
[input_value='']
databases.0.archives.0.documentSecurity
Input should be a valid boolean, unable to interpret input
[input_value='']
... repeated for multiple archives/databases ...
Notes
- Authentication works.
- Endpoint, project ID, and API key are valid.
- The crash happens only when startup validation probes
tables_db. - It looks like some response fields are returned as empty strings (
"") where the Python model expects enum/boolean values.
Could this be a schema mismatch between the current Cloud response and the MCP/SDK models?
TL;DR
The developer is running into a startup validation error while using `mcp-server-appwrite` against Appwrite Cloud. The issue occurs specifically with the `tables_db` validation. The error indicates a problem with parsing the response into `DatabaseList`, with mismatched fields like empty strings instead of expected enum/boolean values. This suggests a potential schema mismatch between the Cloud response and the MCP/SDK models.