Outsystems Mcp

Distribution repo for the OutSystems MCP. To install, paste the matching prompt below into your AI assistant.

Every harness section below sets up two artifacts and says how to keep the skill current. Your agent needs both: the MCP server without the skill gives it every tool and none of the rules, the confirm-before-destructive rule included, and the skill without the MCP server leaves it nothing to call. Some hosts deliver both in one step; the section says so when that is the case. The latest published skill is the one on the main branch of this repo; there are no release notes, so the commit history is where changes show up.

• Skill: the document that tells the agent how to work with OutSystems: confirm before changing tenant state, poll long-running operations until they finish, decide retries from the error category, prefer the asset key over names. It changes with new releases, so each section carries an Update step. Some hosts wrap it in a plugin or a Power.
• MCP server: the OutSystems endpoint at https://<my-tenant>/mcp, which exposes the tools and signs you in to your tenant. OutSystems hosts it and updates it on the tenant side, and your harness only stores its URL; if you reach it through the mcp-remote local proxy, as the Claude Desktop install does, also keep mcp-remote at 0.14.0 or later (see Install - Claude Desktop).

Install - Claude Code

Skill and MCP server: one plugin install delivers both. The plugin carries the skill and declares the MCP server from your tenant hostname. Paste into Claude Code:

Install the OutSystems outsystems-mcp plugin from OutSystems/outsystems-mcp on GitHub.
Step 1: ask me for my OutSystems tenant hostname (something like `mycompany.outsystems.dev`). Strip any scheme, leading `www.`, trailing slash, and path or query, keeping only the host. If the result doesn't match `^[A-Za-z0-9]([A-Za-z0-9.-]*[A-Za-z0-9])?$`, ask again rather than proceeding with an unvalidated value: the next step does not validate it, and a value carrying a scheme prefix or a path produces a server URL that cannot resolve.
Step 2: run `claude plugin marketplace add OutSystems/outsystems-mcp`.
Step 3: run `claude plugin install outsystems@outsystems --config tenant_hostname=<my-tenant>`, where `<my-tenant>` is exactly the bare hostname from Step 1. The plugin declares the MCP server itself, at `https://<my-tenant>/mcp`, so there is no separate `claude mcp add` step. If `claude` rejects `--config`, my Claude Code predates plugin options: tell me to update Claude Code and re-run this step; if updating is not possible, install without `--config` and tell me to run `/plugin configure outsystems@outsystems` and type that same bare hostname there. Never add a `--client-id` or pin a callback port anywhere: the server supports OAuth Dynamic Client Registration, so Claude Code registers its own client on an ephemeral loopback port.
Step 4: run `claude mcp list`. Expect either `plugin:outsystems:outsystems: https://<my-tenant>/mcp`, or, if I installed before 0.20.0, only `outsystems: https://<my-tenant>/mcp`: that is an older entry hiding the plugin's server as a duplicate. In the second case, or if both appear with different URLs, run `claude mcp get outsystems` to read its `Scope` and `URL`, tell me both, and, unless that scope is `project` (shared config: report it and let me decide), ask before running `claude mcp remove outsystems -s <that scope>`; then re-run `claude mcp list` and confirm `plugin:outsystems:outsystems` now appears. If the list shows no `outsystems` line at all, the tenant option was not stored: re-run Step 3.
Step 5: tell me to restart Claude Code, then ask anything OutSystems-related; you'll drive the OAuth flow automatically via Claude Code's synthesized `authenticate` tool (a client convenience, not a server tool). If that doesn't trigger, or a call fails with an auth