These instructions assume you have already signed up and activated your Outsystems Personal Edition.
- If you don’t have one yet, click here to get your own Personal Edition.
Setup an MCP Host for ODC
Install your favorite MCP host
OutSystems also supports the following MCP hosts:
- AWS Kiro
- Claude Code
- Cursor
- Any other MCP host that supports the MCP Streamable HTTP transport with OAuth connects to the same endpoint, without validated setup
All things being equal, we recommend you use AWS Kiro or Claude Code.
If you need more detaied instructions or help in setting up your coding agent, follow this link. For other MCP hosts, please follow the instructions on this link.
Log In to your Personal Edition
Open the Personal Edition home page and click the Start Building button. That will set up your Personal Edition environment and take you to it. Note the URL on top (e.g. personal-xxxxxxxx.outsystems.dev), as that is your tenant address. You will need it for your coding agent.
Launch your coding agent, start a new project if needed, and on the prompt paste the following:
$Read https://outsystems.com/mcp/outsystems-get-started.md and follow it.
Your coding agent will help you set it up interactively. You may be asked to perform some steps in your IDE to configure your coding agent's connection to OutSystems, add the integration manually, or authenticate depending on your tool of choice.
Building Your First App
After the setup, it may prompt you what you want to do next, and you may select Build a first app.
You might have to tell your agent to publish the app once it’s done, and answer additional questions as the several stages of the plan are executed.
That app works for the sake of this campaign, and at the time of writing we have tested that it can be built within the free AWS Kiro token quota. You can build something else as long as it gets deployed and you can run it!
After you build the app, submit this form, send us the URL to the app for us to check, and select the AWS Certification you'd like to win and you'll be in the draw. You won't enter the draw without submitting this form for us to validate your entry.
Accessing the app
Before you can access the app, you must give yourself the right permissions. Currently, none of the OutSystems MCP tools manage users or end-user roles, but you can learn how to do it by asking your MCP host:
❯Tell me how I can give permissions to my user to access the app. Also, tell me the URL of the app.
Feel free to keep iterating on the app, and ask for changes. For more details on creating a full application with OutSystems MCP, check this link.
Troubleshooting
If you need additional instructions, follow this link. For other MCP hosts, please follow the instructions on this link.
Other things you can do with the MCP Server
Kicking the tires
Inside Claude you can start inquiring about your environment. Here are some example prompts for you to try:
❯What can I do with the MCP server?
This gives you some inspiration on what you can do with the OutSystems MCP server. If you are connected to a factory, there are already some cool things you can try to explore your tenant. If not, don’t worry, we’ll build an app next.
❯What apps do I have installed?
Lists the apps available on your tenant.
Creating an application
You can use your agent to create a new app if you haven't yet. Copy this prompt into the agent to create the tested, sample app (use the Copy button; you don’t need to expand it):
❯Create an application using the following instructions# Build the IT Help Desk appBuild an OutSystems web app named "IT Help Desk" in my tenant. Employees submit IT support tickets, and the IT team tracks and resolves them. Work in the phases below. Send Mentor one turn per phase step, and build one screen per Mentor turn. Ask me before each publish, publish after each step, and send me the app's URL after the last publish.## Guidelines for MentorInclude these guidelines in every Mentor turn:* Apply OutSystems UI to every screen, and use OutSystems UI blocks, such as a Tag for the ticket status. Don't generate bare HTML layouts.* Give each screen exactly the roles listed for it. Don't make any screen anonymous or public.* Use ODC terminology only.* At the end of the turn, run a quick sanity check of what you changed, not a full audit of the app.## Phase 1: Data model, roles, and sample dataBuild the following data model, roles, and sample data in one Mentor turn, then publish.Entities:* Ticket: TicketNumber (Text, unique, generated as TCK-00001, TCK-00002, and so on), Subject (Text), Description (Text), SubmittedDate (DateTime), ResolvedDate (DateTime, optional), CreatedById (User Identifier), AssignedToId (User Identifier, optional), StatusId (TicketStatus Identifier), CategoryId (TicketCategory Identifier).* Comment: CommentText (Text), CreatedDate (DateTime), AuthorId (User Identifier), TicketId (Ticket Identifier). A ticket has many comments. Deleting a ticket deletes its comments.Static entities:* TicketStatus: New, Assigned, In Progress, Resolved, Closed.* TicketCategory: Hardware, Software, Network, Account Access, Other.Roles: Employee, IT Agent, IT Manager.Sample data: when the app starts with no tickets, create 5 sample tickets with different categories and statuses, each with one or two comments.## Phase 2: ScreensBuild the following screens in order, one screen per Mentor turn, and publish after each screen. Make every screen available to the Employee, IT Agent, and IT Manager roles.1. Ticket Queue: tickets that aren't Resolved or Closed, newest first, with TicketNumber, Subject, Category, Status, and SubmittedDate. Show Status as a Tag. Add a search on Subject and a filter by Status. Set Ticket Queue as the app's default screen, so the app's URL opens it.2. Ticket Details: the ticket's fields and its comments in chronological order, with author and date. Add a form to add a comment as the current user. Add a dropdown that lists the app's users to assign the ticket, and a dropdown to change its status. When the status changes to Resolved, set ResolvedDate to now. Make each row in Ticket Queue open Ticket Details.3. Submit Ticket: a form with Subject, Description, and Category, all required. On save, set SubmittedDate to now, CreatedById to the current user, and Status to New, generate the TicketNumber, then open the ticket's details. Add a menu with Ticket Queue and Submit Ticket.## Phase 3: DashboardBuild this phase only if I ask for it: a Dashboard with open tickets, tickets by category, and average resolution time, measured from SubmittedDate to ResolvedDate.## After the last publishSend me the app's URL. Then tell me that to open the app, my user needs one of the app's end-user roles in the stage I'm testing, and that my member access to ODC Portal and ODC Studio doesn't include it. Tell me to assign the roles in ODC Portal, under Management > Govern > Users, by opening my user and managing its end-user roles for IT Help Desk in the Development stage. Share these pages:* User management, which explains members and end-users: https://www.outsystems.com/tk/redirect?g=9e0fb9b7-d2b0-419f-a5d8-5b5ed730da5e* Grant or revoke user roles: https://www.outsystems.com/tk/redirect?g=df369b59-5c40-4954-9622-722503ee54d1…
You might have to tell it to publish the app once it’s done, and answer additional questions as the several stages of the plan are executed.
Before you can access the app, you must give yourself the right permissions. Currently, none of the OutSystems MCP tools manage users or end-user roles, but you can learn how to do it by asking your MCP host:
❯Tell me how I can give permissions to my user to access the app. Also, tell me the URL of the app.
Feel free to keep iterating on the app, and ask for changes. For more details on creating a full application with OutSystems MCP, check this link.
Visualize the architecture of your app
Run the following command in your MCP Host. Replace the name of the app for any other app you might have running in your server.
❯Run the outsystems-app-architecture on the IT Help Desk app
This will create a diagram of your application, its dependencies, UI flows, the works.