241–250 of 250 posts
I’m running basicmemory.com as a production cloud hosted memory. It has mcp/we ui/api/cli interfaces. The difference between mcp/cli/api has been discussed at length but in general mcp gives agents oauth (for clients like Claude web/chatgpt) and a “more agentic” interface that can helpfully steer the agent instead of having it thrash tokens on erroneous api calls and request formats. There are good and bad parts to b…
I’m running basicmemory.com as a production cloud hosted memory. It has mcp/we ui/api/cli interfaces. The difference between mcp/cli/api has been discussed at length but in general mcp gives agents oauth (for clients like Claude web/chatgpt) and a “more agentic” interface that can helpfully steer the agent instead of having it thrash tokens on erroneous api calls and request formats. There are good and bad parts to b…
Past job had MCPs for the following: - Loki - Prometheus - Grafana - Incident.io - GitHub for our codebase - A custom MCP for our server inventory/nodes Having all of them made it trivial for the LLM to start with an alert, search the codebase for the alert source and then review the Prom stack for additional info. Automated a lot of the toil around digging through alerts and then making changes to fix issues.
at Hedgy we built an MCP to give our agents read-only access to cross-system data + context about what it means [0]. daily it helps me debug customer flows and think through features and priority. the advantage of MCP is that the tool description names what data it has so the agents know to just use it if they want that kind of data. as new data is added, everyone’s tool description updates. with a REST api or cli I…
We use MCP in production since March 26 for user-facing endurance sports analytics and planning that integrates directly with the MCP host, in this case the chat interfaces of ChatGPT, Claude, Grok, Perplexity.ai, Mistral, you name it. All of those let users add either custom MCP servers, which users can do with a simple explanation. To connect Claude for example: https://www.tredict.com/faq/connect-claude-web-with-t…
Combined with github presence and some other places agents just seem to find and use whatever works for them.
This is all largely invisible to end users who just use us through their agents to find apartments.
The exception is OpenAI which as you found out doesn't allow MCP for chat users (does for codex) instead requiring an app-store type listing. Not so open and triggers an app store style discovery process (and presumably tax in the near future).
MCP's are great for adoption of your service outside of developer circles. Non Technical users can click a link, trigger an OAuth flow and authenticate. You can't do that with API. API still is better for developers using a AI via a CLI but MCP is easier adoption for web or desktop based clients.
This (points up)! I've read many comments about how good CLIs are, and they are right. But for developers. For non-tech people, installing the CLI is a hurdle: it involves having the right dependencies installed, controlling how you handle secrets (like API keys), and handling updates (ie. npx with a private registry). But for internal tools, once you create an MCP with OAuth, the installation (in Claude) is straight…