Atlassian、MCPサーフェスを220ツールに拡大しOpenAIとの支出コミットメントを締結

Atlassianの再構築されたMCPサーバーは現在1日1,500万コールを処理し220以上のツールを公開。新たな支出コミットメントによりGPT-6 AstraがRovoのマルチモデル構成に加わるが、プラットフォームのモデル非依存姿勢は維持される。

公開日 更新日 5 分で読了 ✓ AI対応 共有

TL;DR — 3つの文

  • Atlassian's rebuilt MCP server handles more than 15 million calls per day and exposes 220-plus tools across Jira, Confluence, Bitbucket, Loom and Goals (S1).
  • A new "spend commitment" runs from Atlassian to OpenAI; Rovo remains multi-model and Astra is explicitly not the default (S1).
  • Governance features include OAuth 2.1 + PKCE, per-user permission enforcement, tiered read/write/destructive actions, DLP via Atlassian Guard and org-wide audit logs (S1).

引用元: key_takeaways (実フィールド、最大3件)。事実と分析は別々にラベル付けされています。

Atlassian、MCPサーフェスを220ツールに拡大しOpenAIとの支出コミットメントを締結Editorial cover for a component sourcing brief. Chip motif; headline "Atlassian、MCPサーフェスを220ツールに拡大しOpenAIとの支出コ". Reported key numbers: 220 -plus. 1 cited source. Static cover (no animation).Atlassian、MCPサーフェスを220ツールに拡大しOpenAIとの支出コREPORTED KEY NUMBERS220 -plus1 sourceXAIPART
Cover image generated from data already shown on this page: the category motif, the headline, and reported key numbers. No decorative illustration; no third-party image.

AIの回答から来ましたか — これが検証可能なオリジナルです

AIの要約は、主張の根拠を落としている可能性があります。元の予測、影響を受ける部品、すべての引用はこのページにあり、それぞれ出典まで追跡できます。

XAIPART予測

このブリーフには反証可能な予測が含まれています。

影響を受ける部品

この記事に一致するカタログ項目はありません。推測して一致させるのではなく、何も表示しません。

Reported by VentureBeat on . Summarized and analyzed by XAIPART Editorial.

What happened

Atlassian announced an expansion of its partnership with OpenAI, adding GPT-6 Astra and the GPT-5.6 series to its platform and Rovo AI, and connecting the Teamwork Graph to ChatGPT and Codex through a rebuilt Model Context Protocol server.S1 The arrangement includes a commercial commitment that an OpenAI representative described as "effectively a spend commitment" - Atlassian committing dollars to OpenAI models and technology, not the reverse.S1

Atlassian was explicit that GPT-6 Astra is not becoming Rovo's default model; Rovo routes requests dynamically across providers through an internal AI gateway that balances capability, speed and cost per task.S1 The company's own MCP announcement cites Anthropic's head of enterprise product, Scott White, calling Atlassian's MCP "one of the most-used enterprise MCP integrations on Claude," and Atlassian reports that its server's token-savings claims were measured on Claude models.S1

The rebuilt MCP server now handles more than 15 million calls per day, exposes 220-plus tools across Jira, Confluence, Bitbucket, Loom and Goals, and uses up to 25% fewer tokens on comparable Jira and Confluence work in internal testing.S1 Jira Service Management support is listed as coming soon.S1 Governance features include Atlassian-hosted endpoints secured with OAuth 2.1 and PKCE, per-user permission enforcement at query time, separated read, write and destructive risk tiers with confirmation gates on higher-risk steps, Data Loss Prevention via Atlassian Guard, domain and IP allowlists, per-scope controls and org-wide audit logging, including an option to disable writes entirely.S1

GPT-6 Astra pricing is listed at $10 per million input tokens and $50 per million output, with Rovo credit consumption scaling to the models and compute used per task.S1 OpenAI reports Astra reached the "Critical" cybersecurity threshold under its Preparedness Framework and scored 100% on one exploit benchmark, but the same safeguards can "slow, pause, or stop legitimate work," including defensive security tasks.S1 On data, Atlassian states only the data returned by an invoked MCP tool is sent to OpenAI, Astra supports Zero Data Retention for eligible API customers, enterprise access to Astra is off by default, and OpenAI is listed as a subprocessor that does not train on customer inputs or outputs.S1

