What is the challenge?
The Aha! Roadmaps MCP server supports create and update actions, but reviewers and viewers cannot use these actions for work their existing permissions allow.
What is the impact?
Reviewers and viewers must leave their connected AI tools to complete permitted actions in Aha! Roadmaps.
Describe your idea.
Extend MCP create and update access to reviewers and viewers for actions permitted by their existing roles.
Apply the same record and workspace permissions through MCP as in Aha! Roadmaps, and retain administrator controls over MCP access.
Keep actions outside each user's permissions unavailable.
Will this also allow for the ability to do a proxy vote through the MCP? this is currently restricted, and is very limiting for our use case where internal users add proxy votes on behalf of our customers.