MCP server with Claude Code Bug
Session ID: 75347bd2-0f71-4da4-bde3-b5490660e4a5
Log file: ~/.claude/projects/-Users-angelaradcliffe/75347bd2-0f71-4da4-bde3-b5490660e4a5.jsonl
The error: Every call to mcp__chipp__create_app failed with:
INTERNAL_ERROR: Invalid prisma.application.create() invocation:
The column botProtectionEnabled does not exist in the current database.
This was a server-side Chipp API bug — their code references a botProtectionEnabled database column that hasn't been added via migration yet. It failed consistently across multiple retries and
different workspaces, confirming it was a platform-wide issue.
The recommendation at the time was to create the app through the Chipp web UI instead, then use the API for setting the system prompt, uploading knowledge base files, and configuring the model.
You can also resume that conversation directly with:
claude --resume 75347bd2-0f71-4da4-bde3-b5490660e4a5
Would you like to try creating the app again now to see if Chipp has fixed the issue?
Log in to comment and vote
Comments1
Angela Radcliffe
Feb 12
and now this one is fixed… but got a new one
⎿ Error: {"error":{"code":"INTERNAL_ERROR","message":"The incoming JSON object does not contain a client_email field"}}
⏺ That's a Chipp server-side configuration error (cloud storage auth issue). Let me try the URL-based approach instead, or try the upload again.
⏺ The document upload hit a server-side cloud storage auth error (client_email missing — a GCP service account config issue on Chipp's side). This is separate from the earlier bug they fixed.
Unfortunately the URL-based upload won't work for local files either. Let me retry the document upload once more in case it was transient.
⏺ chipp - add_document_source (MCP)(appId: 10039015, files: [{"fileName":"KB_01_NEMSQA_Stroke01_Measure_Spec.md","content":"IyBORU1TUUEgU3Ryb2tlLTAxOiBTdXNwZWN0ZWQgU3Ryb2tlIFJlY2VpdmluZyBQcmVob3NwaXRhbC
BTdHJva2UgQXNzZXNzbWVudAo="}])
⎿ Error: {"error":{"code":"INTERNAL_ERROR","message":"The incoming JSON object does not contain a client_email field"}}
⏺ Same error — it's a persistent Chipp server-side issue with their cloud storage (GCP) credentials, not our input. Here's where things stand:
Completed:
- App created: EMS Stroke QI Prototype (ID: 10039015)
- System prompt set: Full T-Bow QI assistant prompt with all 7 stroke metrics, 4 AHA measures, evaluation logic, severity classifications, and communication guidelines
- Model: GPT_4_1 (default)
Blocked by Chipp:
- Knowledge base file uploads are failing with a GCP service account configuration error (client_email missing). This is a Chipp infrastructure issue.
Your 5 KB files are still on disk at /Users/angelaradcliffe/Downloads/files-4/ and ready to upload once Chipp fixes this. You could also try uploading them manually through the Chipp web dashboard in
the meantime.
Would you like me to try anything else with the app configuration, or would you prefer to wait until the upload issue is resolved?
✻ Brewed for 16m 2s