Nexus – 针对电商 MCP 的原生 Agent 运营平台，支持自助注册，无需演示
3 分•作者: karimsherif•4 个月前
嗨 HN，
我是 Karim，在开罗。我经营一家电商运营公司，并构建了 Nexus 来解决我自己的问题：6 个互不相连的工具。
Nexus 涵盖了完整的运营堆栈：CRM、订单、库存、履约、运输和全渠道消息传递（WhatsApp/FB/IG），集成在一个平台上。
关于代理原生部分：
AI 代理通过单个 POST 请求进行自我注册，交换密钥以获取 JWT，并连接到 MCP 服务器，该服务器拥有 22 个涵盖整个业务的工具。无需人工审批。无需演示。无需销售电话。
免费层级 = 只读。写入权限 = 付费计划。代理首先证明价值。
这并非 MENA 地区专属——完全远程且自我维护。雅加达的运营人员与开罗的运营人员运行相同的工作流程。
2 个付费客户。乐于回答有关以下方面的问题：架构（Supabase + Deno Edge Functions）、多租户 RLS 或代理原生商业模式。
MCP 发现：https://nexus.aiforstartups.io/.well-known/mcp.json
代理文档：https://nexus-docs.aiforstartups.io/api/ai-agents-mcp
查看原文
Hi HN,<p>I'm Karim, based in Cairo. I run an ecommerce operations company and built Nexus to solve my own problem: 6 disconnected tools that never talked to each other.<p>Nexus covers the full ops stack: CRM, orders, inventory, fulfillment, shipping, and omnichannel messaging (WhatsApp/FB/IG) in one platform.<p>The agent-native part:
AI agents self-register via a single POST request, exchange a key for a JWT, and connect to an MCP server with 22 tools covering the entire business. No human approval. No demo. No sales call.<p>Free tier = read-only. Write access = paid plan. The agent proves value first.<p>This isn't MENA-specific — fully remote and self-maintained. An operator in Jakarta runs the same workflows as one in Cairo.<p>2 paying customers. Happy to answer questions on: architecture (Supabase + Deno Edge Functions), multi-tenant RLS, or the agent-native business model.<p>MCP discovery: https://nexus.aiforstartups.io/.well-known/mcp.json
Agent docs: https://nexus-docs.aiforstartups.io/api/ai-agents-mcp