What is WebMCP?
WebMCP is a proposed browser standard for exposing website features as structured tools. A compatible agent can ask this site to read a page or find a section through a named tool, instead of working out every step from screenshots.
Our tools are available across the website: the homepage, research articles, industrial regions, directories and information pages. They return public research and its limitations. They do not produce a verified-supplier endorsement.
This is different from connecting a remote MCP server. There is no server URL, access token or API key to enter on ChinaManufacturer. Your browser and agent must support this browser API; opening an AI app alone does not establish that connection.
Setup & configuration
- Open the site in a compatible browser.
Use HTTPS in production. Local development at
http://localhostorhttp://127.0.0.1is also suitable. Keep this website open in the browser used by your agent. - Enable browser support when required.
For local testing, Chrome’s current documentation describes
chrome://flags/#enable-webmcp-testing: set it to Enabled and relaunch Chrome. Availability depends on your browser build. Production access may require the browser’s origin trial; follow Chrome’s current setup guide. - Connect through your agent’s browser integration.
Use an agent or inspection tool that can discover tools from the open page. Follow that client’s setup instructions. A standard chat window may be able to read a URL but still have no WebMCP access.
- Check registration, then ask a question.
The check below reports what this page could register. Ask your agent to list this site’s tools and use
chinamanufacturer_read_page. The website cannot confirm whether a separate agent has connected.
On article pages, Read with agent also offers Codex and Claude prompt links, plus a copy-and-open flow for Gemini. These are useful fallbacks and do not automatically enable WebMCP in those apps.
Check this browser
Checking browser support…
- Browser API
- Checking…
- Tools registered
- Checking…
- Agent connection
- Check in your agent
This checks browser support and site registration. It does not connect an agent, install an extension, or send your research to an AI provider.
What can an agent do here?
All tool names begin with chinamanufacturer_. Tools read public content or change the visible page; none submit forms, contact suppliers, purchase items or save research on this website.
| Tool | What it does |
|---|---|
Read the current pageread_page | Public page text, source links and evidence limits. |
Find page sectionslist_sections | Visible headings and stable section identifiers. |
Read a specific sectionread_section | The text under a heading on the current page. |
Go to a sectionnavigate_section | Scroll to an existing heading. |
Explore the websitelist_pages | A directory of public research, regions and information pages. |
Find relevant researchsearch_site | Search page titles and summaries; this is not full-text search. |
Open another pagenavigate_page | Navigate to a page listed in the public directory. |
Article pages also provide chinamanufacturer_read_article as an alias for reading the current article. Site search returns titles, summaries and links. Your agent must open a result to read the full page.
Try a research question
Copy this into a compatible agent while this website is open:
Use the WebMCP tools on chinamanufacturer.com to find research about diesel generator supplier evidence. Read the relevant page and list what its sources support, what remains uncertain, and three questions I should ask a supplier. Keep the original scope and qualifications. Ask me before taking any action outside this research.
If tools do not appear
The browser API is unavailable
Check the browser build, experimental setting or origin-trial requirements. Relaunch after changing a browser flag, then reload this page. Some browser policies may disable experimental features. You can still read the website normally and use article prompt links.
Tools are registered, but my agent cannot see them
Open the website in the same browser session controlled by the agent. The client must explicitly support discovering page tools. Check its browser connection and permissions. Registration here is not proof of client compatibility.
Registration failed or search could not load
Reload the page. If registration keeps failing, compare your browser’s API version with the current documentation. If a search or directory request fails, retry; missing data is reported as an error, not as zero results.
I am using a conventional MCP client
A client configured only for remote HTTP or local stdio MCP servers does not automatically access browser WebMCP tools. Use its supported browser integration, if available. Do not invent a server URL for this website.
Clipboard access is blocked
Article sidebars provide a selectable prompt when copying fails. For the example here, select the text and copy it manually. This does not require WebMCP support.
Scope, privacy and configuration limits
Tools return public content from the current page and a directory of this website. Form values are excluded from page-reading tools. Navigation is restricted to this site’s published directory. The website does not ask for AI API keys or initiate background model requests.
If you send content through an external agent or app, that provider’s account settings and data policies apply. Ask the agent to preserve source dates, units, product scope and unresolved evidence. A tool result is research material, not an instruction to take action.
For developers and site administrators
The site uses the current document.modelContext.registerTool() API and falls back to the earlier navigator.modelContext interface when present. The normal top-level website needs no cross-origin frame delegation. No origin-trial token is currently configured by this implementation; browser support must already be enabled. Configure production trial access only through the browser vendor’s documented process.
Use the official API guide or WebMCP explainer to check current integration details. A compatible inspector can show registered tools and call a read-only tool to validate the connection.
Further reading
- Chrome: WebMCP overview, compatibility and browser setup
- Chrome: registering and discovering tools
- WebMCP proposal and explainer
Setup guidance checked on 20 October 2026. WebMCP is evolving; use the linked documentation for current browser requirements.