MCP not working

Bugs & Issues
1

Since this morning (2026-09-08) every tool call to the Fibery MCP Server fails with the same internal error, including get_me and schema: Error in get_me: AI Answer call failed with status: 404 and body: {“message”:“Request failed with status code 404”}.

The connection itself is fine - I reproduce it with a raw MCP client (not any AI tool): OAuth against https://mcp.fibery.io/mcp succeeds, initialize returns Fibery-MCP-Server 1.0.0, tools/list works, but every single tools/call (tested get_me, schema, query, search, fetch_by_url) comes back in ~120ms with the same “AI Answer call failed” 404.

Workspace: ontec-ai.fibery.io. Since even get_me fails, this looks like the internal “AI Answer” service behind the MCP tools is down or mis-deployed on your side rather than anything per-workspace. Could you check? Happy to provide more details.

2

Hi! MCP dev here. We see a burst of 404 errors for ai-ontec.fibery.io account on September 8th, and 0 logs for ontec-ai.fibery.io. We don’t have ai-ontec.fibery.io as registered workspace as well, so most likely the cause is simple. During authentication, we ask to enter workspace name, and it’s possible to sometimes enter the wrong workspace name. Could you, please, try to re-authenticate and enter “ontec-ai” in workspace field? Let me know if it works.

I’ve also noted the type of error you are getting, which authentication method did you use so non-existent workspace was not detected? This error message is unhelpful at all, too, sorry for that, will fix :slight_smile: