[changelog] [Added] rovo:mcp module now available in Preview

Open
#25 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
backend, tooling

Research direction

Start with the simulator's modules manifest parsing and validation, then inspect the existing Rovo action resolver path and its actionKey schema checks. Confirm the manifest accepts rovo:mcp with the manifest-reference properties, validates referenced actions, and determines whether MCP-tool invocation needs separate handling. Done means the supported MCP configuration is validated and its actions can be exercised through the simulator's Rovo path.

Written by the indexing model from the issue text.

Description

upstream-changelog

GUID: CHANGE-3400
pubDate: Fri, 14 Aug 2026 10:56:21 GMT
Category: Added

What's changing

The rovo:mcp module has progressed from Early Access (EAP) to Preview. It lets Forge apps expose Rovo actions as MCP tools that can be added to custom agents in Rovo Studio. Apps declaring rovo:mcp now appear under Connected Apps in Rovo Studio, making configured actions available as tools for custom agents. Existing EAP users need no changes; new users add the rovo:mcp module to the manifest and configure the actions to expose.

Docs:

Impact on forge-sim parity

This touches the manifest/modules surface. forge-sim already simulates Rovo actions (resolver invocation with actionKey validation against the action schema). Now that rovo:mcp is out of EAP-gating (we skipped it as CHANGE-3362 while it was EAP-only), we should:

  • Accept rovo:mcp in manifest validation (module key, required/optional properties per the manifest reference)
  • Decide whether the simulator should model the "actions exposed as MCP tools" wiring — at minimum, validate that actions referenced by rovo:mcp exist and are invocable via the existing Rovo action path
  • Simulator areas: modules (manifest parsing/validation), possibly resolver invocation if the MCP-tool invocation shape differs from plain Rovo action invocation

Link: https://developer.atlassian.com/platform/forge/changelog/#CHANGE-3400

Dominant language
TypeScript
Stars
5
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ryanackley/forge-sim

All issues in ryanackley/forge-sim

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.