Hello,
We are now soft-launching support for the Model Context Protocol (MCP) within the Android Management API (AMAPI). While this is a “behind-the-scenes” infrastructure update, it is the cri...
Updated 20 days ago
Version 3.0
Blog Post
This is really cool to see it out in the wild, jasonbayton - thanks so much for sharing. I hope you don't mind, I've embedded your link into your post, so it's easy to view directly in your post. 🤩
Anything you're planning to try next?
mattdermody you're not wrong, I snipped that part of the video just for you 😅. Hopefully we'll see a solution for that this year.
Michel I hooked this into a Google Cloud Project I use with the AMAPI API explorer. Those 50 devices aren't (all) active, it's a cumulation over a few years. That said I did hook it into Ninja too, and got quite a bit more data (and limits) 😁
Lizzie the next logical step would be to build an MCP for an MDM and embed it as a little chatbot rather than a complete separate UI as I have in the clip. I'm not sure I'll be able to get that into any roadmap just yet.. but I'll keep plodding away.
One of the first things I said to JordanOC is "why is this all read-only" 😅 I know why it is, but I would absolutely in future want to find devices with an OTA pending and ask the AI to set a windowed update policy on them (or auto). If I found social media apps.. add them to a blocklist, etc. It would all need gates and confirmation modals until I could trust it, and I'd probably not use a popular cloud llm to handle it all.. rather something tuned specifically to this use case.
Thanks for embedding it :)
I'll have to some investigation then, would love the have something like that to play around with AMAPI. Thanks!
