4 ms·
Show HN: AutoManus MCP Server – create a sales rep agent from Claude in 1 min [video]
Hi HN, I’m Sean, founder of AutoManus.
We just released an MCP server + REST API that lets you create a sales representative agent for any business, directly from Claude Desktop or Cursor.
The idea is simple: every AI product/agency/business needs a way to talk to customers, and you don’t want to build that layer from scratch every time. You want a sales layer, the sales interface to speak to the world.
With the MCP server you can say:
“Create a sales representative agent for my business”
Then you provide:
company name
website URL
email
AutoManus will:
research the website and build a knowledge base
create the agent in under 1 minute
give you a WhatsApp + webchat link to test
Ownership + security:
you claim the agent via an emailed claim link
domain verification prevents someone from impersonating your company on WhatsApp
It also turns conversations into structured leads and follow up todos in the hub.
If you’re a developer, the REST API lets you create agents directly into your agent hub using an API key, no claim flow needed.
Repo: github.com/automanus-io/mcp-server
NPM: npmjs.com/package/@automanus/mcp-server
Docs: automanus.io/docs/mcp
Would love feedback.
- matrixgard 7mo agoThe one-minute setup is a strong pitch for the demo, but I'm curious what happens when the agent hits an edge case it wasn't trained on — does it gracefully defer to a human or does it just hallucinate a confident wrong answer? That's the moment that kills trust with customers, especially in the first few weeks of deployment. The WhatsApp integration is smart — that's where most SMB customer conversations actually happen in a lot of markets outside the US. What does the handoff flow look like if a conversation escalates beyond what the agent can handle? Are you targeting businesses that already have a sales process and want to automate it, or founders who are pre-sales-motion and trying to figure out how to talk to customers at all?
- ShenSeanChen 7mo agoGreat questions. On edge cases: the agent doesn't try to "fake" answers. If it doesn't have enough context from the website/knowledge base, it asks follow-up questions or flags the conversation as needing human review. We're also adding explicit escalation rules so certain intents immediately route to a human. For handoff: the idea is that the agent handles the early conversation layer (answering questions, capturing requirements, qualifying). If the conversation becomes complex, the thread can be handed to a human with the full conversation history and extracted lead data. On ICP: today we're mostly seeing traction with businesses that already receive inbound inquiries (often on WhatsApp) but don't have a structured way to capture or follow up on them. The agent sits in front of that chaos and structures it into leads. Still early though — we're learning a lot from users right now.