Infosec teams need visibility into who has connected to the MCP server and which accounts have been used for those connections.
Today, an employee could potentially connect their own LLM to Aha! through MCP, but there is not an easy way to inspect or report on this activity.
Administrators need a report or audit view showing which users have authenticated to the MCP server.
They also need visibility into which credentials or accounts were used for MCP connections.
If available, they need to know which external LLM or MCP client was used for each connection.
Create a report or admin view in Aha! that lists MCP connections by user/account.
Include connection metadata useful for security review, such as first seen, last seen, connection status, and client/provider details when available.
Support infosec review of unauthorized or risky external AI connections.
As MCP is a entry point into potentially, very sensitive data, it would also be prudent to email Aha account admins when a new MCP connection is made.