# SHAR Production Metadata MCP [Health: Active]

**Category:** 🎥 Multimedia Process  
**Repository:** https://github.com/SHARProduction/production-metadata-mcp  
**GitHub Stars:** 0  
**Views:** 6  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/shar-production-metadata-mcp

## Description
Read-only local MCP validation for rights-aware production metadata manifests.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "shar-production-metadata-mcp": {
    "command": "npx",
    "args": ["-y","shar-production-metadata-mcp"]
  }
}
```

## Documentation

## What SHAR Production Metadata MCP MCP server does

SHAR Production Metadata MCP MCP server provides one read-only MCP tool: `validate_production_manifest`. The tool receives a production metadata manifest as an object and evaluates it for releasability. This makes it suitable for agents or MCP-compatible clients that need to check metadata before a production asset is released.

The project is focused on rights-aware metadata rather than media processing. It validates the manifest contract and applies the releasability policy described by the project. The README specifically distinguishes structural validity from the policy outcome when `rights_status=unknown`, so callers should treat those as separate aspects of the result rather than assuming a structurally valid manifest is always releasable.

## How it works

The server runs locally and exposes the validation tool through MCP. A client submits a manifest object to `validate_production_manifest`; the server returns a releasability result. It does not publish the submitted data or perform external lookups.

SHAR Production Metadata MCP MCP server does not read local files and does not make network calls. The caller therefore needs to provide the manifest object directly. This behavior keeps validation limited to the supplied metadata and avoids requiring access to a filesystem, remote service, or publishing destination.

A machine-readable JSON Schema is included at `schema/production-manifest.schema.json`. The schema describes the structural contract and mirrors the fields used by the validator. It can be used to understand the expected manifest shape before integrating the tool into an agent workflow.

## Setup and configuration

The repository documents a Node.js installation and startup flow:

```bash
npm install
npm start
```

Run these commands from a checked-out copy of the repository. The provided material does not list environment variables, API credentials, hosted endpoints, or additional configuration settings. Because the server is local and does not call networks, no external service setup is described.

## Tools and capabilities

- Exposes `validate_production_manifest` through MCP.
- Accepts a production manifest object.
- Checks the manifest against the project’s structural contract.
- Returns a releasability result.
- Handles structural validity separately from the policy for `rights_status=unknown`.
- Operates in read-only mode.

## Limitations and notes

SHAR Production Metadata MCP MCP server validates metadata only. The provided material does not describe video editing, media inspection, rights acquisition, publishing, or storage capabilities. It cannot read a manifest from a local file on behalf of the caller, because local file access is explicitly excluded; the client must provide the object to the tool.

The server also does not contact external systems or publish results. Any workflow that needs those operations must handle them outside this server. The repository is MIT-licensed, and the available documentation identifies MCP-compatible clients generally without naming particular desktop or editor clients.

_Full upstream README: https://allmcps.com/mcp/shar-production-metadata-mcp/readme_