feat(magento): use connection-level Authorization token instead of form field

[JonasJesus42]

Summary

• Removes apiToken from the Magento MCP connection form (configSchema and StateSchema) — users now enter their Magento integration token in the encrypted Token field of the HTTP connection instead.
• resolveCredentials now accepts the full MESH_REQUEST_CONTEXT and extracts the API token from ctx.authorization (stripping the Bearer prefix), with MAGENTO_API_TOKEN env var as a local dev fallback.
• All 7 tool files updated to pass env.MESH_REQUEST_CONTEXT directly instead of env.MESH_REQUEST_CONTEXT?.state.

This aligns the Magento MCP with the pattern used by Strapi, HyperDX, and Discord MCPs in this repo, where the connection-level token (encrypted at rest) is used as the downstream API key.

🤖 Generated with Claude Code

---

Summary by cubic

Switch Magento MCP to use the HTTP connection’s Authorization token instead of the apiToken form field. This simplifies setup, encrypts the token at rest, and aligns with our other MCPs.

• Refactors

  • Read the API token from MESH_REQUEST_CONTEXT.authorization (strips Bearer), with MAGENTO_API_TOKEN as a local fallback.
  • Removed apiToken from configSchema/StateSchema; updated all tools to pass the full MESH_REQUEST_CONTEXT.

• Migration

  • Set your Magento integration token in the HTTP connection’s Token field.
  • Remove any apiToken from existing Magento connections; keep baseUrl only.
  • For local dev without a connection token, set the MAGENTO_API_TOKEN env var.

^{Written for commit a14faf6. Summary will update on new commits.}