How do I stop needing the JWT token to refresh. Authorisation every day is probably a blocker for teams use.
Is it possible to connect multiple workspaces? Ie I have two workspaces a personal one and a work one but looks like I can only connect to a single mcp.
What is your setup in Claude so I can reproduce the JWT behaviour?
Regarding multiple workspaces, it is not possible to do it now unfortunately since authentication is bound to MCP url on the client’s side.
Navigate to Settings → Connectors → Add custom connector
Fill in the connector details and submit:
Name: Fibery
URL: https://mcp.fibery.io/mcp
After adding the connector, Claude will automatically initiate the OAuth 2.0 authentication process (no API tokens needed). If no luck, click Connect button for Fibery tool and try again.
Tried disconnecting, closing Claude desktop re-connecting and getting 401s JWT Token Expired.
I can get it to work for a short while but then stops. Feels like a very short time - few hours.
I have also tried resetting in the connecters in settings where there is another place to configure them.
Thanks for the details! I was able to reproduce it, and just deployed a fix. Claude Desktop/Web should start working fine now. However, Claude Code (in case You use it too) has a bug in their MCP Client implementation, hope they will fix it soon. Let me know if it helped!
Yes it seems to be a lot more stable now. Thank you for fixing so fast! The claude fibery integration is
Side question….
One thing I’m trying to figure out when Claude returns an entity from a query, I get back fibery/id and fibery/public-id but no URL.
Is there a way to get a direct link to an entity through the MCP? I’d love Claude to be able to surface a clickable link at the end of a query or creation so the user can jump straight to it in the app right now they have to go find it manually.
Is there a URL pattern I can construct from the available fields, or is this something you’re planning to expose through the MCP in future?
Regarding the links, thanks for the insight, we are working actively on MCP right now, so soon we will either add them automatically in the query tool, or add a tool which generates them from fibery-id/public-id-s. For now, a quirky work-around would be to tell Claude to provide URLs in format https://{workspace}.fibery.io/{Space}/{Database}/{fibery/public-id} should work (in case of a space in Space or Database name, it should be replaced with an underscore _).