Enhanced MCP server for Limitless Pendant with advanced conversation analysis, meeting detection, action item extraction, and comprehensive
Free
Nothing to run from here
Outsystems Mcp Extended is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
Community MCP server that fills the gaps in the official OutSystems ODC MCP. Adds Asset Repository, Asset Configurations, Code Quality, Dependency Management, Portfolio, Native Mobile Build, UAM reads, and Environment Configuration tools — by wrapping the
Quickstart
# 1 — run it from where its publisher ships it
npx -y outsystems-mcp-extended
# 2 — ask your agent something
> Community MCP server that fills the gaps in the official OutSystems ODC MCP. Adds Asset Repository, Asset Configurations, Code Quality
Outsystems Mcp Extended is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
RPAll 1 server
rpgomes-code1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Outsystems Mcp Extended as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add outsystems-mcp-extended -- npx -y outsystems-mcp-extendedReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
55 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Retrieve env-wide default system configurations (SMTP, CSP, log level defaults). Wraps GET /api/asset-configurations/v1/environments/{envKey}/default-system-configurations.
Takes no parameters.
Example callreturns →
Retrieve runtime configurations of a deployed AI Agent in an environment. Wraps GET /api/asset-configurations/v1/environments/{envKey}/agents/{agentKey}/revisions/deployed/configurations.
Takes no parameters.
Example callreturns →
Retrieve the runtime configurations of a deployed application in a given environment. Wraps GET /api/asset-configurations/v1/environments/{envKey}/applications/{appKey}/revisions/deployed/configurations. Use to debug
Takes no parameters.
Example callreturns →
Retrieve full details for a single asset by key. Wraps GET /api/asset-repository/v1/assets/{assetKey}. More detail than asset_list rows.
Takes no parameters.
Example callreturns →
List assets in the asset repository — the canonical
Takes no parameters.
Example callreturns →
Retrieve details for a specific revision of an asset. Wraps GET /api/asset-repository/v1/assets/{assetKey}/revisions/{revisionNumber}.
Takes no parameters.
Example callreturns →
Retrieve the metadata of an asset revision (template type, URL path, deployability flags, model digest). Wraps GET /api/asset-repository/v1/assets/{assetKey}/revisions/{revisionNumber}/metadata.
Takes no parameters.
Example callreturns →
Retrieve the release notes of an asset revision. Wraps GET /api/asset-repository/v1/assets/{assetKey}/revisions/{revisionNumber}/release-notes. Use for changelog generation.
Takes no parameters.
Example callreturns →
List the full revision history of an asset. Wraps GET /api/asset-repository/v1/assets/{assetKey}/revisions.
Takes no parameters.
Example callreturns →
Bulk-resolve asset revisions by key+revision filters, optionally embedding release notes, icon, source-code refs, signature, metadata. Wraps POST /api/asset-repository/v1/assets/search. Use to resolve many asset keys in one call.
Takes no parameters.
Example callreturns →
Show the current OutSystems authentication status. Returns tenant ID, user ID, OAuth client, issuer (Keycloak realm), scope, expiry, and whether a refresh token is available for silent re-auth. If no token is currently stored, indicates that and points to the
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Finalizes OAuth when the local callback listener cannot be reached from the browser host (SSH session, remote devcontainer, etc.). Pass the full URL the user copied from their browser
Takes no parameters.
Example callreturns →
List all consumer assets of a given asset — i.e.,
Takes no parameters.
Example callreturns →
Launch an async analysis of what would break if an asset were deleted. Returns an analysis key; poll with dep_deletion_analysis_status. Wraps POST /api/dependency-management/v1/deletion-analyses. Use as pre-flight safety check before destructive operations.
Takes no parameters.
Example callreturns →
Retrieve the deletion-impact analysis report. Wraps GET /api/dependency-management/v1/deletion-analyses/{analysisKey}. Poll after dep_deletion_analysis_start until report is complete.
Takes no parameters.
Example callreturns →
Async analysis of what would change if an asset were deployed to a target environment. Wraps POST /api/dependency-management/v1/deployment-analyses. Returns an analysis key; poll with dep_deployment_analysis_status. Use as pre-flight before promoting to production.
Takes no parameters.
Example callreturns →
Retrieve the deployment-impact analysis report. Wraps GET /api/dependency-management/v1/deployment-analyses/{analysisKey}. Poll after dep_deployment_analysis_start until report is complete.
Takes no parameters.
Example callreturns →
What does this asset revision depend on? Returns the list of producer (upstream) assets. Wraps GET /api/dependency-management/v1/assets/{assetKey}/revisions/{revision}/producers. Inverse of dep_consumers.
Takes no parameters.
Example callreturns →
Search for public elements (entities, actions, structures) across the tenant by name, description, or type. Wraps POST /api/dependency-management/v1/public-elements/search. Use to answer
Takes no parameters.
Example callreturns →
List the public elements (from other assets) that a specific revision actually uses. Wraps GET /api/dependency-management/v1/assets/{assetKey}/revisions/{revision}/referenced-elements. Use to scope refactors —
Takes no parameters.
Example callreturns →
List the public entities, actions, structures exposed by a specific asset revision. Wraps GET /api/dependency-management/v1/assets/{assetKey}/revisions/{revision}/public-elements. Use to understand the public API contract of an asset version.
Takes no parameters.
Example callreturns →
Retrieve the default domain that an environment uses to serve apps. Wraps GET /api/environment-configurations/v1/environments/{envKey}/default-domain.
Takes no parameters.
Example callreturns →
List custom domains configured on an environment. Wraps GET /api/environment-configurations/v1/environments/{envKey}/domains. Use to answer
Takes no parameters.
Example callreturns →
List IP filter groups configured on an environment. Wraps GET /api/environment-configurations/v1/environments/{envKey}/ip-filter-groups. Use when debugging 403 errors that might be IP-restricted.
Takes no parameters.
Example callreturns →
List native mobile build operations across the tenant. Wraps GET /api/native-mobile-builds/v1/build-operations. Use to recover lost operation keys or audit recent builds.
Takes no parameters.
Example callreturns →
Fetch log messages for a native mobile build operation. Wraps GET /api/native-mobile-builds/v1/build-operations/{operationKey}/log-messages. Use to diagnose Error-status builds.
Takes no parameters.
Example callreturns →
Start a native iOS or Android build for a mobile application. Wraps POST /api/native-mobile-builds/v1/build-operations. Returns an operation key; poll with mobile_build_status. This is the entry point for the full native mobile workflow that
Takes no parameters.
Example callreturns →
Retrieve status and details of a native mobile build operation. Wraps GET /api/native-mobile-builds/v1/build-operations/{operationKey}. Poll after mobile_build_start until terminal; when complete the response carries download URLs.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
List the native builder (MABS) versions available in the tenant. Wraps GET /api/native-mobile-builds/v1/native-builder-versions. Use to know which MABS versions can be set in mobile_config_android_patch / mobile_config_ios_patch.
Takes no parameters.
Example callreturns →
Retrieve the Android build configuration of a mobile app in an environment (keystore alias, appIdentifier package name, MABS version, framework, build type). Wraps GET /api/native-mobile-builds/v1/environments/{env}/applications/{app}/configurations/android.
Takes no parameters.
Example callreturns →
Update the Android build configuration of a mobile app (set appIdentifier package name, keystore, MABS version, etc.). Wraps PATCH /api/native-mobile-builds/v1/environments/{env}/applications/{app}/configurations/android. All fields are optional partial updates. Setting
Takes no parameters.
Example callreturns →
Retrieve the iOS build configuration of a mobile app in an environment (signing certificate, provisioning profile, appIdentifier bundle ID, MABS version, framework, build type). Wraps GET /api/native-mobile-builds/v1/environments/{env}/applications/{app}/configurations/ios.
Takes no parameters.
Example callreturns →
Update the iOS build configuration of a mobile app (signing cert, provisioning profile, bundle identifier, MABS version, framework). Wraps PATCH /api/native-mobile-builds/v1/environments/{env}/applications/{app}/configurations/ios. All fields are optional partial updates.
Takes no parameters.
Example callreturns →
Suggest the next mobileVersionNumber and mobileVersionCode for a mobile app based on previous builds. Wraps POST /api/native-mobile-builds/v1/build-operations/version-suggestions. Use before mobile_build_start to avoid colliding with prior versions.
Takes no parameters.
Example callreturns →
Cross-environment inventory of deployed assets — the canonical
Takes no parameters.
Example callreturns →
Tenant-wide status of the code-quality analysis pipeline. Wraps GET /api/code-quality/v1/analysis-status. Useful for checking whether analyses are caught up before relying on findings/summary.
Takes no parameters.
Example callreturns →
Submit a code-quality analysis request for a specific asset revision. Async — returns an analysis key; poll with quality_analyze_status. Wraps POST /api/code-quality/v1/code-analyses. Use before quality_asset_summary when a revision hasn
Takes no parameters.
Example callreturns →
Retrieve status and findings of an in-flight or completed code-quality analysis. Wraps GET /api/code-quality/v1/code-analyses/{analysisKey}. Poll after quality_analyze_start until status is terminal, then use quality_asset_summary for the digested view.
Takes no parameters.
Example callreturns →
Retrieve the code-quality analysis summary for a specific asset revision — findings breakdown by severity plus the quality score. Wraps GET /api/code-quality/v1/assets/{assetKey}/revisions/{revision}/analysis-summary. Use as a single-call
Takes no parameters.
Example callreturns →
Quality metrics (scores, finding counts) per asset across the tenant. Wraps GET /api/code-quality/v1/assets-quality-metrics. Use to rank assets by quality or identify which ones need attention.
Takes no parameters.
Example callreturns →
List static-analysis code-quality findings across the tenant. Optionally filter by asset, severity, or pattern ID. Wraps GET /api/code-quality/v1/findings. Useful pre-deploy or pre-refactor to catch regressions before they ship. Required permission: Asset Management > Read.
Takes no parameters.
Example callreturns →
Aggregate summary of code-quality findings across the tenant — counts by category and severity. Wraps GET /api/code-quality/v1/findings-summary. Use for dashboards or
Takes no parameters.
Example callreturns →
Historical trend of code-quality findings over time. Wraps GET /api/code-quality/v1/findings-trend. Use to track
Takes no parameters.
Example callreturns →
Retrieve full detail for a single code-quality pattern (description, rationale, severity, examples). Wraps GET /api/code-quality/v1/patterns/{patternId}. Use to look up the meaning of a patternId from quality_findings.
Takes no parameters.
Example callreturns →
List the catalog of code-quality patterns (rules) the platform checks for. Wraps GET /api/code-quality/v1/patterns. Use to discover what rules are enforced before writing code, or to look up a patternId returned by quality_findings.
Takes no parameters.
Example callreturns →
List application-level roles defined across the tenant. Wraps GET /api/identity/v1/application-roles. Use to understand role-based access for impact analysis (
Takes no parameters.
Example callreturns →
List all users who have a given application role. Wraps GET /api/identity/v1/application-roles/{key}/users. Use to answer
Takes no parameters.
Example callreturns →
List tenant groups. Wraps GET /api/identity/v1/groups. Use to enumerate the group structure for role assignment.
Takes no parameters.
Example callreturns →
List org-level roles defined in the tenant. Wraps GET /api/identity/v1/organization-roles.
Takes no parameters.
Example callreturns →
List the tenant
Takes no parameters.
Example callreturns →
List all application roles assigned to a specific user. Wraps GET /api/identity/v1/users/{key}/application-roles. Use to answer
Takes no parameters.
Example callreturns →
Retrieve full details for a single user. Wraps GET /api/identity/v1/users/{key}. Returns name, email, status, last login, photo, etc.
Takes no parameters.
Example callreturns →
Search tenant users by name, email, or other filters. Wraps GET /api/identity/v1/users. Use to resolve user identities for impact analysis, audit, or onboarding workflows. Returns up to 100 users per page.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Outsystems Mcp Extended costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 96 / 100
Release 1.0.0 · scanned 26 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest940b3b7d164750d8dd1fd5f222d658372a6b40b97eea60a298f202c351d4363a
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (55 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| asset_config_env_defaults | no tags | |
| asset_config_get_agent | no tags | |
| asset_config_get_app | no tags | |
| asset_get | no tags | |
| asset_list | no tags | |
| asset_revision_get | no tags | |
| asset_revision_metadata | no tags | |
| asset_revision_release_notes | no tags | |
| asset_revisions_list | no tags | |
| asset_search | no tags | |
| auth_status | no tags | |
| authenticate | no tags | |
| complete_authentication | no tags | |
| dep_consumers | no tags | |
| dep_deletion_analysis_start | no tags | |
| dep_deletion_analysis_status | no tags | |
| dep_deployment_analysis_start | sensitive-source | |
| dep_deployment_analysis_status | no tags | |
| dep_producers | no tags | |
| dep_public_elements_search | no tags | |
| dep_referenced_elements | no tags | |
| dep_revision_public_elements | no tags | |
| env_config_default_domain | no tags | |
| env_config_domains_list | no tags | |
| env_config_ip_filter_groups_list | no tags | |
| mobile_build_list | no tags | |
| mobile_build_logs | untrusted-input | |
| mobile_build_start | no tags | |
| mobile_build_status | untrusted-input | |
| mobile_build_validate | no tags | |
| mobile_builder_versions | no tags | |
| mobile_config_android_get | no tags | |
| mobile_config_android_patch | no tags | |
| mobile_config_ios_get | no tags | |
| mobile_config_ios_patch | no tags | |
| mobile_version_suggestions | no tags | |
| portfolio_deployed_assets | no tags | |
| quality_analysis_status | no tags | |
| quality_analyze_start | no tags | |
| quality_analyze_status | no tags | |
| quality_asset_summary | no tags | |
| quality_assets_metrics | no tags | |
| quality_findings | no tags | |
| quality_findings_summary | no tags | |
| quality_findings_trend | no tags | |
| quality_pattern_get | no tags | |
| quality_patterns_list | no tags | |
| uam_application_role_list | no tags | |
| uam_application_role_users | no tags | |
| uam_groups_list | no tags | |
| uam_organization_roles_list | no tags | |
| uam_permissions_list | no tags | |
| uam_user_application_roles | no tags | |
| uam_user_get | no tags | |
| uam_user_search | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest940b3b7d164750d8
Scanned2026-08-26
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 1.0.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
1.0.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Outsystems Mcp Extended in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.