capture_url

Capture and recordingFull

Capture a web page by its address: the SuperCapture browser extension opens the URL in a new tab of the user's browser, captures it - the visible viewport, or with full_page the whole page scrolled and stitched - then closes the tab. For a page the user doesn't already have open; for one they do, capture page_visible / page_full with tab_url. Nothing on the page is clicked or typed into. http and https only. The page loads as the user's browser would load it, signed in where they are, so the user is asked to approve every call. Saves into the folder currently open in the gallery, or the save root if none; pass 'folder' to target a specific folder. With a bookmark's id instead of a url, its page is fetched again into it (Recapture), asked about the same way.

Needs the Full level, which is the default for any client holding the bearer token.

Parameters

Name	Type	Required	Description
url	string	no	The page's address, http:// or https://.
id	string	no	Or a bookmark (or web video) already in the library, whose page is fetched again: its article text, picture and title replaced with what the page shows now, as Recapture does. Takes nothing else.
path	string	no	Or that bookmark's path or name.
full_page	boolean	no	Capture the whole page, scrolled and stitched, instead of the visible viewport (default false).
folder	string	no	Destination folder as a rel path under the save root ('' = the save root; omitted = the gallery's current folder, or for a bookmark the reading folder open in Reader mode, else Reader/). Unknown or non-writable folders are a hard error.
bookmark	boolean	no	Save the page as a bookmark (Reader) instead of a capture: its first screen, title and article text, as the extension's right-click Bookmark does. Not with full_page.

Example

A JSON-RPC call to POST http://localhost:21516/mcp with the bearer token, filling in the required parameters:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "capture_url",
    "arguments": {}
  }
}

See the MCP server overview for how to connect a client and where the token lives.