Context:
We use Aha!'s official remote MCP server to let our Claude-based tooling read and write Aha! records on behalf of our Product Managers reading Features/Requirements with custom fields, and creating/updating records and comments via manage_record/add_comment.
The gap:
We want to help PMs avoid forgetting the one manual step in our Aha!↔Jira workflow: clicking Integrations → Send to [integration] on a Feature to create its linked Jira Epic. We found that Aha!'s REST API already supports this programmatically. However, this action isn't exposed as a callable tool on the MCP server itself.
The ask:
Could the Aha! MCP server add a tool, e.g. send_record_to_integration(record_id, integration_id), that wraps this same endpoint, scoped to the same OAuth permissions the connector already enforces for the calling user? This would let us detect that a Feature hasn't been sent to Jira yet and offer to do it in the same flow, rather than just telling the PM to go click the button manually.