Connections that extend the customer workflow—not internal vendor plumbing.
Explore Shopify, MCP, Claude Desktop and Slack integrations with clear availability states.
Connect the engineering workflow to systems merchants and developers actively use.
Integrations represent a connection the merchant or developer can understand and use.
The public hub includes Shopify, MCP, Claude Desktop and Slack. Hosting, transactional email, billing processors and databases belong in security, privacy or subprocessor disclosures.
Available: store connection through OAuth.
Shopify supplies store identity, authorization and theme context for the audit and engineering workflow.
Available for compatible power-user clients.
MCP exposes tenant-scoped, read-only TaskerArmy context without granting production authority.
Available through the MCP connection.
Claude Desktop can query approved TaskerArmy context after the user completes the documented connection flow.
Availability must match the production integration state.
When enabled, Slack messages should describe job state, required action and a safe deep link—not generic AI completion language.
Connections that extend the customer workflow—not internal vendor plumbing. resources
Related TaskerArmy pages
Direct answers before installation
Why are Stripe and Resend not listed as integrations?
They are internal infrastructure providers, not customer-configurable TaskerArmy integrations. Relevant use belongs in privacy, security or subprocessor documentation.
Connect the store. Start with evidence.
Run the connected-store audit, review prioritized findings and decide which bounded engineering job should move to staging first.