Prompt Spider UI MCP
An MCP server shows agent steps on screen: a mechanical spider catches words and branches split work into code, model and you.
- 114 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- A local web server on `127.0.0.1` and stdio MCP, with no external services or keys.
Install
- Works in
Manual install
git clone https://github.com/Kirito14IT/prompt-spider-ui.gitThe first quick-start command: then `cd prompt-spider-ui`, `npm start`. For MCP also run `npm --prefix mcp ci`.
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- A local web server on `127.0.0.1` and stdio MCP, with no external services or keys.
This is third-party code. Review the repository files before installing.
What it does
Prompt Spider UI draws agent work on Canvas 2D. A spider crawls across text, grabs words and sorts them into three branches: `code`, `model` and `you`. It has a scrubbable timeline, a rotating nebula sphere view, term search and PNG snapshots. A local stdio MCP gives the agent 11 tools. It creates a session, returns a preview link, accepts step reports, saves a JSON replay and exports a standalone project with sources. The agent reports its own steps; the UI does not read the chat or hidden reasoning. The demo runs without keys or dependencies.
Who it is for. Agent developers and demo authors who need to show a run visually rather than as a log.
Good fit when
- An agent task is shown at a meeting or in a recording.
- A session must be saved as JSON and replayed later.
- A custom project with its own theme and MCP is built from a ready interface.
- Steps that need a human decision should stand out on a separate branch.
Not a fit when
- You need production monitoring or call tracing.
- The agent cannot report its own steps.
- Session data must outlive the process without manual export.
Example request
Create a Prompt Spider session, return the preview link and report steps as you work, sorting them into code, model and you.MCP
- Transport
- stdio
- Authentication
- not required
Limitations
Sessions live only in process memory: up to 20 sessions, 10,000 events and a 16 MiB log each. Export before quitting. Only what the agent reports is shown, and distance between nodes does not imply semantic closeness. Node.js 20 or newer is required and MCP dependencies are installed separately with `npm --prefix mcp ci`. Documentation is in Chinese. The project is young, so the session replay format may change between versions.
How to disable. Remove the server entry from the client configuration, for example with `codex mcp remove prompt-spider` or by editing the JSON, and stop `npm start`. Exported projects sit in `exports/` and are deleted manually.
FAQ
Do I need to install dependencies for the demo?
No. `npm start` is enough for the plain interface. Only the MCP subproject needs dependencies.
How do I connect it to Codex?
Run `codex mcp add prompt-spider -- node "C:/projects/prompt-spider-ui/mcp/server.mjs"` with your absolute path.
What can be exported?
A standalone project with sources, theme, license and bilingual docs. The `spider_export_project` call can include the replay and MCP.
Does the interface read my chats?
No. The UI shows only what the agent passed in step reports.
Which port does the interface use?
`127.0.0.1:4317` by default; the `PORT` variable changes it, for example `PORT=4318 npm start`.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server plus a Chrome extension: pick a DOM element by Option-click and the agent gets its text, styles and selector
An MCP server and plugin to build UI with the agent: curated design systems, UI prompts and layout variations
An agent gets the MDMA spec, prompts and validation so it can answer with forms, tables and approvals right inside Markdown
A plugin for Claude Code, Codex and Cursor that adds WebMCP tools to your site so browser agents use app logic.
A design studio for people and agents: dsa CLI, MCP endpoint and skill to edit layouts, slides, reports and 3D together.
An interface design skill that anchors an agent to your product, with an optional MCP server adding real screens from a catalogue.
README in short
The repository holds the interface, an MCP subproject and docs. The service listens only on `127.0.0.1`, default port 4317.