Keep Secrets in APX Runtime, Not in APC
📰 Dev.to AI
Learn to separate secrets and portable project context in APC and APX for better MCP storage management
Action Steps
- Identify sensitive data in your project
- Move secrets to APX runtime for local storage
- Keep portable project context in APC
- Configure MCP storage to respect this separation
- Test your setup to ensure secrets are not committed
Who Needs to Know This
Developers and DevOps engineers can benefit from this distinction to keep sensitive information secure and ensure seamless collaboration
Key Insight
💡 Separate portable project context from machine-local runtime state for secure MCP storage
Share This
Keep secrets safe in APX runtime, not APC!
Key Takeaways
Learn to separate secrets and portable project context in APC and APX for better MCP storage management
Full Article
Keep Secrets in APX Runtime, Not in APC The cleanest way to think about APC and APX is this: APC is for portable project context, APX is for machine-local runtime state . Once you hold that line, MCP storage becomes much easier to reason about. The rule is simple: if the data is safe to commit and useful to every clone of the repo, it belongs in APC. If it contains secrets, machine-specific paths, or anything that should stay local, it belongs in APX runtime
DeepCamp AI