I looked at the MCP protocol over the weekend and build an MCP Server for Fibery 
Claude understands that I want to create a support ticket entity inside my Fibery workspace:
It works! The ticket was created:
Here is a sharelink to the example MCP Tool I build:
https://fiberflow.fiberflow.io/@public/Templates/Ticket/470890d1-9d28-4b0c-9846-6f22a5512eff
I started out with generic tools like “Get the schema of a Fibery database” and “Create an entity” (this is how the Airtable MCP works). I quickly realized that this is very difficult for the AI to get right. The AI Agent has to understand the Fibery schema and how each field is structured in order to create an entity or query a database with the correct select statement.
Instead, the user has to be able to build their own MCP Server Tools for their Fibery setup. Fibery is a flexible platform where the user can build whatever they want, so the MCP Server has to be very flexible as well. The user should be able to craft dedicated MCP Tools that allow the AI Agent to perform certain use-cases inside the Fibery workspace. A list of useful things that the AI can do with a lot of context provided via the description of the respective tool. This is also also a lot safer than to give the AI full access to every database and allow read, create, update and delete operation on every entity in Fibery 
I also discovered that the response the MCP Tool sends back to the AI Agent has to be very flexible as well. The formatting of the returned entity might be better as a well-crafted plaintext that only contains the relevant properties instead of just JSON.stringify the entire entity. Also if an error occurs, the AI has to exactly know what went wrong, why and how to fix the issue.
So here is the solution I came up with: The user can build an MCP Tool with a no-code interface by providing the inputs of the tool (what the AI has to provide when calling the tool), the actions that should be performed inside the Fibery workspace (e.g., create a new support ticket) and what to respond back to the AI Agent. So each MCP Tool is an automation that can be executed by the AI Agent.
Testing the MCP Tool by asking the AI Agent to call it every time is very cumbersome, so I added the option to manually run the MCP Tool:
The MCP server allows for inputs to be required / optional, I added that option but the Claude AI Agent does not seem to understand that an input is optional at this moment 
Here is a simple example where I use the flexibility of the automation engine to give the AI Agent a tool that solves a use-case instead of only doing basic data manipulation. I will add more actions in the next couple of days like “Search for entities” action with filtering, which is very useful for building MCP Tools.
I am curious if this is way of building an MCP Server for Fibery is useful to you or whether you had something totally different in mind
You can try it out over at app.fiberflow.io
Cheers,
Ben