Key numbers
MetricReported valueSource
MCP server daily callsMore than 15 million[S1]
MCP tool count exposed220-plus[S1]
Internal token reduction vs. prior serverUp to 25%[S1]
GPT-6 Astra input token price$10 per million tokens[S1]
GPT-6 Astra output token price$50 per million tokens[S1]
Spend-commitment counterpartyAtlassian to OpenAI (direction of payment)[S1]

Background timeline

  1. - Atlassian Intelligence launches, using OpenAI models from the start.S1
  2. - Original Atlassian-OpenAI partnership establishes the foundation later expanded.S1
  3. - Atlassian introduces its MCP integration for ChatGPT.S1
  4. - GPT-6 Astra ships as a standalone release.S1
  5. - Atlassian announces expanded OpenAI partnership and rebuilt MCP server, coinciding with Team '26 Europe.S1

XAIPART take

Technical impact

The MCP expansion turns Atlassian into a practical enterprise agent substrate: 220-plus tools across Jira, Confluence, Bitbucket, Loom and Goals, with per-user OAuth 2.1 + PKCE enforcement and tier-separated write/destructive actions that an admin can throttle or disable outright. For engineering teams already running Atlassian as a system of record, the 25% token reduction and the explicit DLP pipeline address the two biggest operational objections to long-running Rovo agents - cost and data egress - without forcing an all-in commitment to any single model family.XAIPART analysis

Market impact

Atlassian is paying OpenAI for priority model access while keeping Anthropic and other providers routed through the same gateway, which signals that model-portable enterprise infrastructure now has more commercial gravity than exclusive frontier-model deals. Buyers sourcing AI tooling should expect competing multi-model gateways from rival platforms, and any roadmap pinned solely to GPT-6 Astra will face the same benchmark ambiguity the source already flags on the Artificial Analysis Intelligence Index.XAIPART analysis

Action

Pilot the new MCP connection in a non-production Jira and Confluence tenant first, validate the OAuth 2.1 + PKCE enforcement and DLP labels against a representative prompt-injection scenario, and instrument Rovo credit usage per task before enabling Astra tier access. Lock the admin-console writes-disable switch and the per-scope read/write/search controls into your change-management baseline so that a model swap or an Astra safety pause cannot bypass your governance posture.XAIPART analysis

XAIPART Forecast

XAIPART expects that, within roughly two quarters of this announcement, at least one Atlassian-published Rovo reference architecture will demonstrate a third-party model performing greater than 50% of routed production traffic on the rebuilt MCP server, confirming the multi-model gateway as the durable layer rather than GPT-6 Astra. If, by , Atlassian has not disclosed a non-OpenAI model carrying more than 50% of Rovo traffic against this 15M-calls-per-day MCP baseline, this forecast is wrong.XAIPART analysis

Facts are as reported by the cited source. The design-in, sourcing and forward-looking statements above are XAIPART's analysis, not the source's claims. The contract size behind the "spend commitment," the precise scope of Astra Zero Data Retention eligibility, and whether the internal-Rovo model path matches the ChatGPT/Codex MCP retention terms are not disclosed by the source.

Corrections: none at publication. This brief will be updated with a timestamp if the source corrects its report.

Dated developments, extracted from this page's timeline (curated milestones = hollow markers).
Timeline of dated developmentsDated entries: 2023-04-01 2023 - Atlassian Intelligence laun…; 2023-01-01 - Original Atlassian-OpenAI partne…; 2025-12-01 2025 - Atlassian introduces its MC…; 2026-09-03 - GPT-6 Astra ships as a standalon…; 2026-10-06 - Atlassian announces expanded Ope….2023-04-012023 - Atlassian Intelligence laun…2023-01-01- Original Atlassian-OpenAI partne…2025-12-012025 - Atlassian introduces its MC…2026-09-03- GPT-6 Astra ships as a standalon…2026-10-06- Atlassian announces expanded Ope…

