Docs · Connect your AI
MCP overview
Noru gives a connected agent fresh, visible screen perception and repeatable local recall through one small, observe-only MCP surface.
What connects
Noru runs a local Model Context Protocol server over standard input and output. Your MCP client starts the bundled noru-mcp process when it needs the connection. There is no hosted Noru endpoint, API key, or network listener in this agent path.
The server advertises contract 4and exactly 3 tools. They cover three agent intents: observe the Mac now, find an earlier capture, and fetch one addressed capture.
The end-to-end request path
- Your agent decides current visual context is needed and calls
get_latest_capture. - The local MCP process asks the running Noru app for the selected live target.
- Noru checks authorization, pause state, Screen Recording permission, and capture availability.
- The app captures the requested target and shows a visible acknowledgement before publishing it.
- The MCP result carries a model-sized PNG, on-device extracted text when ready, and machine-readable details about exactly what was served.
- Your chosen agent receives that result and answers under the agent provider's own terms.
A failed or refused live request never substitutes an older screenshot. History is a separate, explicit path through list_capturesand get_capture.
Free and Pro
Security boundary
This MCP surface observes and retrieves. It has no click, type, scroll, key, pointer, write, or computer-control tool. Live observation requires the running app and its Screen Recording grant. History reads use Noru's local capture store and can work while the app is closed unless you revoke agent access.
Continue with the reference
Start with Agent connection, then use theTool reference for every argument and example.Results, errors, and access documents the wire shape and recovery behavior. MCP resourcescovers the optional addressable-resource surface.