All issues

Allow running without a runtime backend when no MCP servers are hosted

#7978

· rubennati opened

on Sep 21, 2026

Existing vMCP profiles incorrectly show newly added MCP servers as enabled in As-is mode.

#7976

· sangee2004 opened

on Sep 19, 2026

Tool names change after adding a second MCP server to an existing vMCP.

#7975

· sangee2004 opened

on Sep 19, 2026

`Update Configuration` modal briefly appears when connecting to a preconfigured vMCP

#7974

· sangee2004 opened

on Sep 18, 2026

Default access policy for the PUP user registry exposes newly created MCP servers to all users

#7967

· sangee2004 opened

on Sep 17, 2026

vMCP component servers are incorrectly listed when configuring MCP access policies

#7966

· sangee2004 opened

on Sep 17, 2026

vMCP creation confirmation shows access control guidance to standard users.

#7965

· sangee2004 opened

on Sep 17, 2026

`Test vMCP` and `Connect` options are available to admins without access to the vMCP

#7964

· sangee2004 opened

on Sep 17, 2026

Profiles with all tools explicitly enabled are incorrectly created with `allowAllComponents`

#7961

· sangee2004 opened

on Sep 17, 2026

Disabling a vMCP tool fails when the tool is still referenced by profiles

#7960

· sangee2004 opened

on Sep 17, 2026

No way to add newly available tools from an updated vMCP server to existing/new profiles.

#7958

· sangee2004 opened

on Sep 17, 2026

`default` profile with allowAllComponents returns no tools after updating an MCP server when another profile has refined tools.

#7957

· sangee2004 opened

on Sep 17, 2026