# 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.

Source: https://elaichi.ai/connectors/outsystems/

## Facts

| | |
| --- | --- |
| Application | OutSystems |
| Category | Application Development |
| AI tools | 23 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once OutSystems is connected

- 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

## Connect OutSystems in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick OutSystems.
2. Optionally set Share with, then press Connect.
3. Paste an OutSystems API key. One person generates a token in OutSystems and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which OutSystems tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## OutSystems MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
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

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

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

## OutSystems MCP connector for Microsoft Copilot

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

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

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

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

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

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a OutSystems tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with OutSystems through Elaichi

### Check what is deployed where before a release

Engineering. 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.

### Start a deployment and follow it through

Release management. 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.

### Create or retire an environment for a project

Platform operations. 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.

### Confirm the build under test is right

QA. 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.

### Pull the role list for an access review

Security. 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.

### Request source code for a review

Architecture. 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.

## 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.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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.

## All 23 OutSystems tools

Every tool below is callable through https://api.elaichi.ai/mcp once OutSystems is connected, subject to the toolbox it is in and the restrictions on the caller.

- **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.
- **OutSystems deployments execute** (Execute). Run a command ('start', 'continue', or 'abort') on an OutSystems LifeTime deployment. Execution is asynchronous: a successful call returns an empty 202 Accepted response with no body. Required: deployment_id, command.
- **Get single OutSystems deployment by ID** (Get). Get the details of an OutSystems LifeTime deployment by id, including any conflicts OutSystems detected. Returns: Deployment, ApplicationsToDeploy, ApplicationsToRedeploy, ApplicationConflicts, ModulesToDelete. Required: id.
- **Create a OutSystems application source code** (Create). Request source code access for an application in OutSystems LifeTime, kicking off asynchronous packaging of the app's source code on an environment. Returns: PackageKey, Status, Messages. Required: environment_id, application_id. Packaging runs asynchronously — poll Status and then fetch the download link.
- **Get single OutSystems application source code by ID** (Get). Get the download link for the source code package of an application in OutSystems LifeTime. Returns: url, expires, PackageKey, Status, Messages. Required: id (the package key returned when requesting source code access), environment_id, and application_id.
- **Get single OutSystems environment application by ID** (Get). Get the running version of a specific application in an OutSystems environment. Returns: Key, Name, Kind, Team, Description, URLPath, IconHash, IconURL, IsSystem, AppStatusInEnvs. Required: environment_id, id (the application Key).
- **List all OutSystems environment applications** (List). List the running versions of all applications in an OutSystems environment. Returns: Key, Name, Kind, Team, Description, URLPath, IconHash, IconURL, IsSystem, AppStatusInEnvs. Required: environment_id.
- **Create a OutSystems module source code** (Create). Request source code packaging for a module in an OutSystems environment. Returns: PackageKey, Status, Messages. Required: environment_id, module_id. Packaging is asynchronous — use PackageKey to poll the status until Done before fetching the download link.
- **Get single OutSystems module source code by ID** (Get). Get the download link for a module's packaged source code in OutSystems. Returns: url, expires, PackageKey, Status, Messages. Required: id (the package key from create), environment_id, module_id. The package status must be Done before the link is available.
- **List all OutSystems roles** (List). List all roles defined in OutSystems LifeTime. Returns: Key, name, description, manageInfrastructure, manageTeams, environmentPermissions, EnvironmentKey, ImportedUsers.
- **Create a OutSystems environment** (Create). Register an environment in LifeTime for OutSystems. Returns: EnvironmentKey, ImportedUsers. Required: EnvironmentName, EnvironmentAddress, ServiceCenterUsername, ServiceCenterPassword, LifeTimeAddress, EnvironmentPosition.
- **Delete a OutSystems environment by ID** (Delete). Unregister an environment from LifeTime in OutSystems by id. Returns: Key, Name, OSVersion, Order, HostName, UseHTTPS, EnvironmentType, NumberOfFrontEnds, ApplicationServerType, ApplicationServer, DatabaseProvider, IsCloudEnvironment. Required: id (the environment Key from the list response).
- **List all OutSystems environments** (List). List all environments registered in the OutSystems infrastructure. Returns: Key, Name, OSVersion, Order, HostName, UseHTTPS, EnvironmentType, NumberOfFrontEnds, ApplicationServerType, ApplicationServer, DatabaseProvider, IsCloudEnvironment, EnvironmentKey, ImportedUsers.
- **Get single OutSystems application source code status by ID** (Get). Get the status of an application source code access package in OutSystems LifeTime. Returns: PackageKey, Status, Messages. Required: environment_id, application_id, and id (the package key). Poll until Status is Done before requesting the download link.
- **Create a OutSystems deployment db mapping** (Create). Map the extensions' logical databases to database connections in an OutSystems deployment. Returns the confirmation message 'Mapping succeeded and deployment triggered'. Required: deployment_id, ExtensionKey, and DBMapping entries (DatabaseName, LogicalDatabaseName), one object per connection.
- **List all OutSystems deployment db mappings** (List). List the extension logical databases that still need to be mapped to database connections in the destination environment for an OutSystems deployment to proceed. Returns: ExtensionKey, ExtensionName, LogicalDatabase. Required: deployment_id.
- **Get single OutSystems deployment status by ID** (Get). Get the execution status of a deployment in OutSystems LifeTime by its deployment key id. Returns: DeploymentStatus, Info, DeploymentLog. Intermediate statuses such as running require re-polling until a terminal status such as finished_successful.
- **Create a OutSystems environment deployment** (Create). Create a new deployment in an OutSystems environment by uploading an app or solution binary file. Returns the deployment key of the created deployment. Required: environment_id and the binary file content (an OAP or OSP file).
- **Get single OutSystems module source code status by ID** (Get). Check the status of a module source code access package in an OutSystems Lifetime environment. Returns: PackageKey, Status, Messages. Required: id (package key), environment_id, module_id. Poll until Status is Done before requesting the download link.
