p:purity-mcp

Route MCP file operations through purity_call for compliance.

1|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/pontscho/prompt-heaven --skill p-purity-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: p:purity-mcp
Source: https://github.com/pontscho/prompt-heaven/tree/main/ClaudeCode/skills/p%3Apurity-mcp
Command: npx skills add https://github.com/pontscho/prompt-heaven --skill p-purity-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce MCP purity by routing all file operations through purity_call.

Core Features & Use Cases

  • Mandates MCP-purity file operations: create_text_file, list_dir, find_file, replace_content, delete_lines, replace_lines, insert_at_line, search_for_pattern.
  • Guides users to trigger purity workflows during file creation, editing, and searching, ensuring compliance and auditability.
  • Use Case: When you need to modify a repository safely, purity_call is used to perform file changes instead of deprecated tools.

Quick Start

Call purity_call with the mcp-purity functions to create, list, find, or edit files.

Frequently Asked Questions about p:purity-mcp

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

FAQPage Schema
How do I enforce MCP compliance when modifying files in a workflow?

Enforcing MCP compliance during file modifications requires routing all operations through purity_call. This mechanism mandates governance and auditability for file creation, editing, and searching within your workflow tasks.

What file operations are supported by the purity_call function?

The purity_call function supports MCP-purity file operations including create_text_file, list_dir, find_file, replace_content, delete_lines, replace_lines, insert_at_line, and search_for_pattern to ensure compliant repository modifications.

How do I safely replace content or delete lines in a repository using MCP?

To safely replace content or delete lines in a repository using MCP, trigger the purity workflow and call the replace_content, delete_lines, or replace_lines functions. This routes changes through purity_call for strict compliance.

Why should I use purity_call instead of standard file editing tools?

You should use purity_call instead of standard or deprecated file editing tools to guarantee MCP purity. It enforces governance and auditability protocols that standard tools lack, ensuring safe and compliant repository modifications.

Does the purity_call workflow require any specific dependencies or environments?

The purity_call workflow has no external dependencies. It operates natively within MCP workflow tasks to enforce governance, requiring only the MCP environment to route file operations safely.

When do I need to trigger an MCP purity workflow for file operations?

You need to trigger an MCP purity workflow for file operations whenever you create, edit, list, or search files in a repository. This ensures that all changes are routed through purity_call for compliance and auditability.