81–90 of 198 posts
Good for both development and cost reduction, as the agentic harnesses often allow for much greater amount of token usage per subscription, as opposed to API key which always is per volume.
We use MCP when security and tight capability boundaries are important. For example, even GitHub’s fine-grained tokens aren’t always fine-grained enough for our use cases. In those situations, it’s straightforward to build a small MCP server that exposes exactly the operations we want an agent to have access to. That gives us a much smaller and more explicit attack surface, without having to manually audit every poss…
It's a very popular part of our platform.
Here's the repository: https://github.com/iodize6399/xuexi-keben
And here's the server itself: https://keben.555420.xyz
We do social media community management ( https://trollwall.ai/mcp ) and our customers want to know what their followers are talking about - topics, sentiment, why are people angry, showing actual example comments, comparing to last month.. Having a conversation about this is much better UX than having dashboard or static report (.. your Claude can at the end even generate PDF report on what you talked about).
We tried to build different analytics screens for this and we always found out that different types of customers what their own angle. MCP, together with knowledge/memory of their own ChatGPT/Claude, allows them to super customize it for what they want and need.