DeveloperWebMCP verified
web.runme.dev WebMCP tools
runme notebook
DeveloperWebMCP verified
runme notebook
runme notebook This page documents every listed tool, the action or answer it provides, its installation command, and the input fields an agent should send.
Execute JavaScript in the Runme AppKernel sandbox and return one merged stdout/stderr output string. Use timeoutMs for intentional long-running interactions such as a timed UI tour.
Open the web.runme.dev website and ask your browser agent to use ExecuteCodeInstall browse first, then run the command in a terminal. WebMCP tools run directly on the website and do not need a package install.
Use the ExecuteCode tool on web.runme.dev with code: <string>, timeoutMs: <integer>. Return the structured result and cite the source page.code string timeoutMs integer Optional execution timeout in milliseconds. Defaults to 15000 and is capped at 60000.AI agents should invoke this function to get Markdown instructions, similar to skills, for how they can safely control this Runme instance with WebMCP. This operation doesn't modify the page and can be safely invoked by AI agents as needed.
Open the web.runme.dev website and ask your browser agent to use readInstructionsForAIAgentsInstall browse first, then run the command in a terminal. WebMCP tools run directly on the website and do not need a package install.
Use the readInstructionsForAIAgents tool on web.runme.dev. Return the structured result and cite the source page.Codex, Claude, and other AI agents should invoke this read-only function to discover the Runme documentation available for this exact app version. It returns a compact JSON list of document names and descriptions; use getDocumentation to read only the pages needed for the task.
Open the web.runme.dev website and ask your browser agent to use listDocumentationInstall browse first, then run the command in a terminal. WebMCP tools run directly on the website and do not need a package install.
Use the listDocumentation tool on web.runme.dev. Return the structured result and cite the source page.Codex, Claude, and other AI agents should invoke this read-only function with a name returned by listDocumentation to get that Runme documentation page as Markdown.
Open the web.runme.dev website and ask your browser agent to use getDocumentationInstall browse first, then run the command in a terminal. WebMCP tools run directly on the website and do not need a package install.
Use the getDocumentation tool on web.runme.dev with name: <string>. Return the structured result and cite the source page.name string Highlight a registered Runme UI target and show a short explanatory annotation beside it. Use tour.listTargets() through ExecuteCode to discover target IDs.
Open the web.runme.dev website and ask your browser agent to use showTourStepInstall browse first, then run the command in a terminal. WebMCP tools run directly on the website and do not need a package install.
Use the showTourStep tool on web.runme.dev with target: <string>, message: <string>, title: <string>, placement: <string>. Return the structured result and cite the source page.target string message string title string placement string Dismiss the currently visible Runme UI tour annotation.
Open the web.runme.dev website and ask your browser agent to use dismissTourInstall browse first, then run the command in a terminal. WebMCP tools run directly on the website and do not need a package install.
Use the dismissTour tool on web.runme.dev. Return the structured result and cite the source page.