[{"data":1,"prerenderedAt":1046},["ShallowReactive",2],{"post-en-antigravity-plugins-vs-mcp":3,"surround-en-blog\u002Fen\u002Fblog\u002Fantigravity-plugins-vs-mcp.md":1039},{"id":4,"title":5,"body":6,"canonical":325,"category":1020,"date":1021,"description":1022,"extension":1023,"image":1024,"meta":1025,"navigation":1026,"path":1027,"seo":1028,"slug":1029,"status":1030,"stem":1031,"tags":1032,"translationSlug":1029,"__hash__":1038},"blog\u002Fen\u002Fblog\u002Fantigravity-plugins-vs-mcp.md","Official Plugins vs. Custom MCP in Antigravity: Differences and Selection Guide (with Notion)",{"type":7,"value":8,"toc":1003},"minimark",[9,14,35,38,44,47,186,189,193,200,205,208,239,276,279,283,305,308,417,441,445,448,495,498,502,529,580,590,592,596,602,606,618,688,692,703,707,710,731,735,741,763,766,768,772,938,940,944,951,999],[10,11,13],"h2",{"id":12},"_1-background-and-bluf-bottom-line-up-front","1. Background and BLUF (Bottom Line Up Front)",[15,16,17,18,22,23,26,27,30,31,34],"p",{},"While auditing my local Antigravity configuration in ",[19,20,21],"code",{},"~\u002F.gemini\u002Fconfig\u002Fmcp_config.json"," today, I tested my existing Notion MCP setup and then noticed the official Notion plugin in the Antigravity Marketplace (",[19,24,25],{},"antigravity-plugins-partners\u002Fplugin\u002Fnotion","). Just like Chrome DevTools—which exists both as a standalone ",[19,28,29],{},"chrome-devtools-mcp"," and an official ",[19,32,33],{},"chrome-devtools-plugin","—Notion is available in both forms on the same machine.",[15,36,37],{},"After switching Notion from a standalone MCP entry to the plugin and testing both setups side by side, here is the takeaway:",[15,39,40],{},[41,42,43],"strong",{},"In Antigravity, a plugin is not a separate tool protocol. Under the hood it still runs an MCP server, but bundles workflow Skills, lifecycle management, and native remote connection settings on top. Use official or partner plugins for standard SaaS tools where workflow Skills help; use standalone or custom MCP entries for local scripts, custom CLI flags, or cross-client reuse. You can mix both across different services, but only keep one active per service.",[15,45,46],{},"Using Notion as the concrete example, the table below summarizes the key differences:",[48,49,50,70],"table",{},[51,52,53],"thead",{},[54,55,56,61,64],"tr",{},[57,58,60],"th",{"align":59},"left","Dimension",[57,62,63],{"align":59},"Antigravity Plugin (Notion Plugin)",[57,65,66,67,69],{"align":59},"Standalone \u002F Custom MCP (",[19,68,21],{},")",[71,72,73,93,114,134,153,170],"tbody",{},[54,74,75,81,87],{},[76,77,78],"td",{"align":59},[41,79,80],{},"What It Includes",[76,82,83,86],{"align":59},[41,84,85],{},"MCP Server + 12 Workflow Skills"," (meeting prep, weekly digests, spec-to-tasks, research docs, etc.)",[76,88,89,92],{"align":59},[41,90,91],{},"Tool Layer Only",": exposes raw API read\u002Fwrite and search tools without workflow instructions",[54,94,95,100,107],{},[76,96,97],{"align":59},[41,98,99],{},"Connection Transport",[76,101,102,103,106],{"align":59},"Native Streamable HTTP (",[19,104,105],{},"\"serverUrl\": \"https:\u002F\u002Fmcp.notion.com\u002Fmcp\"","), no local Node bridge needed",[76,108,109,110,113],{"align":59},"Often bridged via ",[19,111,112],{},"npx -y mcp-remote@latest"," (or Stdio launching a local script)",[54,115,116,121,124],{},[76,117,118],{"align":59},[41,119,120],{},"Setup & Lifecycle",[76,122,123],{"align":59},"Installed, updated, and hot-toggled from the Antigravity plugins UI without editing JSON",[76,125,126,127,130,131,69],{"align":59},"Managed manually in ",[19,128,129],{},"mcp_config.json"," (arguments, env vars, or ",[19,132,133],{},"\"disabled\": true",[54,135,136,141,147],{},[76,137,138],{"align":59},[41,139,140],{},"Tool Namespace",[76,142,143,144,69],{"align":59},"Prefixed with the plugin name (verified runtime server name: ",[19,145,146],{},"notion_notion",[76,148,149,150,69],{"align":59},"Uses the config key directly (e.g., ",[19,151,152],{},"notion",[54,154,155,160,163],{},[76,156,157],{"align":59},[41,158,159],{},"Cross-Client Reuse",[76,161,162],{"align":59},"Antigravity ecosystem only",[76,164,165,166,169],{"align":59},"Portable JSON structure across ",[19,167,168],{},"antigravity-cli",", Claude Code, Codex, and other MCP clients",[54,171,172,177,183],{},[76,173,174],{"align":59},[41,175,176],{},"Remote Plan Limits",[76,178,179,182],{"align":59},[41,180,181],{},"Bound to your Notion plan","; switching to the plugin unlocks nothing extra",[76,184,185],{"align":59},"Same—enforced entirely by the remote account tier",[187,188],"hr",{},[10,190,192],{"id":191},"_2-under-the-hood-how-plugins-and-standalone-mcp-differ","2. Under the Hood: How Plugins and Standalone MCP Differ",[15,194,195,196,199],{},"It is easy to assume that a plugin uses a proprietary built-in API while MCP is an external protocol. Checking the local plugin directory and Antigravity's customization docs shows they are not competing protocols—the real difference is ",[41,197,198],{},"a packaged bundle vs. a bare server definition",".",[201,202,204],"h3",{"id":203},"_21-a-plugin-is-a-bundle-mcp-is-just-one-layer-inside-it","2.1 A Plugin Is a Bundle; MCP Is Just One Layer Inside It",[15,206,207],{},"In Antigravity's customization system, a Plugin is an installable unit that toggles together and can hold four components:",[209,210,211,218,223,229],"ul",{},[212,213,214,217],"li",{},[19,215,216],{},"plugin.json",": manifest metadata (name, version, author, repository);",[212,219,220,222],{},[19,221,129],{},": the MCP server definition shipped with the plugin;",[212,224,225,228],{},[19,226,227],{},"skills\u002F",": step-by-step runbooks teaching the agent how to use those tools effectively;",[212,230,231,232,235,236,199],{},"Optional ",[19,233,234],{},"rules\u002FAGENTS.md"," and ",[19,237,238],{},"hooks.json",[15,240,241,242,245,246,248,249,251,252,255,256,259,260,259,263,259,266,259,269,272,273,199],{},"Inspecting my installed Notion plugin at ",[19,243,244],{},"~\u002F.gemini\u002Fconfig\u002Fplugins\u002Fnotion\u002F"," (published by Notion Labs), its ",[19,247,129],{}," is just three lines, while its ",[19,250,227],{}," directory ships ",[41,253,254],{},"12 workflow Skills",", including ",[19,257,258],{},"notion-setup",", ",[19,261,262],{},"notion-meeting-prep",[19,264,265],{},"notion-research-documentation",[19,267,268],{},"notion-weekly-project-digest",[19,270,271],{},"notion-database-designer",", and ",[19,274,275],{},"notion-spec-to-implementation",[15,277,278],{},"With a standalone MCP setup, the agent only gets raw page and database operations. With the plugin, it also gets standardized playbooks for turning specs into task databases or drafting weekly digests.",[201,280,282],{"id":281},"_22-transport-and-maintenance-native-streamable-http-vs-local-bridge","2.2 Transport and Maintenance: Native Streamable HTTP vs. Local Bridge",[15,284,285,286,289,290,293,294,297,298,301,302,199],{},"Antigravity supports two MCP transports: ",[41,287,288],{},"Stdio"," (spawning a local binary or script) and ",[41,291,292],{},"Streamable HTTP"," (connecting directly to a remote ",[19,295,296],{},"url"," \u002F ",[19,299,300],{},"serverUrl","). Legacy HTTP+SSE (spec 2024-11-05) is not supported directly and requires a Stdio bridge such as ",[19,303,304],{},"mcp-remote",[15,306,307],{},"Comparing my two local Notion definitions makes the difference clear:",[209,309,310,359],{},[212,311,312,315,316,318,319,354,355,358],{},[41,313,314],{},"Standalone config"," (",[19,317,21],{},"):\n",[320,321,326],"pre",{"className":322,"code":323,"language":324,"meta":325,"style":325},"language-json shiki shiki-themes github-dark","\"notion\": {\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"mcp-remote@latest\", \"https:\u002F\u002Fmcp.notion.com\u002Fmcp\"]\n}\n","json","",[19,327,328,336,342,348],{"__ignoreMap":325},[329,330,333],"span",{"class":331,"line":332},"line",1,[329,334,335],{},"\"notion\": {\n",[329,337,339],{"class":331,"line":338},2,[329,340,341],{},"  \"command\": \"npx\",\n",[329,343,345],{"class":331,"line":344},3,[329,346,347],{},"  \"args\": [\"-y\", \"mcp-remote@latest\", \"https:\u002F\u002Fmcp.notion.com\u002Fmcp\"]\n",[329,349,351],{"class":331,"line":350},4,[329,352,353],{},"}\n","\nEvery launch spawns a local ",[19,356,357],{},"npx"," bridge process, which depends on the local Node environment.",[212,360,361,315,364,318,367,409,410,412,413,416],{},[41,362,363],{},"Plugin-bundled config",[19,365,366],{},"~\u002F.gemini\u002Fconfig\u002Fplugins\u002Fnotion\u002Fmcp_config.json",[320,368,370],{"className":322,"code":369,"language":324,"meta":325,"style":325},"{\n  \"mcpServers\": {\n    \"notion\": {\n      \"serverUrl\": \"https:\u002F\u002Fmcp.notion.com\u002Fmcp\"\n    }\n  }\n}\n",[19,371,372,377,382,387,392,398,404],{"__ignoreMap":325},[329,373,374],{"class":331,"line":332},[329,375,376],{},"{\n",[329,378,379],{"class":331,"line":338},[329,380,381],{},"  \"mcpServers\": {\n",[329,383,384],{"class":331,"line":344},[329,385,386],{},"    \"notion\": {\n",[329,388,389],{"class":331,"line":350},[329,390,391],{},"      \"serverUrl\": \"https:\u002F\u002Fmcp.notion.com\u002Fmcp\"\n",[329,393,395],{"class":331,"line":394},5,[329,396,397],{},"    }\n",[329,399,401],{"class":331,"line":400},6,[329,402,403],{},"  }\n",[329,405,407],{"class":331,"line":406},7,[329,408,353],{},"\nThis uses native remote ",[19,411,300],{}," directly, eliminating the local ",[19,414,415],{},"npx mcp-remote"," bridge and letting the Marketplace handle updates.",[15,418,419,420,423,424,427,428,430,431,434,435,438,439,199],{},"On the flip side, standalone MCP excels whenever you need ",[41,421,422],{},"full control over local commands and flags",". For example, I run a custom local Gmail MCP by launching a local Python script with ",[19,425,426],{},"uv"," over Stdio, and I switched ",[19,429,29],{}," in my main config from ",[19,432,433],{},"--isolated"," to ",[19,436,437],{},"--autoConnect"," so it attaches to my logged-in Chrome browser. Custom scripts and bespoke flags belong directly in ",[19,440,129],{},[201,442,444],{"id":443},"_23-cross-client-config-boundaries","2.3 Cross-Client Config Boundaries",[15,446,447],{},"Checking configurations across clients on the same machine shows that each reads its own file:",[209,449,450,462,470,483],{},[212,451,452,455,456,458,459,69],{},[41,453,454],{},"Main Antigravity config",": ",[19,457,21],{}," (with permission grants in ",[19,460,461],{},"~\u002F.gemini\u002Fconfig\u002Fconfig.json",[212,463,464,455,467],{},[41,465,466],{},"Antigravity CLI",[19,468,469],{},"~\u002F.gemini\u002Fantigravity-cli\u002Fmcp_config.json",[212,471,472,475,476,479,480],{},[41,473,474],{},"Claude Code",": top-level ",[19,477,478],{},"mcpServers"," in ",[19,481,482],{},"~\u002F.claude.json",[212,484,485,455,488,491,492],{},[41,486,487],{},"Codex",[19,489,490],{},"[mcp_servers.*]"," blocks in ",[19,493,494],{},"~\u002F.codex\u002Fconfig.toml",[15,496,497],{},"Plugins stay inside Antigravity, whereas standalone MCP commands and arguments transfer directly across clients.",[201,499,501],{"id":500},"_24-remote-plan-restrictions-stay-identical","2.4 Remote Plan Restrictions Stay Identical",[15,503,504,505,508,509,259,512,259,515,259,518,272,521,524,525,528],{},"Before switching, I called ",[19,506,507],{},"notion-get-tool-access"," on the standalone Notion MCP. On a personal\u002Ffree Notion plan, core tools such as ",[19,510,511],{},"fetch",[19,513,514],{},"create_pages",[19,516,517],{},"update_page",[19,519,520],{},"list_recent_pages",[19,522,523],{},"create_comment"," are ",[19,526,527],{},"available",", while server-side tier limits still apply:",[209,530,531,541,560],{},[212,532,533,536,537,540],{},[19,534,535],{},"query_data_sources"," is marked ",[19,538,539],{},"available_with_limit",";",[212,542,543,259,546,259,549,552,553,556,557,540],{},[19,544,545],{},"query_multiple_data_sources",[19,547,548],{},"query_meeting_notes",[19,550,551],{},"connector_search",", comment edit\u002Fdelete\u002Freactions, and suggested-edit tools return ",[19,554,555],{},"plan_required"," or ",[19,558,559],{},"full_version_required",[212,561,562,565,566,259,569,259,572,575,576,579],{},[19,563,564],{},"search"," works, but parameters like ",[19,567,568],{},"filters.edited_by_user_ids",[19,570,571],{},"filters.last_edited_date_range",[19,573,574],{},"filters.title_only",", and non-relevance ",[19,577,578],{},"sort"," require Business or Enterprise.",[15,581,582,583,586,587,199],{},"Because both setups hit ",[19,584,585],{},"https:\u002F\u002Fmcp.notion.com\u002Fmcp"," with the same Notion account, ",[41,588,589],{},"switching to the plugin does not bypass plan restrictions",[187,591],{},[10,593,595],{"id":594},"_3-step-by-step-migration-switching-notion-from-standalone-mcp-to-the-plugin","3. Step-by-Step Migration: Switching Notion from Standalone MCP to the Plugin",[15,597,598,599,601],{},"If you already configured Notion manually in ",[19,600,129],{}," and want to switch cleanly without loading duplicate tools, follow these four steps.",[201,603,605],{"id":604},"step-1-disable-the-existing-standalone-mcp-entry","Step 1: Disable the Existing Standalone MCP Entry",[15,607,608,609,611,612,434,614,617],{},"Open ",[19,610,21],{}," and add ",[19,613,133],{},[19,615,616],{},"\"notion\""," (disabling is safer than deleting if you ever want to roll back):",[320,619,621],{"className":322,"code":620,"language":324,"meta":325,"style":325},"{\n  \"mcpServers\": {\n    \"notion\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"mcp-remote@latest\",\n        \"https:\u002F\u002Fmcp.notion.com\u002Fmcp\"\n      ],\n      \"disabled\": true\n    }\n  }\n}\n",[19,622,623,627,631,635,640,645,650,655,661,667,673,678,683],{"__ignoreMap":325},[329,624,625],{"class":331,"line":332},[329,626,376],{},[329,628,629],{"class":331,"line":338},[329,630,381],{},[329,632,633],{"class":331,"line":344},[329,634,386],{},[329,636,637],{"class":331,"line":350},[329,638,639],{},"      \"command\": \"npx\",\n",[329,641,642],{"class":331,"line":394},[329,643,644],{},"      \"args\": [\n",[329,646,647],{"class":331,"line":400},[329,648,649],{},"        \"-y\",\n",[329,651,652],{"class":331,"line":406},[329,653,654],{},"        \"mcp-remote@latest\",\n",[329,656,658],{"class":331,"line":657},8,[329,659,660],{},"        \"https:\u002F\u002Fmcp.notion.com\u002Fmcp\"\n",[329,662,664],{"class":331,"line":663},9,[329,665,666],{},"      ],\n",[329,668,670],{"class":331,"line":669},10,[329,671,672],{},"      \"disabled\": true\n",[329,674,676],{"class":331,"line":675},11,[329,677,397],{},[329,679,681],{"class":331,"line":680},12,[329,682,403],{},[329,684,686],{"class":331,"line":685},13,[329,687,353],{},[201,689,691],{"id":690},"step-2-install-and-enable-the-notion-plugin-from-the-marketplace","Step 2: Install and Enable the Notion Plugin from the Marketplace",[15,693,694,695,697,698,700,701,199],{},"Search for and install the Notion plugin (",[19,696,25],{},") in Antigravity. It installs into ",[19,699,244],{}," without requiring manual edits to ",[19,702,461],{},[201,704,706],{"id":705},"step-3-verify-clean-handover-in-a-new-turn","Step 3: Verify Clean Handover in a New Turn",[15,708,709],{},"Start a new session and confirm two things:",[711,712,713,719],"ol",{},[212,714,715,716,718],{},"The old ",[19,717,152],{}," MCP tool group is gone—no duplicate tool definitions are injected;",[212,720,721,722,726,727,730],{},"The plugin's server appears under the ",[41,723,724],{},[19,725,146],{}," namespace, alongside the 12 bundled ",[19,728,729],{},"notion-*"," Skills.",[201,732,734],{"id":733},"step-4-run-read-only-probes-to-confirm-connectivity","Step 4: Run Read-Only Probes to Confirm Connectivity",[15,736,737,738,740],{},"Test ",[19,739,146],{}," with two read-only calls:",[711,742,743,754],{},[212,744,745,746,749,750,753],{},"Call ",[19,747,748],{},"notion-get-self"," with ",[19,751,752],{},"{}"," to confirm the active workspace and authenticated user;",[212,755,745,756,749,759,762],{},[19,757,758],{},"notion-list-recent-pages",[19,760,761],{},"{\"limit\": 3}"," to confirm page and database retrieval works.",[15,764,765],{},"If both succeed, your OAuth session and plugin connection are ready.",[187,767],{},[10,769,771],{"id":770},"_4-four-practical-gotchas-from-testing","4. Four Practical Gotchas from Testing",[711,773,774,807,856,904],{},[212,775,776,779],{},[41,777,778],{},"Running Both at Once Doubles Context Overhead",[209,780,781,795],{},[212,782,783,786,787,789,790,235,792,794],{},[41,784,785],{},"Symptom",": Enabling the Notion plugin without disabling ",[19,788,129],{}," exposes both ",[19,791,152],{},[19,793,146],{},", injecting dozens of near-identical tool schemas into the prompt.",[212,796,797,800,801,803,804,806],{},[41,798,799],{},"Fix",": Strictly pick one per service. Set ",[19,802,133],{}," (or remove the old entry) in ",[19,805,129],{}," immediately after enabling the plugin.",[212,808,809,812],{},[41,810,811],{},"Previously \"Always Allowed\" Actions Prompt for Approval Again",[209,813,814,826,847],{},[212,815,816,818,819,556,822,825],{},[41,817,785],{},": Even though you previously approved ",[19,820,821],{},"notion-fetch",[19,823,824],{},"notion-update-page",", switching to the plugin triggers confirmation prompts again.",[212,827,828,831,832,315,834,837,838,235,841,844,845,199],{},[41,829,830],{},"Cause",": Existing grants in ",[19,833,461],{},[19,835,836],{},"userSettings.globalPermissionGrants.allow",") are keyed to ",[19,839,840],{},"mcp(notion\u002Fnotion-fetch)",[19,842,843],{},"mcp(notion\u002Fnotion-update-page)",", whereas the plugin exposes tools under ",[19,846,146],{},[212,848,849,851,852,855],{},[41,850,799],{},": Do not hand-edit ",[19,853,854],{},"config.json","; simply re-approve once when prompted under the new namespace (and optionally clean up stale entries later).",[212,857,858,863],{},[41,859,860,861],{},"Tools Work in the Desktop App but Differ in ",[19,862,168],{},[209,864,865,872,899],{},[212,866,867,869,870,199],{},[41,868,785],{},": A local server available in the main Antigravity client is missing or behaves differently when running ",[19,871,168],{},[212,873,874,455,876,235,878,880,881,884,885,749,888,890,891,893,894,749,896,898],{},[41,875,830],{},[19,877,21],{},[19,879,469],{}," are separate files. On my machine, the main config includes a local ",[19,882,883],{},"gmail"," script and runs ",[19,886,887],{},"chrome-devtools",[19,889,437],{},", while the CLI config omits ",[19,892,883],{},", runs ",[19,895,887],{},[19,897,433],{},", and adds two CLI-only servers.",[212,900,901,903],{},[41,902,799],{},": Always inspect both files separately when debugging discrepancies between desktop and CLI runs.",[212,905,906,909],{},[41,907,908],{},"Meeting Notes or Connector Search Still Fail After Switching to the Plugin",[209,910,911,920,930],{},[212,912,913,455,915,556,917,919],{},[41,914,785],{},[19,916,548],{},[19,918,551],{}," remains unavailable even with the official Notion plugin active.",[212,921,922,924,925,556,927,929],{},[41,923,830],{},": These tools return ",[19,926,555],{},[19,928,559],{}," based on your Notion workspace tier, not your local MCP setup.",[212,931,932,934,935,937],{},[41,933,799],{},": Run ",[19,936,507],{}," once to inspect the exact capability matrix for your account before debugging local configs.",[187,939],{},[10,941,943],{"id":942},"_5-summary-and-when-to-use-which","5. Summary and When to Use Which",[15,945,946,947,950],{},"Based on these tests, a ",[41,948,949],{},"hybrid per-service strategy"," works best in Antigravity:",[209,952,953,976],{},[212,954,955,958,959],{},[41,956,957],{},"Choose Official \u002F Marketplace Plugins when",":",[209,960,961,964,967],{},[212,962,963],{},"You are connecting standard services with maintained plugins (such as Notion, Canva, or Chrome DevTools);",[212,965,966],{},"You want the bundled workflow Skills (meeting prep, weekly project digests, spec-to-task breakdowns);",[212,968,969,970,972,973,975],{},"You prefer one-click UI toggles, managed updates, and native ",[19,971,300],{}," connections without maintaining local ",[19,974,415],{}," processes.",[212,977,978,958,981],{},[41,979,980],{},"Choose Standalone \u002F Custom MCP when",[209,982,983,986,992],{},[212,984,985],{},"You are running private local scripts or internal services (such as a custom Python or Node MCP server);",[212,987,988,989,991],{},"You need custom CLI flags (headless vs. isolated vs. ",[19,990,437],{}," browser attachment);",[212,993,994,995,998],{},"You only need Notion as a raw data pipe with existing ",[19,996,997],{},"mcp(\u003Cname>\u002F...)"," whitelist rules untouched, or you want identical MCP definitions across multiple AI clients.",[1000,1001,1002],"style",{},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"title":325,"searchDepth":338,"depth":338,"links":1004},[1005,1006,1012,1018,1019],{"id":12,"depth":338,"text":13},{"id":191,"depth":338,"text":192,"children":1007},[1008,1009,1010,1011],{"id":203,"depth":344,"text":204},{"id":281,"depth":344,"text":282},{"id":443,"depth":344,"text":444},{"id":500,"depth":344,"text":501},{"id":594,"depth":338,"text":595,"children":1013},[1014,1015,1016,1017],{"id":604,"depth":344,"text":605},{"id":690,"depth":344,"text":691},{"id":705,"depth":344,"text":706},{"id":733,"depth":344,"text":734},{"id":770,"depth":338,"text":771},{"id":942,"depth":338,"text":943},"coder","2026-11-16","Comparing Antigravity plugins and standalone MCP servers using Notion as an example, covering packaging, transport, migration steps, pitfalls, and selection.","md",null,{},true,"\u002Fen\u002Fblog\u002Fantigravity-plugins-vs-mcp",{"title":5,"description":1022},"antigravity-plugins-vs-mcp","publish","en\u002Fblog\u002Fantigravity-plugins-vs-mcp",[1033,1034,1035,1036,1037],"Antigravity","MCP","Notion","Plugin","Agent","GjljBEQaG1S_tAv9WAAXopsRzbbF79M9tWfjhIzjFGY",[1024,1040],{"title":1041,"path":1042,"stem":1043,"slug":1044,"date":1045,"children":-1},"Zero-DB Traditional Chinese Conversion for Moodle with OpenCC (and How to Bypass RequireJS Pitfalls)","\u002Fen\u002Fblog\u002Fmoodle-opencc-traditional-chinese","en\u002Fblog\u002Fmoodle-opencc-traditional-chinese","moodle-opencc-traditional-chinese","2026-11-09",1794797297192]