Tenant-scoped, read-only MCP access to pending Shopify optimization work.
The taskerarmy mcp server has a specific public responsibility.
The page explains tenant-scoped, read-only findings, job context and evidence for compatible clients without presenting internal infrastructure or unshipped capabilities as customer-ready product.
Expose durable product concepts instead of internal implementation details.
Stores, findings, jobs, states, evidence and authorized actions create a safer contract than database tables or UI scraping.
Document revocable credentials, stable tools, client setup and explicit limitations.
Developers need enough detail to build reliable workflows and enough boundaries to avoid creating unsafe shortcuts.
Every request and handoff remains tenant-aware and attributable.
Authorization is enforced server-side and support or administrative access is recorded with actor, purpose and time.
Developer surfaces remain subordinate to the release model.
External clients and integrations can extend context, but they do not silently change production or erase the approval trail.
Avoid theme publishing, production approval or cross-tenant access.
Availability, beta status and escalation conditions should be written plainly so buyers and developers can choose the correct path.
Related TaskerArmy pages
Connect the store. Start with evidence.
Connect your store, review the audit and choose the first change you want TaskerArmy to prepare in staging.