DeveloperWebMCP verified
sema.run WebMCP tools
Try Sema in the browser — a Lisp with first-class LLM primitives. No install required, runs entirely in WebAssembly.
DeveloperWebMCP verified
Try Sema in the browser — a Lisp with first-class LLM primitives. No install required, runs entirely in WebAssembly.
Try Sema in the browser — a Lisp with first-class LLM primitives. No install required, runs entirely in WebAssembly. This page documents every listed tool, the action or answer it provides, its installation command, and the input fields an agent should send.
Read Sema source from the playground editor. Use this before editing or running unfamiliar code.
Open the sema.run website and ask your browser agent to use read_editorInstall 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 read_editor tool on sema.run with offset: <integer>, limit: <integer>. Return the structured result and cite the source page.offset integer Zero-based character offset at which to start reading.limit integer Maximum number of characters to return.Replace the playground editor contents with Sema source code.
Open the sema.run website and ask your browser agent to use write_editorInstall 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 write_editor tool on sema.run with code: <string>. Return the structured result and cite the source page.code string Complete Sema source to place in the editor.Format the current Sema source in the playground editor.
Open the sema.run website and ask your browser agent to use format_editorInstall 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 format_editor tool on sema.run. Return the structured result and cite the source page.Run the current Sema source and wait for evaluation to finish.
Open the sema.run website and ask your browser agent to use run_editorInstall 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 run_editor tool on sema.run. Return the structured result and cite the source page.Cancel the active worker-backed Sema evaluation when one is running.
Open the sema.run website and ask your browser agent to use stop_runInstall 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 stop_run tool on sema.run. Return the structured result and cite the source page.Read the current playground output, including values, printed lines, errors, and timing.
Open the sema.run website and ask your browser agent to use read_outputInstall 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 read_output tool on sema.run with offset: <integer>, limit: <integer>. Return the structured result and cite the source page.offset integer Zero-based character offset at which to start reading.limit integer Maximum number of characters to return.Find bundled Sema examples by filename, category, or identifier.
Open the sema.run website and ask your browser agent to use find_examplesInstall 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 find_examples tool on sema.run with query: <string>, limit: <integer>. Return the structured result and cite the source page.query string Case-insensitive text used to filter examples.limit integer Maximum examples to return.Load one bundled Sema example into the editor by identifier or filename.
Open the sema.run website and ask your browser agent to use load_exampleInstall 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 load_example tool on sema.run with id: <string>. Return the structured result and cite the source page.id string Example identifier such as getting-started/hello.sema or hello.sema.List one directory in the playground virtual filesystem.
Open the sema.run website and ask your browser agent to use list_filesInstall 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 list_files tool on sema.run with dir: <string>. Return the structured result and cite the source page.dir string Absolute virtual directory path to list.Read a UTF-8 text file from the playground virtual filesystem.
Open the sema.run website and ask your browser agent to use read_fileInstall 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 read_file tool on sema.run with path: <string>, offset: <integer>, limit: <integer>. Return the structured result and cite the source page.path string Absolute virtual file path to read.offset integer Zero-based character offset at which to start reading.limit integer Maximum number of characters to return.Create or replace a UTF-8 text file in the playground virtual filesystem.
Open the sema.run website and ask your browser agent to use write_fileInstall 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 write_file tool on sema.run with path: <string>, content: <string>. Return the structured result and cite the source page.path string Absolute virtual file path to create or replace.content string UTF-8 text content, limited to 1 MiB.Replace the debugger breakpoints with the requested one-based source lines.
Open the sema.run website and ask your browser agent to use set_breakpointsInstall 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 set_breakpoints tool on sema.run with lines: <array>. Return the structured result and cite the source page.lines array One-based editor line numbers on which to pause.Start debugging the current Sema source and wait for a pause, finish, or error.
Open the sema.run website and ask your browser agent to use start_debuggingInstall 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 start_debugging tool on sema.run. Return the structured result and cite the source page.Continue the paused Sema debugger and wait for its next stable state.
Open the sema.run website and ask your browser agent to use continue_debuggingInstall 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 continue_debugging tool on sema.run. Return the structured result and cite the source page.Step the paused Sema debugger into, over, or out and wait for its next stable state.
Open the sema.run website and ask your browser agent to use step_debuggerInstall 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 step_debugger tool on sema.run with mode: <string>. Return the structured result and cite the source page.mode string Debugger stepping mode.Stop the active Sema debugger and return the playground to its idle state.
Open the sema.run website and ask your browser agent to use stop_debuggingInstall 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 stop_debugging tool on sema.run. Return the structured result and cite the source page.Read debugger status, active line, breakpoints, locals, and stack frames.
Open the sema.run website and ask your browser agent to use get_debug_stateInstall 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 get_debug_state tool on sema.run. Return the structured result and cite the source page.