您的 MCP 服务器有用户。您正在为他们的账单买单。
📄 中文摘要
构建了 MCP 服务器后,用户不断使用该服务,导致您面临不断增加的费用,包括代理费用、LLM 令牌、计算费用和第三方 API 费用。尽管考虑过收费,但现有的微支付解决方案存在问题,例如 Stripe 和 PayPal 的费用过高,导致您支付的费用远超收入。此外,使用 API 密钥的方式也存在管理上的困难,因为代理无法自我注册,您需要手动管理密钥。这些因素使得有效收费变得复杂且困难。
📄 English Summary
Your MCP Server Has Users. You Are Paying Their Bill.
After building an MCP server, users continuously utilize the service, resulting in escalating costs including proxy fees, LLM tokens, compute expenses, and third-party API charges. Although charging for usage has been considered, existing micropayment solutions present challenges. For instance, both Stripe and PayPal impose high fees that exceed potential earnings. Additionally, using API keys poses management difficulties, as agents cannot self-register, necessitating manual key management. These factors complicate the implementation of an effective charging strategy.
Powered by Cloudflare Workers + Payload CMS + Claude 3.5
数据源: OpenAI, Google AI, DeepMind, AWS ML Blog, HuggingFace 等