The Forge Model Context Protocol (MCP) Server is now available in preview. This new remote service enables Forge app developers to leverage coding agents with up-to-date Atlassian Forge and Cloud documentation, including markdown-based guides, module catalogs, and manifest references. The Forge MCP Server also provides a search feature for Forge reference documentation and implementation patterns, streamlining Forge app development in AI-powered workflows.
How to Get Started
Feedback Welcome
This is a preview release, and your feedback is invaluable. Please share your experiences, suggestions, or issues in the comments below.
Cheers,
Prashant
2 Likes
Hi @PrashantBabber
Do we need to enroll for this preview? I tried integrating this in vscode but getting following error:
2025-10-22 12:31:15.334 [info] Connection state: Error 400 status connecting to http://mcp.atlassian.com/v1/forge/mcp as SSE: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Bad Request: No valid session ID provided"},"id":null}
I am on latest version of vscode:
Version: 1.105.1 (Universal)
Commit: 7d842fb85a0275a4a8e4d7e040d2625abbf7f084
Date: 2025-10-14T22:33:36.618Z
Electron: 37.6.0
ElectronBuildId: 12502201
Chromium: 138.0.7204.251
Node.js: 22.19.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0
Hello @SumitParakh ,
Thanks for the feedback. We have updated the url in the documentation. Here’s the latest endpoint → https://mcp.atlassian.com/v1/forge/mcp
3 Likes
Cool @PrashantBabber. I can use that now. Thank you for the quick update.
“Migrate Connect app to pure Forge app, make no mistakes”
Now this would probably be achievable if Atlassian behaved like a rational actor and did two things:
- Open source everything so when the AI models are trained they actually know wtf is going on with the Atlassian developer ecosystem. I don’t need you to accept PRs. Simply make the code public (+git history) so the models can consume it.
- Delay the ridiculously unrealistic Forge migration deadlines which are very obviously destroying any remaining trust and goodwill that developers have with Atlassian. If you delayed the migration by 18 months, the AI models will be so good by then that you will save 100s of 1000s of hours of wasted developer time.
1 Like
I can’t get the RovoDev IDE extension to connect to the forge-knowledge MCP.
My RovoDev is connected to the Atlassian-MCP-Server MCP (used to interact with my instance) but not to forge-knowledge.
At the same time, Cascade in my Windsurf is connected to both, and there’s a UX indicator showing that the connection is working — something the RovoDev extension is missing and that would be helpful to implement.
Here’s my user/.rovodev/mcp.json file, which is used by the RovoDev extension in Windsurf:
{
"servers": {
"forge-knowledge": {
"url": "https://mcp.atlassian.com/v1/forge/mcp"
},
"Atlassian-MCP-Server": {
"url": "https://mcp.atlassian.com/v1/sse"
}
},
"inputs": []
}
Here is my user/.codeium/windsurf mcp_config.json file used by Winsurf Cascade successfully:
{
"mcpServers": {
"forge-knowledge": {
"url": "https://mcp.atlassian.com/v1/forge/mcp"
},
"Atlassian-MCP-Server": {
"url": "https://mcp.atlassian.com/v1/sse"
}
}
there seems to be something preventing Rovo Dev connection to the forge-knowledge server.
Can you help?
thanks
I just tried to add the MCP server in my IntelliJ IDEA IDE, but I keep getting this error: Expected status code 200 but was 400
@PrashantBabber is there anything specific needed that I misted?
Hi @dusan.spaic - when you start Rovo Dev CLI, do you see the message, “Would you like to allow the use of the following third-party MCP server: url: https://mcp.atlassian.com/v1/forge/mcp ? Or do you get an error message?
Hi @markrekveld - are you using IntelliJ’s AI Assistant? If so, I noticed in their docs that they don’t yet support Streamable HTTP (HTTP + SSE) transport yet. See Model Context Protocol (MCP) | AI Assistant Documentation . They mention a workaround, but I haven’t tried it.
If you are using GitHub Copilot for IntelliJ, try adding "type": "http" to the configuration to ensure it uses the streamable HTTP transport. For example:
{
"servers": {
"Forge MCP": {
"url": "https://mcp.atlassian.com/v1/forge/mcp",
"type": "http"
}
},
"inputs": []
}
2 Likes
Thanks @BrendanBarlow the workaround seems to work with this configuration.
{
"mcpServers": {
"Force MCP": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://mcp.atlassian.com/v1/forge/mcp"
]
}
}
}
I say seems because the status is shown as ok listing some tools that can be used, but I also see these warnings/error
Is this to be expected because of the lack of direct IDEA support, or is there something else?
@markrekveld It isn’t expected from the Forge MCP server. Our tool names do match the pattern shown in the errors.
I’m no IntelliJ expert, but I’m wondering if the errors are due to the space in the server name, “Force MCP”. It looks like IntelliJ is constructing a qualified tool name that includes the server name. This is just a guess, though.
1 Like
You called it @BrendanBarlow I updated the name of the server to MCP_Force and wtched all the error disappear.
3 Likes
Hi @dusan ,
I’ve been having a little trouble with this myself, but for now have managed to make the connection work with this configuration:
{
"mcpServers": {
"forge-knowledge": {
"url": "https://mcp.atlassian.com/v1/forge/mcp",
"transport": "http"
}
}
}
There seems to be a bit of a contradiction between the URL which holds “https” and the transport which only holds “http” for now.
Anticipate this being cleared up? 
Justin
We’ve updated the documentation on our end (https://developer.atlassian.com/platform/forge/forge-mcp/#connecting-your-ide-to-the-forge-mcp-server) to include the correct settings. http is the correct value for both the transport parameter for the Rovo Dev CLI and for the type one is VS Code.
Thanks @JustinTownsend and all for pointing this out.
2 Likes
