I've been using the MCP for ODC lately and currently the bottle neck is context and mentor describing and applying logic.
The issue is why not allow other models direct access to the services/api to modify application just like mentor? or is there something wrong with my workflow?
I feel like the difference between MCP and just copy pasting from Claude is the context tools. Which is actually the only reason why AI is better in general.
Hi Wan,
I use the OutSystems MCP with Claude Code and Kiro, on both ODC and O11. Here is what I think.With MCP, your AI model can look at your app. It can search your tenant and inspect screens, data models, logic and roles. But it can't change the app model directly. When you build or change something, your agent passes the work to Mentor. OutSystems explains this in the GA announcment: https://www.outsystems.com/product-updates/outsystems-coding-mcpSo you are right that context is where your own model helps most. That is where I spend my effort. I give the model a spec of the app, with entities, naming and conventiions. I also try to give it skills that describe how I want things built, for example my own CRUD wrapper pattern. The clearer the request that reaches Mentor, the better.
Why can't the other models change the app directly? I can only guess from the outside. I think it is about where the MCP runs. On ODC, the MCP runs in the cloud and works across your whole tenant. So OutSystems puts Mentor in the middle to make and check the changes. Mentor builds th same app model as ODC Studio. Form what I've seen, it also uses a temporary environment before it publishes. A model that changed the app directly would skip these steps.I actually think this is a good thing. On ODC, changes go through a gate. Your model does not edit the OML directly. In my builds, every change became a new revision. The agent is also told to ask you before it publishes, deploys or rolls back. And everything runs as you, with your ODC roles and audit trail. For companies, I think this control is worth more than speed.O11 works differently. It does not use Mentor. The O11 MCP runs on your machine, inside Service Studio and works on the module you have open. Your model makes the changes itself, using the Outsystems Model API on a copy of the module. The gate there is Compare and Merge, where you confirm each change by default. Writing is still in Beta. Outsystems explains the difference here: https://success.outsystems.com/documentation/11/outsystems_mcp/outsystems_mcp_in_o11_and_odc/Your workflow is fine. I had problems too, like Mentor's usage limits. Small, clear requests work much better for me than big onces. I also publish after each step.If you're keen, I wrote about this: https://medium.com/@michael.de.guzman/the-metadata-wall-part-3-one-spec-two-platforms-8194c329a533