Skip to content

OutSystems MCP connector

Connect OutSystems to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can list your applications, environments and versions, check deployment status and start deployments, each person inside their own access, with every call logged.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Which version of the Customer Portal is in Production?

Working in OutSystems with Elaichi

  • List all OutSystems application versions
  • Get single OutSystems application version by ID
  • List all OutSystems applications
Ask anything…
Governance / Audit log Last 24 hours
OutSystems List all OutSystems applications Emily Carter · ChatGPT · 9:41 AM Done
OutSystems Get single OutSystems application version by ID Emily Carter · ChatGPT · 9:41 AM Done
OutSystems List all OutSystems application versions Emily Carter · ChatGPT · 9:41 AM Done
OutSystems OutSystems applications bulk update Megan Brooks · Claude · 9:38 AM Done
OutSystems Create a OutSystems deployment Ryan Hayes · Cursor · 9:35 AM Done

How to connect OutSystems to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

OutSystems MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

OutSystems MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

OutSystems MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

OutSystems MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

OutSystems MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect OutSystems to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with OutSystems through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in OutSystems is logged.

  • Engineering

    Check what is deployed where before a release

    Ask which version of an application is running in each OutSystems environment and get the answer in one place. No more clicking through every environment to compare version numbers.

  • Release management

    Start a deployment and follow it through

    Set up a deployment from one OutSystems environment to the next, run it, and ask for its status while it is in progress. The deployment runs under the name of the person who asked.

  • Platform operations

    Create or retire an environment for a project

    Stand up a new OutSystems environment when a project starts and remove it when the work is finished. Each change is recorded against the person who made it.

  • QA

    Confirm the build under test is right

    Pull the list of versions for an application and check that the one in the test environment matches what engineering says they shipped. Flag a mismatch before testing starts.

  • Security

    Pull the role list for an access review

    List every role defined in OutSystems and hand it to the reviewer, without asking an engineer to export it. Repeat the ask each quarter and compare.

  • Architecture

    Request source code for a review

    Ask for the source code package of an application or a single module and check when it is ready to collect. Useful for audits, handovers and code reviews across teams.

Try asking

  • “Which version of the Customer Portal is in Production?”
  • “List deployments to QA from the last week and their status”
  • “Show all environments and the applications running in each”

See all 23 OutSystems tools →

What connecting OutSystems gets you

6 screens from Elaichi, each doing one job for your OutSystems account.

Elaichi Agent

Ask Elaichi to work across your apps.

Which version of the Customer Portal is in Production?

List deployments to QA from the last week and their status

Show all environments and the applications running in each

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask OutSystems what is deployed where.

Plain questions about applications, versions and environments, answered from live OutSystems records.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint for OutSystems in every client.

Claude, ChatGPT and Cursor reach OutSystems through one governed endpoint, no SDK, no shared key.

ElaichiTools
Tool Action Description
List all OutSystems application versions List List all versions of a given OutSystems application in the infrastructure. Returns each version's Key, ApplicationKey, Version, ChangeLog, CreatedOn, InUse, and its MobileVersions and ModuleVersions details. Required: application_id.
Get single OutSystems application version by ID Get Get the download link for the binary file of a specific application version in OutSystems. Returns a link with url and expires. Required: application_id, id.
List all OutSystems applications List List all applications that exist in the OutSystems infrastructure. Returns application records with Key, Name, Kind, Description, URLPath, IconURL, IsSystem, and AppStatusInEnvs per-environment status.
OutSystems applications bulk update Update Block or unblock an OutSystems application from deployment in the environments provided by updating its configurations. Requires application_id and a configurations array with environmentKey, isBlocked, and isBlockedChangeReason. Returns an empty 204 response on success.
Create a OutSystems deployment Create Create a new deployment in OutSystems LifeTime between a source and target environment. Returns the created deployment details: SourceEnvironmentKey, TargetEnvironmentKey, Notes, and ApplicationOperations. Required: SourceEnvironmentKey, TargetEnvironmentKey, ApplicationOperations.

Tool catalog

23 OutSystems tools, no custom code.

