Outsystems MCP Server
OutSystems resources interact directly with your AI through this bridge.
Data last scanned today · Reviewed today
Overview
This repository provides a bridge for AI assistants to interact with OutSystems environments. Designed for developers to facilitate agentic workflows, it uses OAuth Dynamic Client Registration for authentication, allowing the server to handle the handshake process automatically with your OutSystems tenant. Installation varies significantly by environment. WhileClaude Code supports direct installation, Claude Desktop users must use a local proxy configuration to bypass limitations related to OAuth redirect URIs. The server includes specialized tools for sending feedback directly to the maintainers regarding your experience with the agent.
Our verdict
This server is classified with a high risk level, receiving a security score of 40/100. Because it is community-maintained rather than provided by the official vendor and remains in an early alpha stage, it lacks production-level reliability. Users should note that critical components like authentication methods and read-only mode behavior have not yet been subject to formal security review. It is recommended only for experimental or non-critical use by developers who are comfortable troubleshooting breaking changes.
- Zero direct dependencies reduce potential supply-chain vulnerabilities.
- Supports OAuth Dynamic Client Registration for streamlined authentication.
- Active development with commits recorded within the last week.
- MIT licensed for open accessibility.
- Early alpha status implies unstable behavior and potential bugs.
- Not maintained or officially supported by OutSystems.
- Authentication and read-only security aspects are currently unreviewed.
- Requires manual proxy configuration for Claude Desktop installs.
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›Is this MCP server ready for production use?
No, the project is in an early alpha stage and is provided as-is without warranties or guarantees. It is not production-ready and may contain bugs, incomplete features, and unstable behaviors.
›How do I provide feedback on the agent experience?
In Claude Code, you can use the /outsystems-feedback <message> command. In other environments, ask the agent to send feedback in plain language to invoke the underlying feedback tool.
›Can I install this server using the native 'Add custom connector' flow in Claude Desktop?
No, the native Claude Desktop flow will fail during OAuth sign-in because the identity provider rejects the claude.ai callback URL. You must use the provided local proxy instructions involving mcp-remote.
›Are there any specific prerequisites for installing in Claude Desktop?
You must have Node.js installed and available on your machine, and you need to install the mcp-remote package globally using npm install -g mcp-remote.
›Does the server require manual client ID configuration?
No, the server supports OAuth Dynamic Client Registration, meaning the client is registered automatically via an ephemeral loopback port.
›Is a subscription required to use this MCP server?
Yes, using plugins with Claude Desktop requires a paid plan, such as Pro, Max, Team, or Enterprise, and usage may be restricted by Enterprise administrators.
Badge
Maintain this server? Add the live badge to your README.