Have something to say?

Tell us how we could make the product more useful to you.

MCP error: add_url_source via MCP never triggers crawler (sources stuck PROCESSING)

Date: 2026-04-05 MCP Server: Chipp (build.chipp.ai/mcp, streamable-http transport) MCP Client: Claude Code v2.1.92 (Anthropic CLI, macOS) Steps to reproduce Call add_url_source via MCP to add a URL-based knowledge source: { "appId": 10041051, "url": "https://portal-conneva.vercel.app/api/mosaic/knowledge/index.html", "crawlAllLinks": true } Result Source is created successfully and returns a source ID (e.g., dd18f40d-5de9-46a1-a1c8-2a41a9686237). However, the source remains in PROCESSING status indefinitely β€” the crawler never picks it up. Calling get_crawl_progress on the source returns: { "error": { "code": "INTERNAL_ERROR", "message": "Failed to connect before the deadline" } } Expected Source transitions through PENDING β†’ PROCESSING β†’ COMPLETED as the crawler fetches and indexes the content. This is the behavior observed when adding the same URL via the Chipp dashboard. Root cause evidence Dashboard-added sources crawl fine. The same URL was added manually through the build.chipp.ai dashboard and crawled to COMPLETED status successfully. Two individual topic URLs were also added via dashboard and indexed correctly. MCP-created sources never start crawling. Multiple sources created via add_url_source MCP tool remain stuck at PROCESSING. No crawl activity is observed. The crawler itself is healthy. Dashboard-initiated crawls complete normally, confirming the crawler service is running. The issue is that MCP-created sources are not being enqueued for crawling. get_crawl_progress also fails for MCP-created sources with a "Failed to connect before the deadline" error, suggesting the crawl was never initiated (no Temporal workflow to query). Tested multiple times across different sessions and URLs β€” consistently reproducible. Workaround Add sources manually via the build.chipp.ai dashboard instead of the MCP add_url_source tool. Environment MCP Server: Chipp (build.chipp.ai/mcp, streamable-http, OAuth 2.0 + PKCE) MCP Client: Claude Code v2.1.92 (Anthropic CLI, macOS darwin) All other MCP tools (app management, list_knowledge_sources, delete_knowledge_source, custom actions, system prompt, branding) function normally for this workspace and app.

Mark Carlson about 1 month ago

1
πŸ›

Bugs

MCP bug: search_documentation fails with Postgres connection error

Date: 2026-03-22 MCP Server: Chipp (build.chipp.ai/mcp, streamable-http transport) MCP Client: Claude Code (Anthropic CLI, macOS) Steps to reproduce Call search_documentation with any query: { "query": "add_document_source file upload base64" } Result { "error": { "code": "INTERNAL_ERROR", "message": "connect ECONNREFUSED 127.0.0.1:5432" } } Expected Returns relevant documentation excerpts. Root cause evidence The error connect ECONNREFUSED 127.0.0.1:5432 indicates the documentation search handler is attempting to connect to a PostgreSQL instance on localhost:5432. This suggests the docs search feature uses a local or sidecar Postgres database that is not running in the MCP server's deployed environment. Other MCP tools that use a different database connection (app CRUD, knowledge sources, custom actions) all work correctly, so this appears to be a database configuration issue specific to the documentation search feature. Tested twice in the same session β€” consistently fails with the same error. Environment MCP Server: Chipp (build.chipp.ai/mcp, streamable-http, OAuth 2.0 + PKCE) MCP Client: Claude Code (Anthropic CLI, macOS darwin) All other MCP tools (app management, knowledge sources, custom actions, system prompt, branding) function normally for this workspace and app.

Mark Carlson about 1 month ago

πŸ›

Bugs

MCP error: add_document_source fails with GCS credential error

