[{"data":1,"prerenderedAt":722},["ShallowReactive",2],{"home":3,"article-\u002Fblog\u002Fmcp-vs-webmcp-architecture-guide":316},{"id":4,"title":5,"articleCta":6,"calculatorCallout":11,"capabilities":17,"capabilitiesSectionText":42,"capabilitiesSectionTitle":43,"closing":44,"contact":49,"contactNext":61,"engagements":77,"engagementsSectionText":103,"engagementsSectionTitle":104,"extension":105,"faq":106,"footer":135,"founder":140,"getStartedSectionTitle":155,"getStartedSteps":155,"heroCtaButton":156,"heroKicker":157,"heroPoints":158,"introSectionText":162,"introSectionTitle":163,"meta":164,"microcopy":165,"navbar":177,"processSectionText":197,"processSectionTitle":198,"processSteps":199,"productionSystems":216,"qualifier":239,"services":258,"servicesSectionText":283,"servicesSectionTitle":284,"stem":285,"trustBar":286,"whyUs":293,"whyUsSectionTitle":314,"__hash__":315},"home\u002Fhome.yaml","Software Architecture, Audits & Production AI Consultancy",{"kicker":7,"title":8,"primary":9,"secondary":10},"Working on something like this?","A 30-minute call tells us both whether we can help.","Request a scoping call","More field notes",{"kicker":12,"title":13,"description":14,"cta":15,"url":16},"Build vs. buy decision tool","Weighing growing SaaS bills against a custom build?","Model your 5-year subscription creep, enterprise tier jumps, and integration tax against a focused custom platform.","Open the 5-year TCO calculator","\u002Ftools\u002Fsaas-vs-custom-calculator",[18,22,26,30,34,38],{"title":19,"icon":20,"description":21},"System & Data Architecture","network","Modular monoliths, bounded services, and PostgreSQL schemas designed around clean contracts rather than hype-driven complexity.",{"title":23,"icon":24,"description":25},"MCP & Agentic Integration","plug","Model Context Protocol servers, browser WebMCP tools, and LangGraph workflows that keep business rules and permissions deterministic.",{"title":27,"icon":28,"description":29},"Custom Software & Internal Portals","code","Full-stack Vue, Nuxt, TypeScript, Node.js, Python, and PostgreSQL builds shaped around operational workflows that off-the-shelf SaaS misses.",{"title":31,"icon":32,"description":33},"ERP, CRM & Workflow Automation","workflow","Durable n8n pipelines, job queues, and cross-system integrations with error recovery, audit logs, and human-in-the-loop checkpoints.",{"title":35,"icon":36,"description":37},"Cloud, Kubernetes & DevOps","cloud","AWS, Azure, GCP, UpCloud, Terraform, and Kubernetes deployments built for reproducible environments and predictable hosting spend.",{"title":39,"icon":40,"description":41},"Security, Compliance & Regulated Domains","shield","Threat modeling, least-privilege access, database row-level security, and engineering controls tailored for HIPAA, HL7 FHIR, SOC 2, and EU privacy rules.","The engineering disciplines behind our audits, integrations, and custom builds.","Core Architectural Capabilities",{"kicker":45,"title":46,"accent":47,"tagline":48},"Next step","Bring the problem.","We will bring the architecture.","Software architecture and production AI consultancy, led by senior architect Mihai Farcas.",{"title":50,"description":51,"form":52},"Tell Us Where the Architecture or Workflow Is Stuck.","Share the system challenge, audit deadline, or automation bottleneck. You will get an honest recommendation on whether an audit, a build, or a simpler fix makes sense.",{"title":53,"description":54,"namePlaceholder":55,"emailPlaceholder":56,"messagePlaceholder":57,"submitButton":58,"errorMessage":59,"thankYouMessage":60},"Request a Scoping Call","Send a short overview of your stack, constraints, and timeline.","Your Name","Work Email","Tell us about your platform, audit timeline, or integration goals...","Send Scoping Request","Something went wrong sending your message. Please try again later, or email us directly at","Thank you! Mihai will review your note and reply within one business day.",{"kicker":62,"items":63,"quickLinksTitle":67,"quickLinks":68},"What happens next",[64,65,66],"Mutual NDA signed before you share repositories, schemas, or internal workflows.","Direct 30-minute scoping call with Mihai Farcas, never a scripted sales handoff.","Clear fixed-fee proposal within 48 hours, or a direct steer if you do not need outside help.","Helpful starting points",[69,72,75],{"label":70,"url":71},"Software architecture audit deliverables","\u002Fservices\u002Fsoftware-architecture-audit",{"label":73,"url":74},"MCP & AI integration service","\u002Fservices\u002Fmcp-ai-integration",{"label":76,"url":16},"5-year SaaS vs. custom cost calculator",[78,84,91,98],{"title":79,"featured":80,"bestFor":81,"description":82,"price":83},"Discovery & Architecture Sprint",true,"Best for: teams turning an open problem or build-vs-buy question into a concrete plan.","A focused one-to-two week sprint yielding a written architecture recommendation, technical risk list, and costed delivery roadmap.","Fixed fee · 1–2 weeks",{"title":85,"bestFor":86,"description":87,"price":88,"link":89},"Software Architecture Audit","Best for: M&A due diligence, inherited platforms, or pre-rebuild verification.","Forensic evaluation across eight architecture dimensions, delivered as an Executive Decision Report and a Technical Engineering Annex.","Fixed fee · 1–4 weeks",{"label":90,"url":71},"Audit deliverables & scope",{"title":92,"bestFor":93,"description":94,"price":95,"link":96},"MCP & AI Automation Build","Best for: teams connecting ERP, CRM, or internal databases safely to AI workflows.","Scoped delivery of custom MCP servers, browser WebMCP tools, n8n pipelines, or internal automation portals with strict security boundaries.","Fixed scope · 4–8 weeks",{"label":97,"url":74},"MCP & AI service overview",{"title":99,"bestFor":100,"description":101,"price":102},"Fractional Architect Retainer","Best for: founders and SMEs needing senior technical leadership without a full-time CTO hire.","Ongoing senior advisory for architecture decisions, pull request reviews, hiring interviews, vendor oversight, and quarterly planning.","Monthly retainer · flexible scope","Four clear engagement shapes matched to where your engineering team is today.","Ways to Work With Us","yaml",{"title":107,"subtitle":108,"cta":109,"questions":110},"Frequently Asked Questions","Common questions from founders, CTOs, and diligence teams before a scoping call.","Prefer direct email? Reach us at",[111,114,117,120,123,126,129,132],{"question":112,"answer":113},"What does Innovi Pro specialize in?","We focus on two connected areas: independent software architecture consulting (audits, M&A due diligence, build-vs-buy strategy) and hands-on engineering for custom platforms, MCP servers, and AI workflow automation.",{"question":115,"answer":116},"Who conducts the architecture audits and scoping calls?","Every scoping call, forensic codebase review, and executive briefing is personally led by Mihai Farcas, Lead Software Architect at Innovi Pro.",{"question":118,"answer":119},"How is Innovi Pro different from a typical software agency?","You work directly with the senior architect and a small trusted engineering network. We keep active client slots deliberately limited rather than staffing layered account managers and rotating junior squads.",{"question":121,"answer":122},"Do you only build AI projects?","Often the right fix is a cleaner PostgreSQL schema, proper background queues, or consolidating SaaS sprawl rather than adding an LLM. We recommend plain deterministic engineering whenever it wins.",{"question":124,"answer":125},"How do engagements start and how are they priced?","Audits, discovery sprints, and vendor reviews run on a fixed fee agreed up front. Custom builds are fixed-scope after discovery, and ongoing architectural guidance runs on a monthly retainer.",{"question":127,"answer":128},"Can you sign an NDA and work inside regulated environments?","Yes. Standard mutual NDAs are signed before code access, and we have built production platforms operating under HIPAA, HL7 FHIR R5, GDPR, and enterprise security expectations.",{"question":130,"answer":131},"Can you work alongside our existing engineering team?","Yes. Most clients engage us to augment their internal engineering leadership, unblock architectural bottlenecks, or handle specialized MCP and automation tracks in their current stack.",{"question":133,"answer":134},"How do we know whether to buy SaaS or build custom software?","Use our interactive 5-year TCO calculator to compare seat growth and tier jumps against build and maintenance costs, or send us your numbers for an honest build-vs-buy review.",{"title":136,"address":137,"email":138,"copyright":139},"Innovi Pro","Cluj-Napoca, Romania","contact@innovi.pro","© 2026 Innovi Pro. All rights reserved.",{"kicker":141,"name":142,"role":143,"photoAlt":144,"bio":145,"tags":148},"The architect behind Innovi Pro","Mihai Farcas","Lead Software Architect","Mihai Farcas, Lead Software Architect at Innovi Pro",[146,147],"I help founders, CTOs, and engineering teams make durable architectural decisions and deliver custom software that holds up under load. My work pairs **independent architecture consulting** with hands-on delivery across a small trusted engineering network.","Our own production platforms include [Innovi Care](https:\u002F\u002Finnovi.care) for clinical FHIR R5 workflows, [RetroAgile](https:\u002F\u002Fretroagile.com) for agentic engineering telemetry, and [GraphPG](https:\u002F\u002Fgraphpg.com) for compiling PostgreSQL catalogs into APIs. I publish deep-dive engineering notes on [mihai.ltd](https:\u002F\u002Fmihai.ltd\u002Fblog) and architectural playbooks on the [Innovi Pro blog](\u002Fblog).",[149,150,151,152,153,154],"Software architecture","MCP & WebMCP","n8n","PostgreSQL","Kubernetes","Healthcare IT",null,"Explore our services","Software architecture · Production AI · Cluj-Napoca",[159,160,161],"Led directly by senior architect Mihai Farcas","Independent architecture audits & technical due diligence","Production MCP, n8n & FHIR R5 systems","We audit complex software architectures before expensive decisions, and build production MCP servers, n8n workflows, and custom platforms designed to last.","Software Architecture & [Production AI Systems.]",{},{"primaryCta":9,"stackTitle":166,"scorecardLink":167,"qualifierCta":168,"featuredEngagement":169,"engagementsHelp":170,"engagementsHelpLink":171,"whyUsCard":172,"formNote":176},"Core delivery stack","The method","Recognize one of these? Request a call","Typical first step","Not sure which engagement fits?","Send a short brief and we will recommend one.",{"kicker":173,"title":174,"cta":175},"Start here","A 30-minute scoping call. Direct access to the architect.","Request a call","NDAs are standard. Mihai replies within one business day to schedule a 30-minute scoping call.",{"items":178},[179,182,185,188,191,194],{"title":180,"url":181},"Services","\u002F#services",{"title":183,"url":184},"Systems","\u002F#work",{"title":186,"url":187},"Engagements","\u002F#engagements",{"title":189,"url":190},"Why Us","\u002F#why-us",{"title":192,"url":193},"Blog","\u002Fblog",{"title":195,"url":196},"Request a Call","\u002F#contact","Transparent steps from initial review to shipped software, without bloated statements of work.","How We Work",[200,204,208,212],{"title":201,"meta":202,"description":203},"1. Scoping Call","30 min · free","A focused 30-minute conversation directly with Mihai Farcas. Bring the bottleneck, architecture question, or codebase history and we ask the direct questions.",{"title":205,"meta":206,"description":207},"2. Fixed-Fee Discovery or Audit","1–4 weeks · fixed fee","We inspect repositories, schemas, and cloud manifests under NDA, then deliver a written scorecard, risk register, and costed roadmap.",{"title":209,"meta":210,"description":211},"3. Iterative Delivery","2-week cycles","When you move into build mode, we deliver working software and integrations in two-week cycles with shared repositories and direct engineer access.",{"title":213,"meta":214,"description":215},"4. Handover & Advisory","Optional retainer","Your team receives readable documentation, clean deployments, and training to own the platform, with optional fractional architect support afterward.",{"kicker":217,"title":218,"subtitle":219,"items":220},"Systems in production","Platforms built and operated by our studio","We test our architectural patterns on software we ship and maintain ourselves.",[221,227,233],{"title":222,"tag":223,"url":224,"linkLabel":225,"description":226},"Innovi Care","Healthcare · FHIR R5","https:\u002F\u002Finnovi.care","Inspect innovi.care","Clinical workflow platform and patient portal built on HL7 FHIR R5 and PostgreSQL 18, enforcing consent boundaries and conflict-free booking in the database.",{"title":228,"tag":229,"url":230,"linkLabel":231,"description":232},"RetroAgile","Agentic IDP","https:\u002F\u002Fretroagile.com","Inspect retroagile.com","Internal developer platform and telemetry layer for AI coding agents, spec-readiness checks, and ephemeral Zero Trust demo environments.",{"title":234,"tag":235,"url":236,"linkLabel":237,"description":238},"GraphPG","Open-Source Engine","https:\u002F\u002Fgraphpg.com","Inspect graphpg.com","Rust query engine compiling PostgreSQL catalogs directly into GraphQL and OpenAPI REST APIs while keeping row-level authorization in Postgres.",{"title":240,"subtitle":241,"items":242},"Is this you?","Most of our engagements begin with one of these five situations.",[243,246,249,252,255],{"title":244,"description":245},"You are about to commit to a 6-figure build or acquisition and need clear verification.","An independent architecture review before you sign. Vendor proposals translated into plain English, with risks ranked by operational impact.",{"title":247,"description":248},"You inherited a platform and need to know what is salvageable.","Whether built by a previous agency or an early founding team, you get an honest assessment before putting another quarter of engineering budget into it.",{"title":250,"description":251},"Your SaaS stack has quietly become a spreadsheet with extra steps.","Ten disconnected tools, rising per-seat bills, and the real workflow living in someone's inbox. You need software or clean integrations shaped around how your team works.",{"title":253,"description":254},"Your team spends half its week on repeatable operational glue.","Invoicing, triage, and copying records between systems. You want reliable background automation rather than fragile prompt scripts.",{"title":256,"description":257},"You want AI plugged into real systems without creating a security hole.","Not another standalone chat box: backend MCP servers, browser WebMCP tools, and scoped workflows backed by proper access control.",[259,271],{"title":260,"description":261,"icon":262,"deliverables":263,"link":269},"Software Architecture Audits & Technical Consultancy","Independent system and architecture audits, technical due diligence, vendor proposal reviews, and costed modernization roadmaps. Every audit delivers a written executive report and an engineering annex your developers can execute directly.","architect",[264,265,266,267,268],"Eight-dimension architecture audit","M&A technical due diligence","Vendor code & quote reviews","Cloud & PostgreSQL scaling plans","Costed 90-day modernization roadmaps",{"label":270,"url":71},"How the architecture audit works",{"title":272,"description":273,"icon":274,"deliverables":275,"link":281},"MCP Servers, WebMCP & AI Automation Engineering","Production integration engineering for teams connecting models to real systems. We build backend MCP servers, browser-side WebMCP tools, LangGraph agents, and self-hosted n8n workflows with strict authorization boundaries.","automation",[276,277,278,279,280],"Custom backend MCP servers","In-browser WebMCP tool integration","Production n8n & queue pipelines","PostgreSQL RLS & Zero Trust boundaries","ERP, CRM & internal API wiring",{"label":282,"url":74},"How MCP & AI integration works","Two ways to work with us: independent architectural counsel when technical decisions are expensive, and hands-on engineering when it is time to ship.","What We Do","home",{"title":287,"items":288},"Senior experience you can reach directly.",[289,290,291,292],"10+ years shipping enterprise software","Experience across healthcare, insurance, fintech & SaaS","Published on DEV, YouTube & engineering blogs","HIPAA · HL7 · FHIR R5 experience",[294,298,302,306,310],{"title":295,"icon":296,"description":297},"Led End-to-End by a Senior Architect","compass","The same senior architect on your scoping call writes the design docs and reviews the pull requests, avoiding agency handoffs to junior benches.",{"title":299,"icon":300,"description":301},"Deep n8n, MCP & Database Engineering","badge","Hands-on production experience across n8n, LangGraph, Model Context Protocol, and PostgreSQL, picking the simplest durable tool for each layer.",{"title":303,"icon":304,"description":305},"Enterprise Rigor, Lean Speed","gauge","Architectural discipline from regulated healthcare and financial systems, applied cleanly so small and mid-market teams stay fast.",{"title":307,"icon":308,"description":309},"Direct Engineering Access","users","You collaborate directly with the engineers building your system, keeping feedback loops measured in hours instead of account-manager relays.",{"title":311,"icon":312,"description":313},"Disciplined AI-Assisted Delivery","sparkles","We pair AI coding workflows with deterministic database constraints and strict verification, shipping faster without trading away reliability.","Why Teams Work With Us","9dwq0en3tqZRbupD2RHzDd_us1wlmuBnzWo6xwhGDBM",{"id":317,"title":318,"author":142,"body":319,"canonical":702,"date":703,"description":704,"extension":705,"image":706,"imageAlt":707,"imageFallback":708,"meta":709,"navigation":80,"ogImage":708,"path":710,"published":80,"readingTime":711,"seo":712,"stem":713,"tags":714,"twitterCard":719,"type":720,"__hash__":721},"blog\u002Fblog\u002Fmcp-vs-webmcp-architecture-guide.md","When to Use Backend MCP Servers vs Browser WebMCP Tools",{"type":320,"value":321,"toc":693},"minimark",[322,326,330,353,360,365,378,381,404,407,411,422,425,444,448,451,553,572,576,579,582,622,631,644,648,651,678],[323,324,318],"h1",{"id":325},"when-to-use-backend-mcp-servers-vs-browser-webmcp-tools",[327,328,329],"p",{},"Teams adding AI capabilities to an existing software product run into an awkward architectural fork early on. They usually handle it either by standing up a separate backend connector layer for every workflow, or by pointing a browser automation agent at their web UI and hoping CSS selectors hold together across releases. Both approaches solve part of the job, however they fail in opposite ways, which is why the Model Context Protocol (MCP) ecosystem now spans two distinct layers: backend MCP servers and in-browser WebMCP tools.",[327,331,332,333,340,341,346,347,352],{},"In this architecture guide we compare backend ",[334,335,339],"a",{"href":336,"rel":337},"https:\u002F\u002Fmodelcontextprotocol.io\u002F",[338],"nofollow","Model Context Protocol (MCP)"," servers against ",[334,342,345],{"href":343,"rel":344},"https:\u002F\u002Fgithub.com\u002Fwebmachinelearning\u002Fwebmcp",[338],"WebMCP",", explain what changes at the authentication and state layers, and show when a production system benefits from running both together. If you want the TypeScript and Vue implementation side rather than the system design view, read the companion engineering walkthrough on ",[334,348,351],{"href":349,"rel":350},"https:\u002F\u002Fmihai.ltd\u002Fblog\u002Fwebmcp-in-practice-registering-browser-tools\u002F",[338],"registering browser AI tools with WebMCP",".",[327,354,355],{},[356,357],"img",{"alt":358,"src":359},"Protocol architecture comparing backend MCP servers invoked over JSON-RPC by external AI hosts with client-side WebMCP tools invoked through document.modelContext inside the browser tab, both converging on the same backend API and PostgreSQL RLS boundary.","\u002Fblog\u002Fdiagrams\u002Fmcp-vs-webmcp-flow-poster.webp",[361,362,364],"h2",{"id":363},"why-one-protocol-was-not-enough","Why one protocol was not enough",[327,366,367,368,372,373,377],{},"Backend MCP solved a real integration bottleneck when teams needed external hosts like Claude, ChatGPT, Copilot, or ",[334,369,151],{"href":370,"rel":371},"https:\u002F\u002Fn8n.io\u002F",[338]," to reach internal APIs and databases through one standardized contract, which we covered in our earlier ",[334,374,376],{"href":375},"\u002Fblog\u002Fwhat-is-mcp-model-context-protocol-explained","MCP protocol overview",". Because those tool calls run out-of-band between the AI platform and a backend server, they work well whenever nobody is looking at a browser screen.",[327,379,380],{},"The trouble starts when a user is already sitting inside an interactive web application, such as a clinical schedule, a construction finance grid, or a code review queue, and wants an assistant to help inside that live workspace. Routing that request through a remote backend MCP server creates three practical headaches:",[382,383,384,392,398],"ul",{},[385,386,387,391],"li",{},[388,389,390],"strong",{},"UI disintermediation."," The agent hits the database or API behind the user's back, so the screen in front of the person does not reflect changes cleanly unless you build extra realtime sync plumbing.",[385,393,394,397],{},[388,395,396],{},"Duplicated session and draft state."," A remote server cannot see unsaved form inputs, active filters, selected table rows, or local browser state without mirroring all of it over the network.",[385,399,400,403],{},[388,401,402],{},"Extra infrastructure for client-side tasks."," Exposing simple UI actions, such as sorting a table or prefilling a multi-step form, forces engineers to maintain a separate backend service when the page already holds the logic in JavaScript.",[327,405,406],{},"Without a standard client-side contract, browser agents fell back to visual scraping, accessibility-tree snapshots, and simulated clicks. That brittle loop is slow, burns tokens on raw DOM markup, and breaks whenever a front-end component changes its layout.",[361,408,410],{"id":409},"how-webmcp-fits-next-to-backend-mcp","How WebMCP fits next to backend MCP",[327,412,413,417,418,421],{},[334,414,345],{"href":415,"rel":416},"https:\u002F\u002Fwebmachinelearning.github.io\u002Fwebmcp\u002F",[338],", incubated inside the W3C Web Machine Learning Community Group, adds a browser-native tool surface via ",[28,419,420],{},"document.modelContext.registerTool()",". Rather than scraping buttons or bypassing your web app entirely, a running page exposes typed JavaScript functions with JSON Schemas and plain-English descriptions directly to a browser-integrated agent or extension.",[327,423,424],{},"The distinction matters because WebMCP targets cooperative human-in-the-loop work rather than unattended automation. A tool registered in the browser executes inside the user's open tab, reuses their existing authenticated cookies or session tokens, updates the live Vue or React state immediately, and keeps consequential confirmations visible on screen.",[327,426,427,428,431,432,435,436,439,440,443],{},"A companion exploratory proposal in the repository explores declarative HTML ",[28,429,430],{},"\u003Cform>"," attributes such as ",[28,433,434],{},"toolname"," and ",[28,437,438],{},"tooldescription",", though the current specification focuses on the imperative ",[28,441,442],{},"document.modelContext"," JavaScript API because rich web applications need dynamic registration tied to active routes and state.",[361,445,447],{"id":446},"comparing-backend-mcp-and-webmcp-side-by-side","Comparing backend MCP and WebMCP side by side",[327,449,450],{},"Choosing between the two protocols gets much easier when you separate where the user sits from where the system of record lives.",[452,453,454,471],"table",{},[455,456,457],"thead",{},[458,459,460,465,468],"tr",{},[461,462,464],"th",{"align":463},"left","Architecture question",[461,466,467],{"align":463},"Backend MCP server",[461,469,470],{"align":463},"Browser WebMCP",[472,473,474,488,501,514,527,540],"tbody",{},[458,475,476,482,485],{},[477,478,479],"td",{"align":463},[388,480,481],{},"Execution location",[477,483,484],{"align":463},"Server process over HTTP\u002FSSE or stdio",[477,486,487],{"align":463},"Live browser tab in client JavaScript",[458,489,490,495,498],{},[477,491,492],{"align":463},[388,493,494],{},"Best fit",[477,496,497],{"align":463},"Headless jobs, cross-system pipelines, external AI hosts",[477,499,500],{"align":463},"Interactive SaaS screens, collaborative co-pilots, live UI updates",[458,502,503,508,511],{},[477,504,505],{"align":463},[388,506,507],{},"Authentication",[477,509,510],{"align":463},"OAuth tokens, API keys, service credentials",[477,512,513],{"align":463},"Existing logged-in browser session and cookies",[458,515,516,521,524],{},[477,517,518],{"align":463},[388,519,520],{},"Unattended \u002F scheduled runs",[477,522,523],{"align":463},"Yes, runs cleanly without an open screen",[477,525,526],{"align":463},"No, tools exist only while the document is open",[458,528,529,534,537],{},[477,530,531],{"align":463},[388,532,533],{},"Browser support (late 2026)",[477,535,536],{"align":463},"Host-agnostic (any MCP client)",[477,538,539],{"align":463},"Origin trials in Chrome 149 and Edge 150, plus ChatGPT Desktop",[458,541,542,547,550],{},[477,543,544],{"align":463},[388,545,546],{},"Main operational risk",[477,548,549],{"align":463},"Token scope creep and stale external state",[477,551,552],{"align":463},"Context bloat from too many page tools, cross-origin exposure",[327,554,555,556,561,562,565,566,571],{},"WebMCP is still early compared to server-side MCP, so progressive enhancement is the sensible stance today. According to the project's ",[334,557,560],{"href":558,"rel":559},"https:\u002F\u002Fgithub.com\u002Fwebmachinelearning\u002Fwebmcp\u002Fblob\u002Fmain\u002Fimplementation-status.md",[338],"implementation status tracker",", Chrome 149 and Edge 150 run Origin Trials, local testing sits behind ",[28,563,564],{},"about:flags#enable-webmcp-testing"," (see ",[334,567,570],{"href":568,"rel":569},"https:\u002F\u002Fdeveloper.chrome.com\u002Fdocs\u002Fai\u002Fwebmcp",[338],"Chrome's WebMCP docs","), and ChatGPT Desktop supports WebMCP directly. Upcoming Brave Leo releases plan to add support too, while Mozilla and WebKit hold open standards positions. Building critical business workflows that depend solely on WebMCP would shut out a large share of users, whereas layering WebMCP on top of existing UI actions upgrades supported browsers safely.",[361,573,575],{"id":574},"security-and-governance-still-belong-on-the-server","Security and governance still belong on the server",[327,577,578],{},"Treating client-side WebMCP as an authorization mechanism is a mistake, for the exact same reason client-side JavaScript validation never secures a normal REST API. Anything executing inside a user's browser tab runs where the user or page scripts can inspect and modify it, and third-party scripts or iframes on the page raise cross-origin questions.",[327,580,581],{},"Two protocol controls govern what runs inside the browser page itself:",[583,584,585,601],"ol",{},[385,586,587,590,591,594,595,600],{},[388,588,589],{},"Permissions Policy isolation."," By default, WebMCP runs in top-level windows and same-origin frames, while cross-origin iframes require explicit delegation via ",[28,592,593],{},"\u003Ciframe allow=\"tools\">"," or server headers (",[334,596,599],{"href":597,"rel":598},"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FHTTP\u002FGuides\u002FPermissions_Policy",[338],"MDN Permissions Policy guide",").",[385,602,603,606,607,610,611,614,615,618,619,352],{},[388,604,605],{},"Scoped frame exposure and safety hints."," The ",[28,608,609],{},"exposedTo"," option limits which secure origins inside a frame tree can discover a registered tool, and tool metadata hints (",[28,612,613],{},"readOnlyHint",", ",[28,616,617],{},"consequentialHint",") help browser hosts decide when to ask a person for confirmation before calling ",[28,620,621],{},"execute",[327,623,624,625,630],{},"Behind both WebMCP and backend MCP, actual data access rules still have to live on your API gateway and database. On our own platforms we push tenant and role checks down into ",[334,626,629],{"href":627,"rel":628},"https:\u002F\u002Fmihai.ltd\u002Fblog\u002Frow-level-security-ai-coding-agents\u002F",[338],"PostgreSQL Row-Level Security (RLS)"," so neither a misconfigured backend MCP server nor a malformed client request can read records belonging to another organization.",[327,632,633,634,639,640,643],{},"Keeping the tool catalog tight matters just as much for reliability as for security. Both ",[334,635,638],{"href":636,"rel":637},"https:\u002F\u002Fdeveloper.chrome.com\u002Fblog\u002Fai-webmcp-origin-trial",[338],"Chrome's WebMCP Origin Trial announcement"," and the specification's best practices warn against registering dozens of overlapping tools upfront, because every schema consumes prompt tokens and increases tool-selection mistakes. Registering tools dynamically per active route, and tearing them down with an ",[28,641,642],{},"AbortController"," signal when the user leaves that screen, keeps the agent accurate.",[361,645,647],{"id":646},"a-practical-adoption-plan-for-software-teams","A practical adoption plan for software teams",[327,649,650],{},"If you are planning an AI integration roadmap over the next two quarters, sequence the work around concrete business bottlenecks rather than protocol novelty:",[382,652,653,663,672],{},[385,654,655,658,659,662],{},[388,656,657],{},"Start with backend MCP when workflows span multiple systems or run unattended."," Triaging inbound support queues, syncing CRM and ERP records, and querying warehouse metrics belong on server-side MCP servers or durable ",[334,660,151],{"href":661},"\u002Fblog\u002Fn8n-production-reference-architecture"," pipelines.",[385,664,665,668,669,671],{},[388,666,667],{},"Layer WebMCP onto complex operational screens."," Workflows where staff filter large financial tables, review clinical charts, or assemble quotes benefit directly when an in-browser assistant calls ",[28,670,442],{}," tools instead of guessing DOM selectors.",[385,673,674,677],{},[388,675,676],{},"Share one deterministic backend boundary."," Route both your UI endpoints and your backend MCP tools through the same typed API contracts and PostgreSQL RLS policies so security posture never forks between human users and AI hosts.",[327,679,680,681,684,685,688,689,692],{},"If your team is deciding where to draw those boundaries across legacy services, ERP connectors, or customer-facing portals, explore our ",[334,682,683],{"href":74},"MCP, WebMCP and AI integration service"," or request an ",[334,686,687],{"href":71},"independent software architecture audit"," before committing engineering headcount. You can also ",[334,690,691],{"href":196},"reach out directly"," to walk through your current stack on a 30-minute scoping call.",{"title":694,"searchDepth":695,"depth":695,"links":696},"",2,[697,698,699,700,701],{"id":363,"depth":695,"text":364},{"id":409,"depth":695,"text":410},{"id":446,"depth":695,"text":447},{"id":574,"depth":695,"text":575},{"id":646,"depth":695,"text":647},"https:\u002F\u002Finnovi.pro\u002Fblog\u002Fmcp-vs-webmcp-architecture-guide","2026-11-19","An architectural guide to choosing between backend Model Context Protocol (MCP) servers and in-browser WebMCP tools, covering auth, UI state, security boundaries, and browser readiness.","md","\u002Fblog\u002Fdiagrams\u002Fmcp-vs-webmcp-cover.webp","Architecture guide cover comparing backend MCP servers and in-browser WebMCP tools.","\u002Fblog\u002Fdiagrams\u002Fmcp-vs-webmcp-cover.png",{},"\u002Fblog\u002Fmcp-vs-webmcp-architecture-guide","8 min",{"title":318,"description":704},"blog\u002Fmcp-vs-webmcp-architecture-guide",[715,345,716,717,718],"MCP","AI agents","software architecture","browser tools","summary_large_image","article","jRer3UIkFmv9byEq34yGF8bxObWoNn6JjYQva2ALVOc",1795106537301]