agenticschema: Turn Schema.org Markup into Agent Tools

Overview

AgenticSchema is a TypeScript library that turns Schema.org markup in web pages into callable tools for AI agents. It reads JSON-LD, Microdata, and RDFa already on a page, addressing the gap between sites publishing structured data and agents otherwise having to scrape pages. The project supports browser-based WebMCP registration and Node.js MCP servers, without requiring a backend of its own.

The browser package registers tools on the page, but does not transport them to a separate MCP client. That requires a WebMCP-capable browser, an extension, or a separate relay. The Node.js server can fetch pages and connect directly to MCP clients over stdio.

Key Features

• Extracts structured data from JSON-LD, Microdata, and RDFa.
• Maps entities to read tools, with profiles for common Schema.org types and generic mapping as a fallback.
• Can generate executable tools from eligible potentialAction definitions, subject to same-origin and HTTP method safeguards.
• Provides a browser adapter that registers tools through WebMCP and can watch for page and route changes.
• Includes a Node.js MCP server that fetches pages and exposes entities as both tools and readable resources.
• Offers diagnostics for skipped or malformed data, along with limits on tool count, descriptions, and returned payloads.
• Supports explicitly defined custom tools for capabilities that cannot be derived from page markup.

Use Cases

• A website developer can expose existing product, article, or organization data to browser agents without building a separate API.
• An agent developer can test what tools a real page provides by running the Node.js server against its URL.
• A site owner publishing a SearchAction can make its declared search endpoint callable by an agent, when it passes the project's safety checks.
• A team experimenting with browser agents can register page tools and bridge them to a local MCP client during development.

Getting Started

For a quick Node.js test, run:

npx @agenticschema/server https://en.wikipedia.org/wiki/Backpack

Node.js 20 or later is required for Node-based use. For browser setup, MCP client configuration, options, and security details, see the README.

Considerations

• Project health data classifies it as new and changing fast. Recent activity includes commits and releases, but development is heavily concentrated in one of its two contributors.
• Browser registration and transport are separate concerns. A browser page can have registered tools that a separate MCP client cannot see until a transport is configured.
• Automatically generated actions are intentionally limited to eligible, idempotent actions. Side-effecting actions require explicit custom tools.
• The README identifies rough edges, including read tools for action definitions that may be noise, and notes that structured data can be less token-efficient than extracted text for some page types.
• The README describes security safeguards, but teams should review its threat model and configure allowed hosts and local relay origins carefully before exposing tools to agents.
• The project requires Node.js 20 or later for Node use. The repository reports CI, but no test suite in its requirements data.