platform-truth-mcp

Set up a local read-only MCP gateway for platform truth and JIRA metadata.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/javierhbr/random-poc --skill platform-truth-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-truth-mcp
Source: https://github.com/javierhbr/random-poc/tree/main/custom-skills/sdd/platform-truth-mcp-codex-skill
Command: npx skills add https://github.com/javierhbr/random-poc --skill platform-truth-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and rules (resource) components.

What problem does it solve?

This Skill provides a local, read-only MCP gateway, enabling component teams to access canonical platform truth and JIRA-linked metadata without relying on hosted infrastructure.

Core Features & Use Cases

  • Local MCP Server: Set up a read-only MCP server that reads from a local platform repository clone.
  • Component Alignment Validation: Facilitate component teams in querying and validating their alignment with platform standards.
  • JIRA Metadata Integration: Expose JIRA mapping without making JIRA the primary source of truth.
  • Use Case: A component team needs to ensure their service adheres to the latest platform API specifications. They use this skill to query the local platform truth and validate their component's configuration against it, referencing JIRA tickets for specific requirements.

Quick Start

Use the platform-truth-mcp skill to validate component alignment against the pinned platform version.

Frequently Asked Questions about platform-truth-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate component alignment against platform truth without hosted infrastructure?

You can validate component alignment locally by setting up a read-only MCP gateway that queries a local platform repository clone, enforcing default validation against pinned platform versions.

Can I query JIRA metadata locally without making JIRA the primary source of truth?

Yes, local MCP integration can expose JIRA-linked metadata for querying while enforcing the local platform repository clone as the canonical source of truth.

Does component alignment validation work with a read-only local platform repository?

Yes, component alignment validation operates strictly against a local, read-only platform repository clone to ensure safe querying of canonical platform truth.

What is the best way to access canonical platform truth offline?

The best way to access canonical platform truth offline is establishing a local MCP server that reads directly from your local platform repository clone.

Why does local MCP enforce read-only access for platform metadata?

Local MCP enforces read-only access to prevent accidental modifications to the canonical platform repository clone, ensuring validation queries return reliable, unaltered platform truth.

Do I need a local platform repository clone to use local MCP for validation?

Yes, you need a local platform repository clone because the local MCP server reads canonical platform truth and pinned versions directly from it to perform validation.