As a developer I need to review the current PF MCP collection template format to see if it can be applied to external collections.
Acceptance criteria
-
Viability research and potential POC
- formatting and ingesting handbook markdown into a parsable format, like JSON
- review the formats used in the related PF MCP collections, metadata appears open with a few core requirements. Review the typings associated with the existing collections
- a generation script, JS or shell can be considered
- review and roughly establish the needed handbook metadata that can both be gathered by directory structure and yaml frontmatter
- this may need compare/contrast with
docs.json within the PF MCP, for reference or as a model
- using the PF MCP collections tuple format to ingest said JSON, or other determined format
- ingesting the collection format itself into the PF MCP
- need to confirm if either "collections-as-plugins" or embedding the PF MCP server with collections is available.
-
Open a formalized issue, or issues, for incorporating handbook data/docs into the PF MCP
- Reference any POC work created by this research story
Assumptions and questions
Jira Issue: PF-4564
As a developer I need to review the current PF MCP collection template format to see if it can be applied to external collections.
Acceptance criteria
Viability research and potential POC
docs.jsonwithin the PF MCP, for reference or as a modelOpen a formalized issue, or issues, for incorporating handbook data/docs into the PF MCP
Assumptions and questions
Work that would help with this research
Existing collection templates
docs.jsonfileJira Issue: PF-4564