News for hackers. Stuff that matters.

carlpeaslee

Show HN: V1.1 of Mac native MCP for iMessage, Reminders, Maps, and more

https://github.com/loopwork-ai/iMCP

Hi! We are the maintainers of the official swift-mcp library and we just released version 1.1 of iMCP.iMCP is written in swift and the first macOS native MCP server. It lets you connect to iMessage, Calendar, Contacts, Reminders, and more.We also think it's one of the easiest MCP servers for a normal person to actually use. Just install it https://imcp.app/download, start the application,...

( Read More... | no comments | 2 points | on HN )
Hmmm, you see any errors?

Show HN: iMCP – Connect Your macOS Messages, Calendar, and More to Claude

https://github.com/loopwork-ai/iMCP

Interact with all your Apple apps and data via Claude Desktop – or your favorite MCP client.MCPs are super hot right now but they're definitely still developer-grade user experiences.We built iMCP because we wanted to see what it would take to start to build a more consumer friendly experience on top of MCP. Not just connecting IDEs to databases and SaaS APIs.iMCP is open source and built...

( Read More... | 6 comments | 6 points | on HN )
Re:Emcee – Turn Any OpenAPI into a MCP on Tuesday March 04, 2025 @02:05PM (#43258704)
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 [email protected] too.

Re:Show HN: emcee – connect agents to APIs (via MCP) on Monday January 27, 2025 @02:48PM (#42844890)
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.

Show HN: emcee – connect agents to APIs (via MCP)

https://github.com/loopwork-ai/emcee

Hi! Mattt and I thought it would be cool (and maybe even useful) if you could easily connect Claude to any API. Well, actually we thought it would be cool if we could order pizza and shitpost directly from our AI-powered IDE.So we made emcee.emcee takes a remote (OpenAPI documented) API, generates an MCP server, and exposes the API methods to your agent (or other MCP client) as tools.The...

( Read More... | 6 comments | 3 points | on HN )