Reported issues for mcp-sap-gui

Pod holds 10 of 10 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to mcp-sap-gui.

Most discussed

Add confirmation middleware using fastmcp elicitation

Add centralized middleware using fastmcp ctx.elicit() for two scenarios:

1. Destructive confirmation — before executing tools tagged destructive, prompt the user to confirm (e.g. "This will post 500 units to storage location 0001. Proceed?")

2. Guidance/disambiguation — when the agent encounters ambiguous situations, use elicitation to ask the user for clarification (e.g. "Found 3 matching materials. Which one?" or "This screen has two save buttons — which workflow?")

Approach: cent

Read the thread · 2026-03-31 · closed · 2 comments

Add focused search-help workflow tools

Add explicit search-help workflow support for the common F4/value-help path.

Why:

• Search help is a very common multi-step SAP pattern.
• It is too variable for a single mega-tool, but too repetitive to leave entirely manual.

Scope:

• Add sap_search_help_open(field_id).
• Add sap_search_help_select(...) for result selection and confirmation.
• Return the popup/screen context needed for the next step.
• Verify that the selected value lands back in the original field.

Acceptance criteria:

Read the thread · 2026-03-26 · closed · 2 comments

Expand automated test coverage for v0.2 architecture and workflows

Add the missing automated coverage needed to make the v0.2 architecture changes safe to evolve.

Why:

• The roadmap now includes session routing, policy evaluation, popup/search-help workflows, and transport changes.
• These areas need stronger regression coverage before multiple contributors start changing behavior in parallel.

Scope:

• Add tests for per-session routing and detach/owned-session cleanup.
• Add tests for policy decisions by tool class, transaction, and system override.
• Add w

Read the thread · 2026-03-26 · closed · 1 comment

Enhance sap_set_batch_fields with validation mode

Make sap_set_batch_fields better for real forms instead of adding a separate form-fill mega-tool.

Why:

• Batch field setting already exists.
• The missing capability is validation feedback and better handling of readonly fields.

Scope:

• Add validate mode to trigger Enter/validation after field entry.
• Add skip_readonly behavior with warnings.
• Return status-bar information and per-field validation failures/highlights.
• Keep the tool composable and predictable.

Acceptance criteria:

Read the thread · 2026-03-26 · closed · 1 comment

Add sap_handle_popup workflow tool

Add a focused popup workflow tool instead of forcing agents to manually inspect and react to modal dialogs every time.

Why:

• Popups are one of the biggest current failure points.
• The existing discovery tooling can already read popup content; the missing piece is a guided action surface.

Scope:

• Add a tool with operation modes such as read, confirm, cancel, and auto.
• Classify popup type (confirmation, error, info, input-required) when possible.
• Match buttons by visible text/tool

Read the thread · 2026-03-26 · closed · 1 comment

Add MCP prompts for core SAP workflows

Use MCP prompts to guide agents through the highest-friction SAP workflows without exploding tool count.

Why:

• Prompts are the cheapest way to improve agent behavior.
• This server already has enough primitives; guidance is the missing layer.

Scope:

• Add prompts for F4/search help.
• Add prompts for table pagination.
• Add prompts for SPRO/customizing tree navigation.
• Add prompts for multi-field form fill and validation.
• Update docs so clients know these prompts exist.

Acceptance criter

Read the thread · 2026-03-26 · closed · 1 comment

Add structured audit logging for mutating actions

Add structured audit logging for all write/destructive operations.

Why:

• Enterprise trust depends on being able to reconstruct what an agent tried to do.
• Security hardening is not enough without observability.

Scope:

• Emit structured events for mutating actions.
• Include tool name, target system/client, session identity, action target, result, and timing.
• Redact secrets and sensitive field values.
• Make log destination/configuration explicit.

Acceptance criteria:

• All mutating tools

Read the thread · 2026-03-26 · closed · 1 comment

Add YAML policy engine and migrate current transaction rules

Replace the current hardcoded blocklist/allowlist checks with a YAML-backed policy model.

Why:

• The current security controls are too limited for real SAP environments.
• We already classify tools as read/write/destructive.
• Policy-driven behavior is a major v0.2 goal.

Scope:

• Define a YAML policy format for defaults, roles, rules, and system overrides.
• Map existing tool annotations to policy classes.
• Preserve current blocked-transaction behavior as the default baseline.
• Support rea

Read the thread · 2026-03-26 · closed · 1 comment

Most recent

Add streamable HTTP transport for controlled local/team use

Add opt-in streamable-http transport while keeping stdio as the default local mode.

Why:

• Team and remote-client usage needs HTTP transport.
• SSE is legacy; streamable-http is the transport to target.
• This should build on the session-manager work, not bypass it.

Scope:

• Add CLI/config support for transport selection.
• Support stdio and streamable-http.
• Keep HTTP stateful for now.
• Default bind to localhost only.
• Document the transport mode clearly in README/client setup do

Read the thread · 2026-03-26 · closed · 1 comment

Refactor server state around a SessionManager

Replace the current module-level global controller/config pattern with explicit server state and per-client session tracking.

Why:

• streamable-http is not safe with the current shared globals.
• SAP GUI COM is stateful; tool calls from the same MCP session must route to the same SAP session binding.
• This is the architectural prerequisite for the rest of v0.2.

Scope:

• Introduce a SessionManager / managed-session layer.
• Keep stdio behavior backward compatible.
• Track ownership (`o

Read the thread · 2026-03-26 · closed · 1 comment

The remaining reports are on the project's issue tracker.