Schema Frameworks MCP Server

Ask a chat assistant to build schema markup for a page. It runs real, tested builders on the page's own data, and when the page does not qualify it outputs nothing and says which field stopped it.

Add It To Your Assistant

  • Claude
  • ChatGPT
  • Gemini
  • Grok
  • Perplexity
  • Le Chat
  • Meta Muse
  • Manus
  • Copilot
# Connector address
https://mcp.jakelabate.com/schema-frameworks
# Then ask
Find the schema framework that fits my page and tell me what it builds. Ask me for the page URL first.

No sign-in. Every tool only reads.

40

Frameworks

One per Google structured data feature.

12

Page types

Each a whole page in one linked graph.

1,558

Test cases

The builders pass them before a page is published.

867

Rules and rows

Google's rules and property rows, each with its own link.

How To Add It

  1. In Claude, open Customize, then Connectors, choose Add custom connector and paste the address. Claude's own instructions have the details.
  2. In any other assistant that supports MCP, add the address as a remote MCP server.
  3. Ask it about a page. The prompt in the box works as it is copied.

What To Ask

  • "Which framework fits this page?" It lists the 40 frameworks with what each one is for. list_frameworks
  • "My page sells one jacket in several sizes. What does it need?" It finds the frameworks and page types that fit the description, with what each one is not for. pick_framework
  • "What markup goes on a product page?" It lists the 12 page types, each one builder for a whole page with its nodes linked by @id. list_page_types
  • "What does Recipe markup need?" It returns Google's rules, the checks the builder runs and every input field. get_framework
  • "Build Recipe schema for this page." It runs the real builder on the page's data and checks the result against Google's rules. build_schema
  • "Why did it output nothing?" It names the fields and the checks that stopped it. build_schema
  • "Give me the Python builder." It returns the source with its file on GitHub. get_builder_code
  • "Is this JSON-LD valid?" It checks any markup against Google's documented rules. validate_schema

When A Page Does Not Qualify

A store page with a town but no street address, sent to build_schema. This is the server's own answer, run when this page was built.

build_schema.jsonJSON
{
  "outcome": "nothing_output",
  "stopped_by": [
    {
      "field": "address",
      "without_it": "Nothing is output.",
      "link": "https://www.jakelabate.com/schema-frameworks/local-business/#input-address",
      "checks_that_read_it": [
        {
          "question": "Has a street address?",
          "link": "https://www.jakelabate.com/schema-frameworks/local-business/#check-5"
        },
        {
          "question": "Has a town or city?",
          "link": "https://www.jakelabate.com/schema-frameworks/local-business/#check-6"
        }
      ]
    }
  ]
}

Each link goes to the exact row or check on the framework's page, so the assistant can cite the line it relies on.

The 7 Tools

  • list_frameworks Lists the 40 schema frameworks, one per Google structured data feature, each with what its markup is for, whether Google has retired the feature, and its page.
  • pick_framework Given a description of a page, returns the frameworks and page types that fit, each with when to use it, what it is not for, and the frameworks that mark up the same schema.org type and get mixed up with it.
  • list_page_types Lists the 12 page types.
  • get_framework Everything about one framework.
  • build_schema Runs a framework's real builder, or a page type's, on the data for one page and returns the JSON-LD, checked against Google's rules.
  • get_builder_code Returns the source code of a framework's builder, in JavaScript or Python, or a page type's in JavaScript, with its file on GitHub.
  • validate_schema Checks any JSON-LD against Google's documented rules for its rich result features.

Where It Comes From

Nothing the server says is typed into it. It is generated from the framework pages, their flowcharts and the validator specs, and redeployed whenever they change. Google's documentation was last checked against the frameworks on Nov 14, 2026.

From Valid Markup To A System

A builder gets one page right. Wiring it to your CMS so every page stays right as content changes, and proving what it earned, is the work. That is what an engagement is for.