Netraptor 0.7.0: your agent can call your API as you
Version 0.7.0 · Released
Update the Chrome extension and netraptor-mcp to 0.7.0, restart your agent, then turn on Let agents call recorded endpoints in Settings. Reading saved traffic keeps working if only one side is updated; live calls need both.
Check a change against the running app
The new call_endpoint tool re-runs a request Netraptor already recorded, inside your logged-in tab, and gives your agent the fresh response. Edit a handler, ask the agent to call it, and read what came back.
Guide: An MCP server for your web app's API traffic (Codex, Claude Code, Cursor)
Your session stays in the browser
The call runs in your tab, so the browser attaches your cookies and Netraptor replays the tokens the page sent. Your agent never sees them, and the response is redacted the same way as saved traffic.
Read-only, and off until you turn it on
Live calls cover GET requests and GraphQL queries on endpoints the site already called. Writes, other origins and redirects are refused, and the agent cannot set headers. Only you can turn the switch on, in Settings → Local MCP server.
Fixes and improvements
- Every live call goes through the page's own fetch, so it appears in the session and in watch_requests.
- The agent can change path and query parameters on a recorded endpoint, or the variables of a recorded GraphQL query. A GraphQL POST keeps its recorded URL.
- Live calls run only while the tab is recording and still on the site where the request was recorded. A call times out after 8 seconds.
- To get the new tool, use npx -y @branch42-labs/netraptor-mcp@latest and restart the old bridge and agent.