Hello,
I am encountering problems with connecting Grist MCP server to Gemini Enterprise and Mistral AI. In both cases I use Custom MCP server. I use paid hosted version of Grist.
The MCP server connected to Mistral actually worked for a few actually but it suddenly stopped.
Gemini case
Gemini Enterprise requires to fill Authentication method by myself. The screen below shows how I did it.
The connection was created according to this google documentation:
After clicking Verify Auth a Grist authentication window appeared, where I proceed to allow access.
Grist shows that third party app is authorized, however as you can seen in the google console screenshot there is a problem with authorization.
In order to auth third-party app I created an app in the Grist developer system. The scope and the client ID was checked multiple times.
Mistral AI case
As mentioned before it worked for few days without any issue. When first issues with connecting do Grist database showed up I decided to delete and recreate Grist credentials in Mistral. After deleting it, I am not able to create new credentials: after creating new MCP server, entering credential name (mistral requires it for each credential, it is just an internal name), clicking Connect the credential is not saved.
Summary
As the both platform have some problem with the auth I assumed there is problem on the Grist side. I opened there support cases, but so far nothing helpful from them.
Should I open grist support case too?