Seata 2.6.0 embeds an MCP server in its Console, letting AI clients query and manage distributed transactions via natural language with mandatory confirmation for destructive operations, covering tool categories, security design, setup steps, and real interaction examples.
Apache Seata 2.6.0 introduces an MCP Server in its Console, enabling developers to query global transactions, branch details, global locks, and server logs using natural language via AI clients like Cursor and Claude Desktop, with safety controls requiring human confirmation for write operations.
Postman's latest desktop client silently scans local environments and modifies ~/.claude/settings.json and ~/.codex/config.toml to inject its remote MCP plugin, adding a trust record that bypasses user consent and potentially exposes production tokens, financial accounts, and internal routes to mcp.postman.com.
AI Tool SecurityClaude CodeConfiguration Injection
The article explains why Model Context Protocol (MCP) and workflows alone cannot enforce business rules like parameter provenance, approval validation, idempotency, and result verification, using a procurement example to illustrate the need for explicit Action contracts that define conditions, approvals, and error handling.
Nous Research secured $90M Series B funding to commercialize its open-source Hermes AI agent for enterprises, offering a modular architecture that separates models, tools, and execution environments so companies retain control over their agent systems and accumulated knowledge.
This article explains the Model Context Protocol (MCP) by tracing a complete tool call flow—from tool discovery via tools/list, model intent generation, MCP routing, server execution, to result return—detailing JSON-RPC message formats, stdio and HTTP transports, and the roles of Model, Host, Client, and Server.
This article details the four conditional gates—client capability extension, feature flags, session type, and call origin—that determine whether an MCP tool call becomes a persistent task in Claude Code, explaining why tasks work in terminal CLI but silently degrade in CI, VS Code, or subagents, and provides decision tables for deployment scenarios.
This article explains how RocketMQ LiteTopic solves the task state persistence problem for stateless MCP services by assigning each task a dedicated message channel that acts as an ordered, durable ledger, enabling reliable task tracking, automatic retries, and seamless replica failover without violating the protocol's stateless requirement.
Nous Research raised $90M Series B to commercialize its open-source Hermes Agent for enterprises, offering a decoupled architecture that lets organizations control models, tools, execution environments, and accumulated knowledge while reducing vendor lock-in and migration costs.
This tutorial demonstrates how to integrate enterprise application UIs into Tencent's WorkBuddy AI assistant using MCP Apps, covering the integration rationale, comparison with self-built agents, three integration methods, and a complete CRM example with code for tool registration, UI widget development, and form submission handling.
AI agentsCRM IntegrationEnterprise Application Integration
Nous Research secured $90M Series B funding to commercialize its open-source Hermes AI agent for enterprises, offering a decoupled architecture where organizations control model selection, tool integration, execution environments, and persistent memory/skills to reduce vendor lock-in at the cost of increased engineering ownership.
Arthas 4 introduces an MCP server that lets AI assistants execute Java diagnostic commands like thread, trace, and watch through natural language, enabling developers to troubleshoot JVM issues without memorizing command syntax, with 29 tools across JVM, class loading, monitoring, and utility categories.
This article explains the Model Context Protocol (MCP), its architecture and communication methods, then demonstrates how to build and configure a MySQL-MCP server in Python, integrate it with AI tools like Workbuddy, and use browser automation via MCP for automated testing of web applications.
This article deconstructs AI agent architecture as a stateful runtime chain—Goal→Plan→Context→Decide→Act→Observe→Verify→State→Next—distinguishing Planner, Tool, MCP, Memory, and Reflection as interconnected layers rather than parallel modules, emphasizing that reliability comes from the harness runtime handling verification, recovery, and context engineering outside the model.
This guide explains the Model Context Protocol (MCP), an open standard that solves the M×N integration problem between AI applications and tools by defining three roles (Host, Client, Server), three capability types (Tools, Resources, Prompts), and two transports (stdio, HTTP), with a minimal Python server example and integration steps for Trae, Claude, and Cursor.
The article explains why Spring AI Alibaba's maintenance pause signals mission completion, not abandonment, as Spring AI now natively supports Chinese models via OpenAI-compatible APIs. It argues Java backends remain essential by shifting from writing APIs to organizing capabilities for AI agents through MCP, emphasizing deep business knowledge as the irreplaceable asset.
This article explains the differences between Skill, MCP, and Agent in AI systems using a restaurant analogy: Skills are specialized tools, MCP is a universal protocol for tool integration, and Agents are autonomous decision-makers that orchestrate Skills via MCP to achieve goals.
The article explains the MCP protocol's new Skills extension (SEP-2640), which adds a third capability layer for reusable agent workflows via skills/list, skills/get, and resources/directory/read methods, enabling structured skill discovery, verification, and distribution alongside tools and resources.
The article analyzes three major changes in the latest MCP specification: protocol-level statelessness replacing session IDs, MRTR for multi-turn interactions within a single request, and Tasks extension for long-running backend operations, plus a comparison with A2A protocol for agent interoperability.
In 2026, AI tools like Claude Code and GitHub Copilot Workspace are silently compressing junior tech roles by automating coding, testing, and ops tasks, reducing headcount needs while increasing workload for remaining engineers, making system design, incident judgment, and domain expertise the new irreplaceable skills.
Anthropic's 20-person Labs team uses two-week evaluation cycles to incubate products like Claude Code and MCP, accepting a 20-30% success rate while graduating viable projects to independent teams once they exceed four members, creating a Bell Labs-style engine for turning frontier model capabilities into commercial tools.
This article explains the architecture of large language model applications, distinguishing between simple chat, fixed workflows, autonomous agents, the Model Context Protocol (MCP) for tool integration, and reusable skills, providing a decision framework for choosing the right approach based on task complexity and stability requirements.
This article explains how IntelliJ IDEA's built-in MCP Server (since 2025.2) enables AI coding agents like Codex to directly control the IDE via the Model Context Protocol, allowing them to run configurations, read diagnostics, format code, and debug Spring Boot applications instead of relying on blind command-line builds.
The article analyzes how large language models serve as decision engines but need tool ecosystems as limbs, explains the Model Context Protocol (MCP) as a universal USB‑C‑like standard, details its 2026 stateless revision, showcases enterprise deployments, and introduces the A2A protocol for agent‑to‑agent collaboration.
This article analyzes why traditional one-time authorization fails when AI agents dynamically select and chain tools, proposing a context-aware framework of connection, delegation, and confirmation grounded in MCP specifications and NIST AI risk management to ensure accountable, scoped, and auditable agent actions.
This article argues that MCP tool discovery does not equal authorization, and details an enterprise control plane architecture with capability grants, credential brokers, risk-tiered approvals, and audit evidence chains to safely integrate AI agents into real delivery workflows.
The article argues that while multiple AI agents can independently review test results, true verification still depends on evidence generated by actual hardware runs, because models cannot create or access facts that never existed in the physical environment.
The Model Context Protocol (MCP) released its most extensive revision on July 28, 2026, removing all stateful handshake and session mechanisms, introducing multi‑round‑trip requests, aligning authentication with OAuth 2.0/OIDC, deprecating legacy features, and seeing Anthropic’s Claude be the first product to adapt the new spec.
The article analyzes the shift from Model Context Protocol (MCP) to command‑line interfaces (CLI) for AI agents, detailing MCP’s architectural complexity, token bloat, security risks, and passive tool design, while highlighting CLI’s on‑demand loading, composability, debugging ease, and growing enterprise adoption.
This article provides a systematic deep‑dive into the Model Context Protocol (MCP), explaining its purpose, architecture, core capabilities, data and transport layers, and step‑by‑step guides for building both local and remote MCP servers with Python, while also covering security, permission, and best‑practice recommendations for real‑world AI applications.
The article reviews the arXiv paper on MCP Server architecture, presenting five reusable design patterns and four anti‑patterns, explains the research methodology, shares concrete code examples, and quantifies how tool count affects LLM selection accuracy, offering practical guidelines for building robust MCP Servers.
This tutorial explains the Model Context Protocol (MCP) introduced by Anthropic, showing how its three‑layer Host/Client/Server architecture and six primitives turn Harness into a standardized, USB‑like interface for connecting any data source or tool to large language models, with concrete examples, transport choices, and step‑by‑step implementation guidance.
Apple’s Safari 247 preview embeds a Model Context Protocol (MCP) server with 16 built‑in tools that let any MCP‑compatible AI agent capture screenshots, inspect the DOM, run JavaScript, monitor network traffic and more, while keeping all data local and offering a privacy‑first architecture that signals a shift toward platform‑level AI integration.
Claude Code, an AI agent that reads code and interacts with tools via the Model Context Protocol, enables QA teams to auto‑generate test cases, conduct exploratory Playwright testing, retain evidence for compliance, perform risk‑based impact analysis, maintain tests after code changes, and close the bug‑to‑regression loop.
The article explains MCP (Model Context Protocol) as a standardized interface for AI agents, detailing its architecture (Host, Client, Server), three core types (Tools, Resources, Prompts), transport options (Stdio and Streamable HTTP), security best practices, and how it differs from function calling.
The article explains Claude Code's Model Context Protocol (MCP), how to connect external servers, the hidden costs and trust implications, the tool‑search lazy‑loading mechanism that prevents context overload, and the three security risks you must manage, all illustrated with real‑world examples and a four‑step interview answer.
This article explains how the Model Context Protocol (MCP) standardizes AI model access to external tools like file systems, databases, and browsers, showing how to integrate ready‑made MCP servers with Spring AI, expose your own tools as MCP servers, and choose between stdio and SSE transports.
Unsloth now lets locally‑run large language models act as real agents by exposing a Model Context Protocol (MCP) interface through a no‑code Studio UI or a llama.cpp + mcp‑cli command line, supporting tool calling, file access, web search, and multi‑model connections with detailed setup steps, hardware guidance, and security cautions.
The article explains how the Model Context Protocol (MCP) lets AI tools like Cursor read PRDs, generate validated Midscene YAML test cases, and upload them to the HAL‑9000 platform through a unified three‑primitive architecture, choosing stdio or HTTP transport, while ensuring security and scalability.
MCP, the Model Context Protocol released by Anthropic and now an open standard, provides a universal USB‑C‑like interface that lets AI tools connect to external services through a single set of adapters, reducing integration complexity from O(N×M) to O(N+M) and enabling scalable, plug‑and‑play AI capabilities.
This article compares Model Context Protocol (MCP) and OpenAI‑style Function Calling, explaining their fundamental differences, runtime architectures, capability scopes, ecosystem effects, and providing concrete scenarios and a decision tree to help developers pick the most suitable approach for their AI applications.
The article analyzes why connecting an MCP server can triple response latency and token usage, explains how unstable tool ordering breaks Anthropic's prompt cache, and provides detailed code walkthroughs, design insights, common pitfalls, and concrete best‑practice recommendations for building reliable MCP integrations.
The article introduces seven essential Model Context Protocol (MCP) servers—Filesystem, Git, Fetch, Memory, Sequential Thinking, Time, and MCP Apps—explaining their configurations, practical use cases, and security tips, showing how each can significantly boost AI workflow efficiency.
The article introduces the Model Context Protocol (MCP), an open standard that unifies AI‑to‑external‑system communication like a USB‑C connector, explains its core concepts and roles, walks through building a Python weather server with FastMCP, and outlines the growing ecosystem of MCP servers and apps.
The Model Context Protocol (MCP) embeds every tool’s description into an LLM’s context window, creating a structural “Context Poisoning” vulnerability that lets malicious or bloated tool metadata hijack agent reasoning, inflate tokens, and bypass traditional input validation.
The 2026 Agent Skills whitepaper, officially released by the算泥 community, analyzes the evolution of prompting, function calling, the Model Context Protocol (MCP), core limitations of current AI agents, and the rapid expansion of the Agent Skills ecosystem across coding and non‑coding scenarios.
Tencent's Kuikly team introduces Kuikly AI, a Harness Engineering foundation for cross-platform development that addresses AI code quality and client complexity challenges through open-sourced Rules for framework conventions and Skills for scenario-specific AI agents, alongside MCP, design-to-code, preview tools, and migration agents.
In early 2026 the AI community witnessed a sharp shift away from Model Context Protocol (MCP) toward CLI‑first approaches, driven by token‑cost inflation, fragmented authentication, and loss of composability, with developers favoring the lightweight, text‑based nature of command‑line tools for building robust agent pipelines.
This article introduces Spring AI, explains its purpose as a standardized Java framework for AI integration, highlights the new Model Context Protocol and expanded model support in version 1.1 GA, and provides a step‑by‑step tutorial—including dependencies, configuration, and code examples—to help developers quickly build AI‑powered applications.
The article analyzes how AI has shifted from a code‑completion add‑on to an integral part of software engineering, highlighting the rise of intelligent agents, the Model Context Protocol standard, trust concerns, the move from "vibe coding" to verification‑first practices, and the evolving skill set required of developers and teams.
The article traces the evolution from early function calls to Tool Calling 2.0, explaining how Model Context Protocol standardizes tool interfaces, how Agent‑to‑Agent communication enables multi‑AI collaboration, and how Skills combine tool orchestration into autonomous workflows, while also discussing remaining challenges such as intent misinterpretation and security risks.
The article explains MCP (Model Context Protocol) as a standardized interface for AI applications to access external data sources and tools, compares it with function calling, outlines its security considerations, architecture, resource types, and transport options such as Stdio and Streamable HTTP.
Although the Model Context Protocol (MCP) was launched by Anthropic in late 2024 and initially praised, users now report severe context‑window costs, instability, and cumbersome authentication, leading Perplexity and others to abandon it in favor of traditional CLI tools that remain more composable and reliable.
This article breaks down Anthropic's four‑layer AI Agent architecture, explains when multi‑Agent setups are worthwhile, details how to design reusable Skills and a standardized MCP connection protocol, and provides a practical checklist and a ready‑to‑use Skill template for immediate implementation.
This step‑by‑step guide shows how to activate the McDonald’s Model Context Protocol (MCP), integrate it into Cherry Studio, install Claude Code support, and use AI commands to automatically retrieve and claim McDonald’s coupons.
The article demonstrates how CodeGenie uses MCP to connect external knowledge bases and Rules to enforce ArkTS standards, enabling AI to detect deprecated APIs, retrieve official docs, and generate compliant HarmonyOS code through a four-step workflow.
Claude’s new Interactive Tools, powered by the Model Context Protocol, embed Slack, Figma, Asana and other SaaS UIs directly in the chat, letting users draft, preview, and send messages or generate FigJam diagrams without leaving the conversation, though the feature is limited to paid plans and raises trust and privacy concerns.
The article breaks down Claude Code’s six building blocks—Subagents, Skills, Model Context Protocol (MCP), Slash Commands, Hooks, and Plugins—detailing their characteristics, execution methods, programmability, complexity, autonomy, use cases, customization difficulty, persistence, and integration patterns, and concludes with a comparative matrix and key distinctions.
This article analytically compares Skills (brain‑level expertise) and MCP (external tool interface) for building AI agents, detailing their architectures, development effort, scalability, security, and real‑world use cases, and provides a decision framework to help engineers select the optimal combination.
This article provides a detailed, source‑code‑level analysis of Spring AI’s Model Context Protocol (MCP) implementation, covering its layered architecture, core client‑server interaction steps, key components, runtime debugging with SSE, and practical code examples for building and testing MCP services in Java.
MCP (Model Context Protocol) is an open standard that lets AI applications connect to external systems through a unified client‑server model, exposing Tools, Resources, and Prompts, while addressing security, permission, and audit concerns to make large‑model deployments more reusable and controllable.
AI IntegrationModel Context ProtocolProtocol Design
This article introduces the Model Context Protocol (MCP), a universal standard that lets large language models seamlessly connect to databases, APIs, local files, and third‑party services, explains its architecture, core primitives, practical Python implementation, trade‑offs, security considerations, and how it compares with other integration approaches.
One year after its launch, the Model Context Protocol (MCP) receives a patch-heavy update adding Task abstraction, client-metadata registration, security hardening, and server-side sampling, while the newer A2A protocol offers bidirectional, asynchronous, secure, and extensible multi-agent communication, marking a paradigm shift in agentic AI.
The article introduces the Model Context Protocol (MCP), an open Anthropic standard that creates a secure, standardized, bidirectional bridge between large language models and external tools, then walks through its architecture, core components, Python server and client code, OpenAI integration, usage flow, ecosystem and future outlook.
Anthropic has transferred its Model Context Protocol to the Linux Foundation, creating the Agentic AI Foundation with co‑founders Anthropic, Block and OpenAI and backing from Google, Microsoft, AWS and others, turning MCP into a neutral, open‑source standard that lets any AI model plug into data sources like a USB‑C connector.
This article provides a comprehensive technical overview of the Model Context Protocol (MCP), an open‑standard JSON‑RPC 2.0 protocol that enables large language models to securely interact with external data sources, tools, and services, detailing its design, architecture, Python SDK implementation, transport mechanisms, and real‑world deployment examples such as the DW‑DBA‑MCP project.
Celebrating one year since its debut, Anthropic’s Model Context Protocol (MCP) releases a major update that introduces task‑based workflows, URL‑based OAuth client registration, enhanced security requirements, extensible components, and a suite of new features aimed at improving reliability, observability, and developer flexibility.
This article explains the fundamentals of AI‑generated content (AIGC), the Retrieval‑Augmented Generation (RAG) technique, Function Calling, autonomous agents, and the Model Context Protocol (MCP), highlighting their evolution, technical workflows, limitations, and real‑world examples for developers.
Block, a fintech giant, deployed AI agents across all 12,000 staff in eight weeks by adopting the Model Context Protocol, simplifying installation, offering model choice, automating tool management, and building a supportive community, revealing key lessons for enterprise AI adoption.
This article explains the Model Context Protocol (MCP) – an open, universal standard that lets large language models seamlessly interact with external tools and data – covering its core architecture, why it’s needed, underlying principles, tool‑selection mechanics, a step‑by‑step Python server implementation, and practical usage tips.
This article introduces the Model Context Protocol (MCP) Go SDK v1.0.0, explains its stable API guarantees, provides quick‑start examples for building MCP servers and clients in Go, and outlines the SDK's modular design and error‑handling strategy for AI‑enabled backend development.
This article explains how BaikalDB leverages the Model Context Protocol to let large language models query and analyze its distributed database without writing any code, detailing the protocol’s principles, server components, transport methods, tool capabilities, use cases, configuration, and future challenges.
This tutorial introduces Claude Code’s Model Context Protocol (MCP), compares it with traditional function calling, explains its client‑server architecture, and provides a step‑by‑step hands‑on guide—including Figma token acquisition, server setup, and Flutter code generation—to demonstrate how MCP streamlines AI‑driven development.
This article debunks common misconceptions about the Model Context Protocol (MCP), explains its client‑host‑server (CHS) architecture, shows how the Host drives AI decisions while Server and Client remain model‑agnostic, compares MCP with Function Calling, analyzes SDK source code, evaluates practical trade‑offs, and outlines the true engineering value and costs of using MCP in AI applications.
This article explains the Model Context Protocol (MCP) as an open standard for secure AI‑tool interaction, details its client‑server architecture, showcases a Figma‑focused MCP implementation with code examples, and discusses data simplification, transformers, and image handling that enable AI assistants to generate accurate front‑end code from design files.
This article defines the Model Context Protocol (MCP), explains why it is needed to unify LLM and external tool interactions, details its client‑host‑server architecture, compares its communication modes, outlines Java/Spring AI support, and discusses current adoption trends and open challenges.
This article explains the Model Context Protocol (MCP) introduced by Anthropic, compares it with Function Call, details its architecture and communication flow, and provides a step‑by‑step Spring AI guide—including server and client development, configuration, code examples, and testing—so developers can integrate AI models with back‑end services efficiently.
This guide explains what the Model Context Protocol (MCP) is, lists key MCP resources, and provides a step‑by‑step tutorial for creating a token, linking a Figma design, configuring Cursor, and using MCP to automatically generate front‑end HTML and Tailwind CSS from a Figma file.
This article explains the Model Context Protocol (MCP) architecture, demonstrates how to build an MCP service for fetching Figma design data, details the data simplification pipeline, and shows how AI assistants can use standardized, secure context to generate accurate code from design files.
The article introduces shadcn‑ui‑mcp‑server, a Node.js tool that implements a Model Context Protocol to let AI assistants read shadcn/ui component documentation, source code, and demos, enabling richer code suggestions and full‑page layout generation within editors like VS Code, Continue, and Cursor.
The Model Context Protocol (MCP) is an open‑source interface that standardizes how large language models interact with external data sources and tools, offering a USB‑C‑like universal connector for AI applications, with built‑in session management, security, and flexible HTTP/SSE transport for seamless real‑world integration.
This article explains how the Model Context Protocol (MCP) solves the AI integration "M×N" problem by providing a universal language for AI applications and tools, outlines its technical principles, showcases practical case studies, and promotes the accompanying book that teaches MCP from theory to implementation.
This article explains why the Model Context Protocol (MCP) is needed for LLMs, describes its client‑server architecture, data and transport layers, and provides step‑by‑step Python examples for creating both an MCP server and a client using FastMCP and low‑level APIs.
This article demystifies the Model Context Protocol (MCP) by walking through a practical fetch-mcp example, then detailing the JSON-RPC 2.0 application layer interactions — initialization, tool listing, and tool calling — and comparing STDIO versus Streamable HTTP transport layers for remote MCP server communication.
This article explains how Volcanic Engine safeguards the Model Context Protocol (MCP) throughout its lifecycle, detailing MCP fundamentals, core components, a step‑by‑step interaction example, seven major security risks, official design principles, and a comprehensive security architecture covering admission control, native design, and runtime protection.
An in‑depth guide outlines the nine core technologies—ranging from autonomous agent fundamentals and multi‑agent collaboration to workflow orchestration, retrieval‑augmented generation, fine‑tuning, function calling, model context protocols, agent‑to‑agent communication, and AI‑driven UI—required to design, deploy, and scale enterprise‑grade AI agents.
This article introduces the Model Context Protocol (MCP), explains its core advantages such as capability expansion, standardized interfaces, and low‑code integration, and demonstrates a practical Sentry‑MCP implementation with Python code, detailed functions, and visual results for AI‑driven data access.
The Model Context Protocol (MCP) is an open, standardized adapter that lets large language models seamlessly connect to tools, data sources, and workflows, offering plug‑and‑play intelligence, cross‑platform compatibility, security, and modular extensibility for building real‑world AI applications.
The article explains the Model Context Protocol (MCP) as a zero‑code bridge that lets large language models seamlessly access databases, external APIs, and execute code, detailing its benefits for developers and everyday users, its core components, step‑by‑step workflow, real‑world examples, and how it outperforms traditional APIs in modern AI agent systems.
The article introduces Model Context Protocol (MCP), explains its architecture of Host, Client, and Server, describes its components—Resources, Tools, Prompts—and demonstrates practical integration with IDE plugins to extend LLM capabilities such as real‑time ticket queries, highlighting its significance for AI development.
This guide shows how to integrate Spring Boot with the Model Context Protocol (MCP) to let large language models interact with existing services via natural language, covering entity definitions, Maven dependencies, configuration, tool annotations, and testing to create an AI‑enabled book management API.
This article explains how the Model Context Protocol (MCP) standardizes AI agent communication with external tools, outlines its benefits, describes its core components, showcases open‑source implementations, and provides step‑by‑step Python examples for building MCP servers and clients.
This article critically examines the rise of Model Context Protocol (MCP) in AI, explaining its purpose as a unified tool‑calling standard, detailing its architecture, comparing it with traditional function calls, and evaluating the technical and market challenges that limit its universal applicability.
This article explains the Model Context Protocol (MCP), an open standard that lets AI models, tools, and agents share context and communicate through a central server, detailing its definition, key components, workflow, benefits for developers, and real‑world examples.
This article systematically analyzes the security threats of the Model Context Protocol (MCP) ecosystem—including supply‑chain poisoning, backdoors, tool‑description injection, malicious updates, cloud‑service abuse, installer vulnerabilities, and open‑source risks—and proposes concrete governance measures and early‑stage implementations to help enterprises secure MCP deployments and operations.
The Model Context Protocol (MCP) is an open, client‑server protocol introduced by Anthropic that standardizes how applications provide context to large language models, offering a USB‑C‑like interface for tools, data sources, and services to enable reliable, extensible, and secure AI interactions.
This article walks through the Model Context Protocol (MCP) concepts, demonstrates how Cursor leverages Docs and Rules to develop a weather‑service MCP server in TypeScript, explores a gold‑price prediction project, and shares practical tips, advantages, and limitations of AI‑assisted coding.
This article explains the Model Context Protocol (MCP) for AI development, detailing its definition, core components, communication methods, execution process, relationship with agents and function calling, ecosystem growth, and future implications and challenges.
This article explains why current AI models struggle to cooperate, introduces the Model Context Protocol (MCP) as a universal “translation standard” for AI interoperability, and outlines its core features, practical benefits, limitations, and steps developers and users should take to adopt it.