Date: 2026-03-22 MCP Server: Chipp (build.chipp.ai/mcp, streamable-http transport) MCP Client: Claude Code (Anthropic CLI, macOS) Steps to reproduce Call MCP add_document_source tool with any file. Minimal example: { "appId": 10041051, "files": [ { "fileName": "test-topic.md", "content": "IyBUZXN0IFRvcGljCgpUaGlzIGlzIGEgdGVzdCBkb2N1bWVudCBmb3Ig dGhlIGtub3dsZWRnZSBiYXNlLg==" } ] } The base64 content decodes to: Test Topic This is a test document for the knowledge base. Result { "error": { "code": "INTERNAL_ERROR", "message": "The incoming JSON object does not contain a client_email field" } } Expected File uploads and begins processing (PENDING β†’ PROCESSING β†’ COMPLETED). Root cause evidence The error message "The incoming JSON object does not contain a client_email field" is produced by the Google Cloud Node.js client library (google-auth-library) when parsing a service account key file. It is thrown when the GoogleAuth constructor receives a credentials object missing the required client_email property. This suggests the add_document_source code path initializes a Google Cloud Storage (GCS) client to upload the decoded file, but the service account JSON key is either missing, malformed, or not configured in the MCP server's runtime environment. Evidence that other knowledge source tools work (same app, same session) The failure is isolated to the file upload code path. All other MCP tools β€” including other knowledge source tools (add_url_source, list_knowledge_sources, get_knowledge_source, delete_knowledge_source, refresh_knowledge_source) β€” work correctly for the same app and workspace. Environment MCP Server: Chipp (build.chipp.ai/mcp, streamable-http, OAuth 2.0 + PKCE) MCP Client: Claude Code (Anthropic CLI, macOS darwin)

Mark Carlson about 1 month ago

πŸ›

Bugs

User reports issue with file download

The users asked the app to summarize the issue, this is what it said: Chronological sequence of events: First attempt (PDF): At the user's request, I created a PDF file containing a summary of the exercises. When attempting to open the generated link, the user received an error message. Second attempt (PDF): Assuming it was an isolated error, I created a completely new PDF file. The result was identical; this link also led to the same error message. Third attempt (Word document): As an alternative, we suggested a Word document (.docx). I created the file, but unfortunately the exact same error occurred here as well. The user was unable to download the file. Detailed error description: The user was kind enough to send a screenshot of the error message. It is an XML error page storage.googleapis.com with the following content: Code: AccessDenied Message: Access denied. Details: Anonymous caller does not have storage.objects.get access to the Google Cloud Storage object. Permission β€˜storage.objects.get’ denied on resource (or it may not exist). Analysis and interpretation of the error: Essentially, this means that the files I created on Google Cloud Storage are not correctly shared for anonymous (public) download. This appears to be a general permission issue in the system configuration that prevents users from accessing the generated files.

Matthias Werner 2 months ago

πŸ›

Bugs

User reports with file download

A paying customer complained about broken file downloads. I check the affected chat and it seems indeed that the provided files cannot be downloaded. Also changing the format didn’t help. The affected chat is ID: 17ef026d-1548-4861-81d4-42196ccbd3aa To me, the links to the file downloads seem legit but they don’t start. It’s frustrating, since the cost for Chipp increased massively due to the usage-based pricing. While I think it’s absolutely fair that, we as Chipp users carry these, but then I expect it to work properly. Certainly, these messages with broken file downloads count against my token usage and I am not happy to pay for token consumption that doesn’t benefit my end users at all but rather increases the risk they churn. Here is what the user said: β€œI am contacting you because I am repeatedly encountering a technical problem when creating a file with the virtual employee Seedy [the name of the app]. I have been trying to create an absence planner for my team for some time now. Seedy has already generated several download links for HTML and Word files for me. Unfortunately, every time I click on one of these links, I get an error message and the download does not start. We have already tried several solutions, including: Generating several completely new download links. Reducing the file size (from an annual planner to a single month). Changing the file format. Unfortunately, none of these steps were successful. As I need the overview for my team planning, I would be very grateful if you could look into the problem.β€œ

Matthias Werner 3 months ago

πŸ›

Bugs