Notion’s monorepo has 16+ MCP configs with many in opt-in plugins developers choose to activate.
Very useful; i particularly like sending an agent to debug an alert across slack/honeycomb/incident.io/materialize db
131–140 of 216 posts
Notion’s monorepo has 16+ MCP configs with many in opt-in plugins developers choose to activate.
Very useful; i particularly like sending an agent to debug an alert across slack/honeycomb/incident.io/materialize db
It has tools to get real jokes, do math, unit conversion, get stock information, search the web with Kagi, and other things I consider to be essential in a voice assistant. It even got approved by my wife.
At work I use our MCP server to debug and troubleshoot issues with our code too. Just yesterday I used it to figure out why a tag wasn’t showing up in traces; using the MCP server, the LLM was able to see that the tag was present in parent traces, but was lost along the way, and figured out why.
Could I find that without the MCP server? Yes, but I’d take me hours of going through lengthy traces, while the MCP and LLM found the issue in minutes.
And you can't expect an average user to install a CLI on their machine just to search for flights or do shopping for example.
I work at Alpic, where we build Skybridge, a framework for developing MCP Apps. Our users have apps published on the ChatGPT and Claude stores, and they've seen traffic quietly growing over the last few months. Traffic isn't massive yet, but it costs little to stake out ground on a new channel and be ready if it takes off.
Earlier quoted context omitted.
This. We also thought MCP was useless, but now the workflows by ChatGPT and Claude are so good; it's as good as installing an app from the App Store. We launched MCP for our SaaS and immediately found users using it. API and MCP all are just buzzwords for customers. What they care about is whether they can get tasks done in our SaaS using Claude or ChatGPT. If that happens, it's a success.
Do you not expose a standard REST api?
MCP is for when your end user (the one driving an LLM Agent) is non technical. Most non technical people are not going to install a CLI on their computer. Most are not going to be driving the LLM agent via a terminal. It also very helpful when you need auth. MCP OAuth with CIMD makes it easy instead of cumbersome process of generating API Keys. If you are technical and already using CLIs, then MCP doesn't give you mu…
I built an MCP server for my voice assistant. By default, Home Assistant offers a few tools to the models, but I felt like it was missing some, so I built it. It has tools to get real jokes, do math, unit conversion, get stock information, search the web with Kagi, and other things I consider to be essential in a voice assistant. It even got approved by my wife. At work I use our MCP server to debug and troubleshoot…
I got a Pebble Index 01 ring and it has support for custom MCP servers. I run one on Tailscale and it can interact with Home Assistant, my home issue tracker, my Anki setup, etc.
I've come full circle on MCP. With agents with a shell tool they quickly became unnecessary but these days I've been coming up with more agentic use cases where I don't want to give the agent a shell, and a narrower MCP interface is a great fit.
Earlier quoted context omitted.
We use a Twilio integration to make it work over a real phone line, but it could just as well be an app or websocket connection in a browser. Voice transport medium aside, the actual use case is not quite what you described. Companies like Eleven Labs and Vapi provide a full end to end voice agent platform. They handle the STT -> LLM -> TTS pipeline and infrastructure for voice agents. Think of a customer talking to…
How is security handled in a situation like this? (I'll end up reading up on it). But I mean things like how does the API let a specific session with a specific user only surface information for that specific user from the available tooling?