Use eComrads with any AI

This page currently supports Claude, Perplexity, OpenClaw, and Hermes for MCP-based access, plus Claude Code, and Codex-style local agent flows through the Skill setup.

Because the context stays intact. Your product references, brand direction, and follow-up edits remain in one thread while Ecomrads routes the work into the right workflow behind the scenes.

No. Most setups are connector-based or prompt-based. The goal is operational simplicity, not a developer-heavy integration process.

Not for normal MCP usage. The standard flow is connector-based or prompt-based authentication through your Ecomrads account, rather than manually managing an API key.

You can trigger Ecomrads workflows such as product photoshoots, storyboards, static ads, and other creative production tasks without leaving the conversation. The goal is to keep ideation, refinement, and execution in one thread.

Usually no. After the initial authorization, the connection should remain available until you revoke access, sign out, or the client asks you to re-authenticate.

Yes. You can authorize the same Ecomrads account in multiple supported clients if you want to work across different environments such as Claude, Perplexity, or local agent workflows.

The fastest fix is to reconnect the MCP server or repeat the authorization flow. Most issues come from expired sessions, revoked permissions, or a client-side connector state that needs to be refreshed.

Yes. MCP is the connector-style route for supported clients, while the skill flow is meant for local agent environments such as Codex-style setups or Claude Code workflows where you want Ecomrads available through locally installed skills.

That is the main advantage. Your references, prompts, follow-up edits, and workflow decisions stay inside the same conversation, so you do not need to re-brief the tool every time you want a new variation or revision.