List pending optimization work that needs attention.
ContextAuthenticated user connects a compatible MCP client.
ResultRead-only job titles, states and relevant context.
Direct answer
MCP lets power users query approved TaskerArmy work while keeping write authority and production decisions inside the product.
Real requests
Recognizable Shopify work, routed honestly.
The example shows the store need, the relevant context and the result delivered to the team.
Ask the MCP client to publish a staged theme.
Contextcontrol over publishing is intentionally excluded.
ResultRequest remains unsupported inside MCP.
Disconnect an old client.
ContextUser removes or revokes the MCP credential.
ResultFurther access stops without changing Shopify state.
Status, Available
The current MCP surface is intentionally narrow.
It exposes the supported read-only context documented by TaskerArmy rather than presenting an unrestricted tool server.
Tenant scope
Resolve the account from the authenticated connection.
Model input does not choose an arbitrary tenant, which reduces the risk of cross-account access.
Read-only behavior
Inspect context without modifying the store.
The integration does not deploy code, publish a theme or act as a substitute approval surface.
Stable objects
Return understandable work states and identifiers.
Store, finding, job, status and evidence should remain consistent enough for clients to use safely.
Credential handling
Keep Shopify tokens and internal secrets out of tool output.
The external client receives only the context required for the authorized MCP capability.
Revocation
Allow the user to remove the connection.
The setup documentation should identify where the connection is managed and what confirms that access has been revoked.
Continue exploring
Related TaskerArmy pages
Questions
Direct answers before installation
Can MCP deploy or publish changes?
No. The current public MCP capability is read-only and does not provide control over publishing.
Can the model choose another tenant?
The integration is designed to resolve tenant scope from authentication rather than accepting an arbitrary tenant from model input.
Where is the connection configured?
Authenticated users manage the supported MCP setup through the TaskerArmy dashboard documentation and connection surface.
Next step
Add read-only context to the tools your technical team uses.
Keep implementation and approval in TaskerArmy while compatible clients help users inspect the queue.