AIPI compensated James Monk for this contribution. This story is adapted from his submitted account with permission.
James Monk wanted his AIPI to do something simple: take a screenshot of his Windows computer when he asked out loud.
It was not a built-in screenshot feature. It was a new ability he connected to his own AIPI through a custom tool.
One request. A new skill.
In his account, James describes using AIPI for desktop tasks such as locking his computer and opening applications. The next idea came naturally: instead of reaching for a keyboard shortcut, could he just ask his AIPI to capture the screen?
He built a tool for that specific job. When called, it asks his Windows computer to capture the desktop and save an image in the Pictures folder with a date-and-time filename.
Once the setup was connected, James reports saying, “take a screenshot,” and finding the saved image on his computer a few seconds later.
How he gave AIPI that ability
James used MCP, short for Model Context Protocol, to connect his AIPI character to an external tool. Think of it as giving a character access to a particular action—not retraining the AI or changing the device’s personality.
- AIPI receives the request. James speaks to his device as usual.
- The character calls a custom tool. A clear tool description explains what the screenshot action does and when to use it.
- His computer does the work. A separate Windows-MCP bridge runs the screenshot command and saves the file on the PC.
The screenshot is captured by the computer, not by a camera in AIPI. This example does not mean AIPI can see or understand whatever is on the screen.
The small setup detail that mattered
James’s project notes describe an important lesson: saving a custom MCP connection and enabling it for a particular agent were separate steps in his setup. The connection could appear in his account without being active for the character he was using.
He checked the server logs to see whether a real request arrived, rather than treating a spoken reply as proof that an action had happened. For the screenshot tool, the saved image was the result that mattered.
Start with one thing you want your character to do
His broader project also explores saved memories, recipes, notes between devices, email and calendar access, and phone notifications. The screenshot is one concrete example of the idea behind it: a character can have a personality you shape and, with additional setup, tools that fit your world.
You do not need to build custom tools to enjoy AIPI. Choose a ready-made character or create your own and start talking. Extensions like James’s are an optional next step for people who want to experiment.
About this community project
Custom setup required. James’s setup uses a self-managed server, a Windows computer running a separate bridge, and configured MCP connections. Depending on the tools you choose, external services, credentials, and costs may also be involved.
This is a creator’s project story, not a plug-and-play installation guide or an AIPI security certification. The working results described here are reported by James; AIPI has not independently reproduced the complete toolset for this article.
Computer-control tools can act on your PC, and email or calendar tools can access personal information. Review the code and permissions before connecting them, protect remote endpoints, and begin with a non-sensitive test environment. Do not assume a tool is safe solely because its description calls it “read-only.”