代替品とライフサイクル

登録済みの代替品 — カタログ範囲であり、市場ランキングではありません
部品関係ライフサイクル根拠
— 登録済みの代替品はありません データ不足 — 前身ラベルを表示するには match_type が必要です

「前身」および「代替」のラベルは、記録された一致タイプ、ライフサイクルステータス、またはソーステキストに基づく場合にのみ付与されます。一致が記録されていない場合、ラベルは表示されません。当社の掲載情報は市場の基準ではありません。

影響を受ける部品

カタログに一致するものはありません。 この記事は、現在XAIPARTに掲載されているどの部品にも該当しません。一致を推測することはなく、プレースホルダーのリストも表示しません。

次元別のコスト圧力

Source: FRED · Generated · reference output z and composite are algorithm outputs, not a fetch snapshot

Cost pressure by dimension — composite stateDiverging bars for three dimensions around a zero midpoint. Input Cost has no reading; Supply Demand z -1.4711, notable; Fx Energy z 0.2546, neutral. Composite index -9.1, band neutral.0Input costno readingSupply/demandz −1.4711 · notable46 dFX & energyz +0.2546 · neutral5 dcomposite −9.1 · neutral−100 · −40 · −15 · 0 · +15 · +40 · +100
Underlying values — copyable for verification.
DimensionFRED series IDUnitLagAs of
Input costPCOPPUSDM, PALUMUSDM, PNICKUSDMUSD/mt52 d
Supply/demandPCU334413334413, IPG3344Sindex(1982=100) / index(2017=100)46 d
FX & energyDEXCHUS, DCOILBRENTEU, DHHNGSPrate / USD/bbl / USD/MMBtu5 d

No free authoritative interface for: gold · silver · rare earth · polysilicon · lithium carbonate · market share — listed rather than approximated.

この記事の制作方法

プロセス証跡 — 取得、ソースの妥当性、モデル、ゲート
このブリーフの監査証跡
Source fetched VentureBeat · venturebeat.com · 8,210 chars
Source sanity (S1) ok — passed before any model call (no s1_ block recorded)
Model / prompt MiniMax-M3 · prompt Blog Agent - News Summary (v2.8-final) · 8,006 tokens · 33.4s · run completed
Gate verdict hold · 5/6 applicable checks passed · spec v2.9 · C10 ratio 0.010471 · C10 rounds 0
Time contract 7 <time datetime> values in this brief — 0 violations (+08:00 or date-only)

上記のすべての行はパイプラインによって生成されており、手作業で書かれたものではありません。

編集スコア

決定論的ゲートの結果 — 純粋なPHPで、判定にモデルは関与していません
ゲートスコアの内訳 6 件の該当チェックのうち、 5項目合格: 83 %. Hold items: C15 (four views + no restating) — sent to human review. Gate spec: v2.9 (S0 + S1 + C1–C20) · Source affinity (C20): 0.8343. 該当するチェックに合格 5 / 6 = 83% · 判定: hold Hold items: C15 (four views + no restating) — sent to human review Gate spec: v2.9 (S0 + S1 + C1–C20) · Source affinity (C20): 0.8343 公開の可否はゲートが決定します。独立監査スコアは助言にすぎません。

独立監査(助言目的、公開には影響しません): 51/100 · 評価 C — 詳細

誤りを見つけましたか? 誤りをお知らせください — 訂正は原文と併せて公開され、記録されます。記事を無断で編集することはありません。

コメント

最初のコメントを投稿しましょう。

情報源

  1. Atlassian deepens its OpenAI partnership while keeping its platform multi-model — https://venturebeat.com/orchestration/atlassian-deepens-its-openai-partnership-with-a-spend-commitment-but-its-platform-stays-firmly-multi-model · rss · 参照日

事実はS1/S2とマークされ、リンクされた出典まで追跡できます。ラベル付けされた箇所は 分析 はXAIPART独自の推論であり、報道された事実とは分けて維持されています。出典リンクは実際に参照され、次の指定は行いません: nofollow — 帰属表示は意図的なものです。