Help us improve
Share bugs, ideas, or general feedback.
From tool-integrations
Use when designing or reviewing filesystem MCP access, path boundaries, allowed roots, method allowlists, and safe local file operations.
npx claudepluginhub yeaight7/agent-powerups --plugin tool-integrationsHow this skill is triggered — by the user, by Claude, or both
Slash command
/tool-integrations:filesystem-mcp-guardrailsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This is a conceptual document for a Filesystem MCP server configuration. It is NOT a runnable configuration file. The earlier research used a Go-based filesystem MCP shape; this skill keeps only the safety model.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
This is a conceptual document for a Filesystem MCP server configuration. It is NOT a runnable configuration file. The earlier research used a Go-based filesystem MCP shape; this skill keeps only the safety model.
When packaged as a true Agent Powerup, this will provide guidance on configuring and safely running local filesystem MCP servers.
Use when the agent needs structured, protocol-driven access to the local filesystem beyond its native capabilities, or when integrating external tools that require filesystem access via MCP.
Before this becomes a shipped MCP config:
apx mcp check metadata and dry-run install behavior.references/path-boundary-checklist.md