Skip to content
Back to search

mcpme

The MoWare MCP Server

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/danielstieger--mcpme/badge.svg)](/listings/danielstieger--mcpme)

HTML

<a href="/listings/danielstieger--mcpme"><img src="/api/listings/danielstieger--mcpme/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 146 lines
  1. ```text
  2. __ __ __ __ _____
  3. | \/ | ___ _ __ | \/ || ____|
  4. | |\/| | / __|| '_ \ | |\/| || _|
  5. | | | || (__ | |_) || | | || |___
  6. |_| |_| \___|| .__/ |_| |_||_____|
  7. |_|
  8. ```
  9. # McpME
  10. An MCP server that lets an agent operate a MoWare business application the way a person does:
  11. through the application's commands and pages, with that person's permissions.
  12. McpME is a toolkit implementation of the MoWare DataUX runtime, next to the browser and desktop
  13. toolkits. The application model stays unchanged. Where the other toolkits draw a window, McpME
  14. hands the same content to the agent as data.
  15. ## Why
  16. - **The agent sees what a person sees.** Pages, fields, tables and messages come from the same
  17. runtime that serves the user interface. Nothing is exposed that the application does not show.
  18. - **The agent can do what that person may do.** Every permission check, validation and business
  19. rule of the application applies, because the agent goes through the same commands.
  20. - **Every action is attributable.** The agent never works on its own account. It always acts on
  21. behalf of a signed-in person, and the application records it under that person's name.
  22. ## What an agent gets
  23. Ten tools, the same for every application:
  24. | Tool | Purpose |
  25. | --- | --- |
  26. | `get_overview` | Commands that can be started now, and the commands already open |
  27. | `describe_command` | Parameters and documentation of a command |
  28. | `start_command` | Start a command from an entry, or directly with parameter values |
  29. | `get_state` | Page, messages, forms, tables, commands and conclusion actions of the active command |
  30. | `get_rows` | Rows of a table by range or text search |
  31. | `set_fields` | Set form field values |
  32. | `select_rows` | Set the row selection of a table |
  33. | `conclude` | Run a conclusion action of the page, such as saving or moving on |
  34. | `cancel_command` | Cancel the active command |
  35. | `switch_command` | Make another open command the active one |
  36. Every changing tool returns the full state of the active command, so the agent does not have to
  37. ask again. Documents the application produces arrive as URLs, charts as their data.
  38. A session with an order application looks like this:
  39. ```text
  40. start_command(label: "Search for orders")
  41. get_rows(table: "Order", search: "order 77") -> position 76
  42. start_command(entry: "Order-1", table: "Order", rows: [76])
  43. start_command(label: "Edit Order Position", table: "OrderPosition", rows: [2])
  44. conclude(action: 964284453, fields: {"posValue": "42,50"})
  45. start_command(label: "Print Order") -> order78.pdf
  46. conclude(action: 190784468) -> saved
  47. ```
  48. ## Requirements
  49. - Java 21 or newer
  50. - Tomcat 11 (Jakarta Servlet 6.1)
  51. - A MoWare installation: the runtime jars from the MoWare plugin and the generated classes of
  52. an application
  53. - The [MCP Java SDK](https://github.com/modelcontextprotocol/java-sdk) and Nimbus JOSE + JWT,
  54. fetched by Gradle
  55. McpME does not run without the MoWare platform. This repository contains the server only.
  56. ## Build and deploy
  57. The paths to the MoWare plugin, the platform sources, the application and Tomcat are set in
  58. `gradle.properties`. The values in the repository are those of the development machine.
  59. ```sh
  60. ./gradlew deploy
  61. ```
  62. This packs the runtime jars into the plugin, builds one WAR containing McpME, the runtime and the
  63. application, and copies it to Tomcat. The MCP endpoint is then at
  64. ```text
  65. http://<host>:<port>/<application>/mcp
  66. ```
  67. ## Configuration
  68. An application gets its own configuration (OFXConfig) with McpME's factories:
  69. - `org.modellwerkstatt.mcpme.core.McpAppFactory` as application factory
  70. - `org.modellwerkstatt.mcpme.print.McpPrintFactory` as print factory
  71. Settings of the application factory:
  72. | Setting | Default | Meaning |
  73. | --- | --- | --- |
  74. | `FixedUser` | none | Sign in every session as this user. For development only; turns sign-in off. |
  75. | `MaxRowsPerTable` | `20` | Rows of a table in one result |
  76. | `MaxOpenCommands` | `5` | Commands that may be open side by side |
  77. | `ShowFolded` | `true` | Include fields and columns the user interface folds away |
  78. | `SessionIdleMinutes` | `60` | Idle time after which a session is closed |
  79. | `PublicUrl` | from the request | Address of the endpoint as clients see it |
  80. ## Sign-in
  81. Without `FixedUser`, McpME is an OAuth resource server. It checks the access token of every
  82. request, answers `401` with a pointer to its metadata (RFC 9728) and binds the MCP session to the
  83. person from the token.
  84. Sign-in through Entra ID is configured with one `EntraIdMcpAuth` element: tenant, client id and
  85. secret of the app registration, the scope, and where the user name comes from, either a claim of
  86. the token or a Microsoft Graph query.
  87. Two things to know when using Entra ID:
  88. - Entra ID has no dynamic client registration. The MCP client needs a registered client id, for
  89. example `claude mcp add --transport http --client-id <id> --callback-port <port> ...`.
  90. - Entra ID rejects the `resource` parameter MCP clients send unless it matches the application id
  91. URI. With `Relay` switched on, which is the default, McpME passes sign-in and token requests on
  92. to Entra ID without it.
  93. MCP clients also look for the metadata at the root of the host. That is outside the web
  94. application and needs a rewrite rule in Tomcat or in the reverse proxy.
  95. ## Documentation
  96. The documentation is in German, in [`docu/`](docu):
  97. - [`mcp-spezifikation.md`](docu/mcp-spezifikation.md): the specification, with the decisions
  98. taken and the findings from testing
  99. - [`toolkit-schnittstelle.md`](docu/toolkit-schnittstelle.md) and the other `toolkit-*.md`
  100. files: the toolkit interface of the runtime that McpME implements
  101. ## Status
  102. McpME is a working prototype. It has been tested against one sample application with Claude Code
  103. as the agent, including sign-in through an Entra ID test tenant. It has not run against a
  104. production application.
  105. Known gaps:
  106. - File upload is not supported.
  107. - The user name through Microsoft Graph is implemented but untested.
  108. - Image fields and links are untested.
  109. - The URLs of generated documents are not protected by McpME.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.