carlpeaslee

Hmmm, you see any errors?

Hey Taylor! Thanks! One of the creators of emcee here.

So... short answer... there isn't a great way right now. Currently emcee is communicating over stdio – and although MCP technically supports SSE, it isn't super friendly to remote workflows.

You can see it's definitely on the roadmap for MCP here, however: https://github.com/modelcontextprotocol/specification/discus...

Curious to hear how you were thinking of using emcee remotely? Feel free to email me at carl@loopwork.com too.

Thanks! That's a super helpful list of compatible endpoints. One thing we've discovered is that sometimes it can be a bit of a pain to find the right API, find the OpenAPI schema URL, and then figure out the right auth / get a token. We're thinking through how to make that discovery process easier.

Another related issue we've seen is that sometimes a service will expose hundreds of endpoints... and you really only need a couple of them. Is there a better way to manage that?

So yeah, tool discovery and authentication are two things we're definitely trying to improve upon.