MCP Server

Tools for agentic processing and validation of structured data.

Our CLI includes an mcp subcommand for running a local Model Context Protocol Server, and may be helpful for common, agentic workflows. The local server requires network access to https://api.schemamarkup.app, and relies on file system access to read client-requested files and, in some cases, write results to temporary files.

Experimental Feature

This is an experimental feature that is subject to change or deprecation. We are still evaluating potential integrations with the evolving world of agentic workflows.

Tools

These tools act as lightweight wrappers around the native CLI subcommands and return concise, agent-friendly output. For advanced usage, execute the CLI directly and consider enabling JSON output.

validate_structured_data
convert_structured_data

Installation

First, refer to the CLI Installation section and make sure the schemamarkup command is available from your PATH. Then, configure your MCP client using the following parameters:

Type: stdio
Command: schemamarkup
Arguments:
- mcp

If you have an Access Token for authentication, use an additional argument or environment variable as described in the CLI Authentication section. We do not currently support OAuth Client Credentials.

JSON Configuration

There is not a standard JSON configuration schema, but you may be able to adapt the following snippet for your client. This assumes an authentication token is stored in a file at ~/.config/schemamarkup/access-token.txt.

{ "schemamarkup": {
  "type": "stdio",
  "command": "schemamarkup",
  "args": [
    "--api-token=@~/.config/schemamarkup/access-token.txt",
    "mcp" ] } }