[{"data":1,"prerenderedAt":1050},["ShallowReactive",2],{"post-zh-antigravity-plugins-vs-mcp":3,"surround-zh-blog\u002Fzh\u002Fblog\u002Fantigravity-plugins-vs-mcp.md":1043},{"id":4,"title":5,"body":6,"canonical":320,"category":1024,"date":1025,"description":1026,"extension":1027,"image":1028,"meta":1029,"navigation":1030,"path":1031,"seo":1032,"slug":1033,"status":1034,"stem":1035,"tags":1036,"translationSlug":1033,"__hash__":1042},"blog\u002Fzh\u002Fblog\u002Fantigravity-plugins-vs-mcp.md","Antigravity 里装官方插件还是自建 MCP？以 Notion 为例拆解异同与选型",{"type":7,"value":8,"toc":1007},"minimark",[9,14,35,38,44,47,186,189,193,196,201,204,236,270,273,277,300,303,412,437,441,444,489,492,496,523,580,590,592,596,602,606,619,689,693,704,708,711,732,736,742,764,767,769,773,950,952,956,962,1003],[10,11,13],"h2",{"id":12},"_1-起因与结论先行","1. 起因与结论先行",[15,16,17,18,22,23,26,27,30,31,34],"p",{},"今天整理本机 Antigravity 的 ",[19,20,21],"code",{},"~\u002F.gemini\u002Fconfig\u002Fmcp_config.json"," 时，我顺手测了一下配置在里面的 Notion MCP，接着又在插件市场里翻到了 Notion 官方出品的插件（",[19,24,25],{},"antigravity-plugins-partners\u002Fplugin\u002Fnotion","）。同一台机器上，既有手配的 Notion MCP，又有现成的 Notion 插件，就像 Chrome DevTools 也同时存在独立 ",[19,28,29],{},"chrome-devtools-mcp"," 和官方 ",[19,32,33],{},"chrome-devtools-plugin"," 一样。",[15,36,37],{},"实际把 Notion 从独立 MCP 切换到插件并逐项测试之后，省流结论如下：",[15,39,40],{},[41,42,43],"strong",{},"在 Antigravity 中，插件并不是另一套工具协议，它底层依然挂载 MCP Server，但额外打包了配套 Skills、生命周期托管和原生连接配置。选型上，标准 SaaS 且需要场景工作流时优先用官方\u002F合作插件；本地自建脚本、需要精细定制启动参数或跨客户端复用时，用独立 MCP；两者可按服务混用，但同一个外部服务只留一个，不要同时开启。",[15,45,46],{},"以 Notion 为例，两者的核心差异可以直接对照下面这张表：",[48,49,50,70],"table",{},[51,52,53],"thead",{},[54,55,56,61,64],"tr",{},[57,58,60],"th",{"align":59},"left","对比维度",[57,62,63],{"align":59},"Antigravity 插件（Notion 插件）",[57,65,66,67,69],{"align":59},"独立 \u002F 自建 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],{},"包含内容",[76,82,83,86],{"align":59},[41,84,85],{},"MCP Server + 12 个场景化 Skills","（含会议准备、项目周报、Spec 转任务、调研文档等）",[76,88,89,92],{"align":59},[41,90,91],{},"纯工具层（Tools）","，只提供底层 API 读写与检索能力，不带流程规范",[54,94,95,100,107],{},[76,96,97],{"align":59},[41,98,99],{},"连接方式",[76,101,102,103,106],{"align":59},"直接使用原生 Streamable HTTP（",[19,104,105],{},"\"serverUrl\": \"https:\u002F\u002Fmcp.notion.com\u002Fmcp\"","），不依赖本地 Node",[76,108,109,110,113],{"align":59},"常见需要 ",[19,111,112],{},"npx -y mcp-remote@latest"," 桥接（或用 Stdio 拉起本地自写脚本）",[54,115,116,121,124],{},[76,117,118],{"align":59},[41,119,120],{},"配置与启停",[76,122,123],{"align":59},"Antigravity 插件面板统一安装、更新与热切换，无需手改 JSON",[76,125,126,127,130,131],{"align":59},"手动维护 ",[19,128,129],{},"mcp_config.json","，增删改参数或加 ",[19,132,133],{},"\"disabled\": true",[54,135,136,141,147],{},[76,137,138],{"align":59},[41,139,140],{},"工具命名空间",[76,142,143,144,69],{"align":59},"带插件前缀（实测暴露服务名为 ",[19,145,146],{},"notion_notion",[76,148,149,150,69],{"align":59},"直接使用配置里的 key（如 ",[19,151,152],{},"notion",[54,154,155,160,163],{},[76,156,157],{"align":59},[41,158,159],{},"跨客户端复用",[76,161,162],{"align":59},"仅在 Antigravity 体系内生效",[76,164,165,166,169],{"align":59},"同一套 JSON 结构可迁移到 ",[19,167,168],{},"antigravity-cli","、Claude Code、Codex 等客户端",[54,171,172,177,183],{},[76,173,174],{"align":59},[41,175,176],{},"远端权限边界",[76,178,179,182],{"align":59},[41,180,181],{},"取决于 Notion 账号套餐","，换插件不会解锁更高阶接口",[76,184,185],{"align":59},"同左，完全取决于账号本身",[187,188],"hr",{},[10,190,192],{"id":191},"_2-拆开看插件和独立-mcp-在机制上差在哪","2. 拆开看：插件和独立 MCP 在机制上差在哪？",[15,194,195],{},"很多人一开始会误以为“插件 = 官方原生内置接口，MCP = 第三方协议”。去本地目录翻一下插件和定制系统的文档，就会发现它们不是替代关系，而是**“打包方式”和“纯连接配置”**的区别。",[197,198,200],"h3",{"id":199},"_21-插件是一个组合包mcp-只是其中一块","2.1 插件是一个组合包，MCP 只是其中一块",[15,202,203],{},"按照 Antigravity 的定制体系设计，Plugin 是一个可整体启停的分发单元（Bundle），标准目录可以同时包含四类东西：",[205,206,207,214,219,225],"ul",{},[208,209,210,213],"li",{},[19,211,212],{},"plugin.json","：插件清单（名称、版本、作者、仓库等元数据）；",[208,215,216,218],{},[19,217,129],{},"：插件自带的 MCP Server 配置；",[208,220,221,224],{},[19,222,223],{},"skills\u002F","：教 Agent 怎么按标准套路使用这些工具的工作流指南；",[208,226,227,228,231,232,235],{},"可选的 ",[19,229,230],{},"rules\u002FAGENTS.md"," 和 ",[19,233,234],{},"hooks.json","。",[15,237,238,239,242,243,245,246,249,250,253,254,253,257,253,260,253,263,253,266,269],{},"以我安装的 Notion 插件（位于 ",[19,240,241],{},"~\u002F.gemini\u002Fconfig\u002Fplugins\u002Fnotion\u002F","）为例，它由 Notion Labs 发布，目录里除了一个仅 3 行的 ",[19,244,129],{},"，还附带了 ",[41,247,248],{},"12 个场景化 Skill","：",[19,251,252],{},"notion-setup","、",[19,255,256],{},"notion-meeting-prep",[19,258,259],{},"notion-research-documentation",[19,261,262],{},"notion-weekly-project-digest",[19,264,265],{},"notion-database-designer",[19,267,268],{},"notion-spec-to-implementation"," 等。",[15,271,272],{},"也就是说，如果只配独立 MCP，Agent 拿到的是一把“能读写页面的锤子”；装上插件后，Agent 还同时拿到了“怎么写周报、怎么把 Spec 拆成任务数据库”的操作手册。",[197,274,276],{"id":275},"_22-传输协议与维护成本原生-streamable-http-vs-本地桥接","2.2 传输协议与维护成本：原生 Streamable HTTP vs 本地桥接",[15,278,279,280,283,284,287,288,291,292,295,296,299],{},"Antigravity 目前支持两种 MCP 传输机制：",[41,281,282],{},"Stdio","（拉起本地可执行文件或脚本）和 ",[41,285,286],{},"Streamable HTTP","（直接连远端 ",[19,289,290],{},"url"," \u002F ",[19,293,294],{},"serverUrl","），不支持旧版 HTTP+SSE（2024-11-05 规范），遇到只支持旧 SSE 的服务端时必须套一层 ",[19,297,298],{},"mcp-remote"," 做 Stdio 桥接。",[15,301,302],{},"对比我本机的两份 Notion 配置，差异很直观：",[205,304,305,354],{},[208,306,307,310,311,313,314,349,350,353],{},[41,308,309],{},"独立手配版本","（",[19,312,21],{},"）：\n",[315,316,321],"pre",{"className":317,"code":318,"language":319,"meta":320,"style":320},"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,322,323,331,337,343],{"__ignoreMap":320},[324,325,328],"span",{"class":326,"line":327},"line",1,[324,329,330],{},"\"notion\": {\n",[324,332,334],{"class":326,"line":333},2,[324,335,336],{},"  \"command\": \"npx\",\n",[324,338,340],{"class":326,"line":339},3,[324,341,342],{},"  \"args\": [\"-y\", \"mcp-remote@latest\", \"https:\u002F\u002Fmcp.notion.com\u002Fmcp\"]\n",[324,344,346],{"class":326,"line":345},4,[324,347,348],{},"}\n","\n每次启动都要靠本地 ",[19,351,352],{},"npx"," 拉起一个桥接进程，依赖本机 Node 环境。",[208,355,356,310,359,313,362,404,405,407,408,411],{},[41,357,358],{},"Notion 插件内置版本",[19,360,361],{},"~\u002F.gemini\u002Fconfig\u002Fplugins\u002Fnotion\u002Fmcp_config.json",[315,363,365],{"className":317,"code":364,"language":319,"meta":320,"style":320},"{\n  \"mcpServers\": {\n    \"notion\": {\n      \"serverUrl\": \"https:\u002F\u002Fmcp.notion.com\u002Fmcp\"\n    }\n  }\n}\n",[19,366,367,372,377,382,387,393,399],{"__ignoreMap":320},[324,368,369],{"class":326,"line":327},[324,370,371],{},"{\n",[324,373,374],{"class":326,"line":333},[324,375,376],{},"  \"mcpServers\": {\n",[324,378,379],{"class":326,"line":339},[324,380,381],{},"    \"notion\": {\n",[324,383,384],{"class":326,"line":345},[324,385,386],{},"      \"serverUrl\": \"https:\u002F\u002Fmcp.notion.com\u002Fmcp\"\n",[324,388,390],{"class":326,"line":389},5,[324,391,392],{},"    }\n",[324,394,396],{"class":326,"line":395},6,[324,397,398],{},"  }\n",[324,400,402],{"class":326,"line":401},7,[324,403,348],{},"\n直接走原生远程 ",[19,406,294],{},"，省掉了本地 ",[19,409,410],{},"npx mcp-remote"," 桥接进程，后续升级也由插件市场托管。",[15,413,414,415,418,419,422,423,425,426,429,430,433,434,436],{},"但独立 MCP 也有插件替代不了的强项：",[41,416,417],{},"完全掌控本地执行命令和启动参数","。比如我本机还有一个自建的本地 Gmail MCP，就是通过 ",[19,420,421],{},"uv"," 直接拉起本地 Python 脚本（Stdio 模式）；再比如 ",[19,424,29],{},"，我在 Antigravity 主配置里把参数从 ",[19,427,428],{},"--isolated"," 改成了 ",[19,431,432],{},"--autoConnect","，用来直连当前登录态的 Chrome。这类私有工具和精细参数调整，写在自己的 ",[19,435,129],{}," 里最直接。",[197,438,440],{"id":439},"_23-跨客户端配置边界主配置cli-与其他-ai-工具各自独立","2.3 跨客户端配置边界：主配置、CLI 与其他 AI 工具各自独立",[15,442,443],{},"检查本机配置时我顺便对比了几套客户端，发现它们各自读自己的配置文件：",[205,445,446,457,465,477],{},[208,447,448,249,451,453,454,69],{},[41,449,450],{},"Antigravity 主配置",[19,452,21],{},"（权限白名单在 ",[19,455,456],{},"~\u002F.gemini\u002Fconfig\u002Fconfig.json",[208,458,459,249,462],{},[41,460,461],{},"Antigravity CLI",[19,463,464],{},"~\u002F.gemini\u002Fantigravity-cli\u002Fmcp_config.json",[208,466,467,249,470,473,474],{},[41,468,469],{},"Claude Code",[19,471,472],{},"~\u002F.claude.json"," 顶层 ",[19,475,476],{},"mcpServers",[208,478,479,249,482,485,486],{},[41,480,481],{},"Codex",[19,483,484],{},"~\u002F.codex\u002Fconfig.toml"," 下的 ",[19,487,488],{},"[mcp_servers.*]",[15,490,491],{},"插件机制只服务于 Antigravity 自身；而独立 MCP 的配置思路与启动命令几乎可以原封不动复制到其他客户端。",[197,493,495],{"id":494},"_24-远端账号限制不会因为换了插件就消失","2.4 远端账号限制不会因为换了插件就消失",[15,497,498,499,502,503,253,506,253,509,253,512,253,515,518,519,522],{},"在切换前，我先用独立 Notion MCP 跑了一次 ",[19,500,501],{},"notion-get-tool-access"," 检查工具可用性。在当前个人账号套餐下，基础的 ",[19,504,505],{},"fetch",[19,507,508],{},"create_pages",[19,510,511],{},"update_page",[19,513,514],{},"list_recent_pages",[19,516,517],{},"create_comment"," 等均为 ",[19,520,521],{},"available","，但可以看到明确的服务端边界：",[205,524,525,535,558],{},[208,526,527,530,531,534],{},[19,528,529],{},"query_data_sources"," 标记为 ",[19,532,533],{},"available_with_limit","；",[208,536,537,253,540,253,543,546,547,550,551,554,555,534],{},[19,538,539],{},"query_multiple_data_sources",[19,541,542],{},"query_meeting_notes",[19,544,545],{},"connector_search","、评论修改\u002F删除\u002F解决以及建议编辑（",[19,548,549],{},"*_suggested_edit","）均返回 ",[19,552,553],{},"plan_required"," 或 ",[19,556,557],{},"full_version_required",[208,559,560,563,564,567,568,571,572,575,576,579],{},[19,561,562],{},"search"," 虽然可用，但按编辑人过滤（",[19,565,566],{},"filters.edited_by_user_ids","）、按时间范围过滤（",[19,569,570],{},"filters.last_edited_date_range","）、仅搜标题（",[19,573,574],{},"filters.title_only","）以及非相关性排序（",[19,577,578],{},"sort","）都会提示需要 Business 或 Enterprise 套餐。",[15,581,582,583,586,587,235],{},"这部分能力边界在 Notion 服务端判定，底层连的是同一个 ",[19,584,585],{},"https:\u002F\u002Fmcp.notion.com\u002Fmcp"," 端点，",[41,588,589],{},"从独立 MCP 换成官方\u002F合作插件并不会自动解锁付费功能",[187,591],{},[10,593,595],{"id":594},"_3-完整复现以-notion-为例从独立-mcp-平滑切到插件","3. 完整复现：以 Notion 为例，从独立 MCP 平滑切到插件",[15,597,598,599,601],{},"如果你之前已经在 ",[19,600,129],{}," 里配过 Notion，想试着切到插件，建议按下面四步走，避免出现“两套工具同时挂在上下文里”的尴尬状态。",[197,603,605],{"id":604},"step-1先停用原来的独立-mcp-条目","Step 1：先停用原来的独立 MCP 条目",[15,607,608,609,611,612,615,616,618],{},"打开 ",[19,610,21],{},"，给原来的 ",[19,613,614],{},"\"notion\""," 加上 ",[19,617,133],{},"（先禁用比直接删掉更稳妥，万一想回退去掉这一行就行）：",[315,620,622],{"className":317,"code":621,"language":319,"meta":320,"style":320},"{\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,623,624,628,632,636,641,646,651,656,662,668,674,679,684],{"__ignoreMap":320},[324,625,626],{"class":326,"line":327},[324,627,371],{},[324,629,630],{"class":326,"line":333},[324,631,376],{},[324,633,634],{"class":326,"line":339},[324,635,381],{},[324,637,638],{"class":326,"line":345},[324,639,640],{},"      \"command\": \"npx\",\n",[324,642,643],{"class":326,"line":389},[324,644,645],{},"      \"args\": [\n",[324,647,648],{"class":326,"line":395},[324,649,650],{},"        \"-y\",\n",[324,652,653],{"class":326,"line":401},[324,654,655],{},"        \"mcp-remote@latest\",\n",[324,657,659],{"class":326,"line":658},8,[324,660,661],{},"        \"https:\u002F\u002Fmcp.notion.com\u002Fmcp\"\n",[324,663,665],{"class":326,"line":664},9,[324,666,667],{},"      ],\n",[324,669,671],{"class":326,"line":670},10,[324,672,673],{},"      \"disabled\": true\n",[324,675,677],{"class":326,"line":676},11,[324,678,392],{},[324,680,682],{"class":326,"line":681},12,[324,683,398],{},[324,685,687],{"class":326,"line":686},13,[324,688,348],{},[197,690,692],{"id":691},"step-2在-marketplace-安装并启用-notion-插件","Step 2：在 Marketplace 安装并启用 Notion 插件",[15,694,695,696,698,699,701,702,235],{},"在 Antigravity 插件市场搜索并安装 Notion 插件（Catalog ID 为 ",[19,697,25],{},"）。安装完成后，插件文件会落在 ",[19,700,241],{},"，无需手动去改 ",[19,703,456],{},[197,705,707],{"id":706},"step-3核对新旧工具组是否切换干净","Step 3：核对新旧工具组是否切换干净",[15,709,710],{},"开启一轮新对话或刷新后，检查两处变化：",[712,713,714,720],"ol",{},[208,715,716,717,719],{},"原来的 ",[19,718,152],{}," MCP 工具组已清空，没有两套工具并存；",[208,721,722,723,727,728,731],{},"新工具组以 ",[41,724,725],{},[19,726,146],{}," 的服务名挂载，同时 12 个 ",[19,729,730],{},"notion-*"," Skills 变为可用状态。",[197,733,735],{"id":734},"step-4用只读探针验证连通性","Step 4：用只读探针验证连通性",[15,737,738,739,741],{},"分别调用 ",[19,740,146],{}," 下的只读工具做一次最小验收：",[712,743,744,755],{},[208,745,746,747,750,751,754],{},"调用 ",[19,748,749],{},"notion-get-self","（参数 ",[19,752,753],{},"{}","）：确认返回当前工作区名称、ID 与登录账号信息；",[208,756,746,757,750,760,763],{},[19,758,759],{},"notion-list-recent-pages",[19,761,762],{},"{\"limit\": 3}","）：确认能正常拉取最近访问的数据库与页面列表。",[15,765,766],{},"两项都正常返回，就说明 OAuth 登录态与插件连接都已接通。",[187,768],{},[10,770,772],{"id":771},"_4-实测踩到的四个细节与避坑清单","4. 实测踩到的四个细节与避坑清单",[712,774,775,808,862,915],{},[208,776,777,780],{},[41,778,779],{},"同时开着插件和独立 MCP，上下文平白多出一倍工具定义",[205,781,782,796],{},[208,783,784,787,788,790,791,231,793,795],{},[41,785,786],{},"现象","：安装 Notion 插件后如果没关 ",[19,789,129],{},"，Agent 会同时看到 ",[19,792,152],{},[19,794,146],{}," 两套几乎一模一样的几十个工具。",[208,797,798,801,802,804,805,807],{},[41,799,800],{},"解法","：同一服务严格二选一。切插件后立即在 ",[19,803,129],{}," 设 ",[19,806,133],{}," 或删掉原条目。",[208,809,810,813],{},[41,811,812],{},"切换之后，以前点过“始终允许”的操作又开始弹窗确认",[205,814,815,831,854],{},[208,816,817,819,820,823,824,253,827,830],{},[41,818,786],{},"：明明之前在 ",[19,821,822],{},"config.json"," 里已经给 ",[19,825,826],{},"notion-fetch",[19,828,829],{},"notion-update-page"," 点过自动放行，切到插件后又得重新点允许。",[208,832,833,836,837,839,840,843,844,253,847,850,851,853],{},[41,834,835],{},"根因","：旧白名单保存在 ",[19,838,456],{}," 的 ",[19,841,842],{},"userSettings.globalPermissionGrants.allow"," 中，规则名是 ",[19,845,846],{},"mcp(notion\u002Fnotion-fetch)",[19,848,849],{},"mcp(notion\u002Fnotion-update-page)","；而插件暴露的服务名变成了 ",[19,852,146],{},"，旧规则名不再命中。",[208,855,856,858,859,861],{},[41,857,800],{},"：不用手改 ",[19,860,822],{},"，后续遇到写操作弹窗时重新点一次允许即可（长期不用的旧规则也可以顺手清理）。",[208,863,864,870],{},[41,865,866,867,869],{},"桌面端好好的，切到 ",[19,868,168],{}," 工具却不见了或行为不一样",[205,871,872,880,910],{},[208,873,874,876,877,879],{},[41,875,786],{},"：在 Antigravity 主客户端里配置好了工具，换到命令行 ",[19,878,168],{}," 时发现少了某个本地服务，或者浏览器连接行为不对。",[208,881,882,884,885,887,888,890,891,894,895,898,899,901,902,253,904,906,907,909],{},[41,883,835],{},"：主配置（",[19,886,21],{},"）和 CLI 配置（",[19,889,464],{},"）是两份独立文件。比如我本机主配置里有本地 ",[19,892,893],{},"gmail"," 脚本且 ",[19,896,897],{},"chrome-devtools"," 用 ",[19,900,432],{},"，而 CLI 版里没有 ",[19,903,893],{},[19,905,897],{}," 用的是 ",[19,908,428],{},"，反而多了另外两个工具。",[208,911,912,914],{},[41,913,800],{},"：排查“为什么换了个入口工具变了”时，记得两边配置文件分开核对。",[208,916,917,920],{},[41,918,919],{},"换完插件仍然调不通会议搜索或跨源检索",[205,921,922,932,942],{},[208,923,924,926,927,554,929,931],{},[41,925,786],{},"：切到 Notion 官方插件后，",[19,928,542],{},[19,930,545],{}," 等高阶能力依旧受限。",[208,933,934,936,937,291,939,941],{},[41,935,835],{},"：这是 Notion 账号套餐权限策略（",[19,938,553],{},[19,940,557],{},"）导致的，和本地用插件还是手配 MCP 没有关系。",[208,943,944,946,947,949],{},[41,945,800],{},"：先调用一次 ",[19,948,501],{}," 查看当前账号的完整工具权限表，确认是配置问题还是套餐限制，避免无效折腾。",[187,951],{},[10,953,955],{"id":954},"_5-选型建议与适用边界","5. 选型建议与适用边界",[15,957,958,959,249],{},"综合这次实测，我在 Antigravity 里的配置策略很明确——",[41,960,961],{},"按服务做混合选型，而不是一刀切",[205,963,964,983],{},[208,965,966,249,969],{},[41,967,968],{},"优先用官方 \u002F Marketplace 插件的场景",[205,970,971,974,977],{},[208,972,973],{},"对接 Notion、Canva、Chrome DevTools 这类有官方或合作方维护插件的标准服务；",[208,975,976],{},"希望直接复用配套 Skills（例如让 Agent 按规范帮我整理会议纪要、写周报、拆项目 Spec）；",[208,978,979,980,982],{},"想减少本地 ",[19,981,410],{}," 进程维护，直接用插件面板一键启停和更新。",[208,984,985,249,988],{},[41,986,987],{},"继续用独立 \u002F 自建 MCP 的场景",[205,989,990,993,996],{},[208,991,992],{},"自己写的本地私有脚本或内部服务（例如本地 Python\u002FNode MCP）；",[208,994,995],{},"需要精细调整 CLI 参数（比如切换无头模式、隔离模式或自动附着当前浏览器）；",[208,997,998,999,1002],{},"只把远程服务当纯数据读写接口、不想动已配置好的 ",[19,1000,1001],{},"mcp(\u003Cname>\u002F...)"," 白名单，或者需要让多套 AI 客户端保持完全一致的 JSON 配置结构。",[1004,1005,1006],"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":320,"searchDepth":333,"depth":333,"links":1008},[1009,1010,1016,1022,1023],{"id":12,"depth":333,"text":13},{"id":191,"depth":333,"text":192,"children":1011},[1012,1013,1014,1015],{"id":199,"depth":339,"text":200},{"id":275,"depth":339,"text":276},{"id":439,"depth":339,"text":440},{"id":494,"depth":339,"text":495},{"id":594,"depth":333,"text":595,"children":1017},[1018,1019,1020,1021],{"id":604,"depth":339,"text":605},{"id":691,"depth":339,"text":692},{"id":706,"depth":339,"text":707},{"id":734,"depth":339,"text":735},{"id":771,"depth":333,"text":772},{"id":954,"depth":333,"text":955},"coder","2026-11-16","以 Notion 为例拆解 Antigravity 官方\u002F合作插件与独立自建 MCP 在打包形式、传输协议、命名空间与跨端复用上的异同，给出完整平滑切换步骤、四项避坑指南与选型建议。","md",null,{},true,"\u002Fzh\u002Fblog\u002Fantigravity-plugins-vs-mcp",{"title":5,"description":1026},"antigravity-plugins-vs-mcp","publish","zh\u002Fblog\u002Fantigravity-plugins-vs-mcp",[1037,1038,1039,1040,1041],"Antigravity","MCP","Notion","Plugin","Agent","mINUX5U-xpZduLVwwAfPkPHkFm_Yx95bj8c7-4c40Xw",[1028,1044],{"title":1045,"path":1046,"stem":1047,"slug":1048,"date":1049,"children":-1},"不改数据库，用 OpenCC 给 Moodle 加上全站繁体中文转换（含 RequireJS 避坑）","\u002Fzh\u002Fblog\u002Fmoodle-opencc-traditional-chinese","zh\u002Fblog\u002Fmoodle-opencc-traditional-chinese","moodle-opencc-traditional-chinese","2026-11-09",1794797295134]