Applications, versions, environments, deployments and roles, covered without writing a line of code.

ElaichiToolboxes
Name Source template Tools Created

Engineering toolbox

OutSystems · applications and modules

OutSystems starter 18 Mar 4, 2026

Release management toolbox

OutSystems · deployments and versions

— 9 Mar 2, 2026

Platform operations toolbox

OutSystems · environments and database mappings

— 24 Feb 27, 2026

QA toolbox

OutSystems · versions under test

OutSystems starter 6 Feb 19, 2026

Security toolbox

OutSystems · roles and access reviews

— 31 Jan 30, 2026

Architecture toolbox

OutSystems · source code reviews

— 12 Jan 22, 2026

Toolboxes

Every team gets its own OutSystems toolbox.

Release managers deploy, QA reads versions, each team scoped to what it needs.

ElaichiConnections
Connection Scope Status Access
OU

OutSystems (Core Platform)

Connected by Emily Carter

Personal • Active 1 team · 6 members
OU

OutSystems (Release Train)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
OU

OutSystems (QA Lab)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
OU

OutSystems (Customer Portal)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
OU

OutSystems (Internal Apps)

Connected by Ryan Hayes

Personal • Active Not shared
OU

OutSystems (Production Ops)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share OutSystems without sharing the API key.

One person connects, teammates work through it and never see the credential.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

OutSystems Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

OutSystems Applications Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

OutSystems Applications List Toolbox

Audit log

Every OutSystems deployment answers to a name.

When, who, what happened and which environment, written to an append-only log.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

OutSystems digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch applications

    OutSystems

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    OutSystems

    Queued

Workflows

A schedule ships the OutSystems release digest.

Deployments are fetched, grouped and drafted, a person approves, and it posts back to OutSystems.

OutSystems health

Refreshed 4 minutes ago · every 15 minutes · from the applications collection

Live

Applications

1,284 ↓ 12%

Environments

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Applications created

Last 14 days

By team

Share of activity

Core Platform 34%

Release Train 27%

QA Lab 21%

Customer Portal 18%

Collections and dashboards

OutSystems deployment health, computed, not asked for.

Four metrics, 14 days of deployments created and a breakdown by team, refreshed on schedule.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for OutSystems

All three can connect OutSystems to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for OutSystems, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over OutSystems tools Allow or restrict single OutSystems tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per OutSystems call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

OutSystems tools for your AI agents

23 tools are ready to call through Elaichi's MCP endpoint the moment you connect OutSystems, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

How do I connect OutSystems to Claude?

Connect OutSystems in Elaichi first, which asks for an API key from your OutSystems platform and nothing else. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and OutSystems is ready in Claude.

Does OutSystems work with ChatGPT and Cursor as well as Claude?

Yes. Once OutSystems is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect OutSystems once and every client picks it up.

What can an AI agent actually do with my OutSystems data?

It can list your OutSystems applications, their versions and your environments, tell you which application is running where, set up and run a deployment between environments, and check how a deployment is going. It can also create or remove an environment, list roles, and request a source code package for an application or module. Short, concrete asks such as "which version of Billing is in Production" work better than long sentences.

Does connecting OutSystems give the AI access to every environment?

No. Every call into OutSystems runs inside the access of the person who signed in, so an agent sees the applications and environments that person can already see in OutSystems. Elaichi can narrow that access further with roles and restrictions, and it can never widen it.

Can my team share one OutSystems connection?

Yes. One person connects OutSystems in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who ran each deployment or asked each question.

Can I stop an agent from deleting or changing things in OutSystems?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting an OutSystems environment or running a deployment for a role or for one person while leaving read actions open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

What happens to an OutSystems connection when someone leaves?

Offboarding a person in Elaichi ends their access to OutSystems through every client at once. A shared OutSystems connection keeps working for everyone else on the team. If you disconnect OutSystems in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.

Does the OutSystems MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. OutSystems is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for OutSystems?

Yes. Both let Claude, ChatGPT or Cursor use OutSystems. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every OutSystems call.

How is Elaichi different from Composio for OutSystems?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to OutSystems: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put OutSystems in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot