How do I install the Finding Dev Server Url skill?

Run npx skillmds add spencerpauly/finding-dev-server-url in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Finding Dev Server Url safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Finding Dev Server Url?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Finding Dev Server Url free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Finding Dev Server Url?

spencerpauly (@spencerpauly) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Finding Dev Server Url by spencerpauly

Name: Finding Dev Server Url
Rating: 4.2 (5 reviews)
Author: spencerpauly

File contents

Finding Dev Server URL

Detect which dev servers are running, what ports they're on, and open them.

How It Works

Cursor stores live terminal output in text files. Each terminal has a file at:

<terminals_folder>/<id>.txt

The terminals folder path is provided in your system context. Each file contains metadata (pid, cwd, last command) followed by the full terminal output.

Workflow

1. List All Terminals

ls <terminals_folder>/*.txt

2. Read Each Terminal's Metadata

Read the first ~10 lines of each terminal file to see:

pid — process ID
cwd — working directory
last_command — what's running (e.g. npm run dev, pnpm dev, python manage.py runserver)

Skip terminals where the last command is clearly not a server (e.g. git status, ls, cd).

3. Scan for Server URLs

Read the full content of terminals that look like they're running a server. Search for these patterns:

Framework	Pattern
Next.js	`Local: http://localhost:XXXX` or `▲ Ready`
Vite	`Local: http://localhost:XXXX/`
Create React App	`Local: http://localhost:XXXX`
Express	`listening on port XXXX` or `listening at http://...`
Django	`Starting development server at http://127.0.0.1:XXXX/`
Rails	`Listening on http://127.0.0.1:XXXX`
Flask	`Running on http://127.0.0.1:XXXX`
Go	`Listening on :XXXX` or `http server started on :XXXX`
PHP	`Development Server (http://localhost:XXXX) started`
Remix	`http://localhost:XXXX`
Astro	`http://localhost:XXXX`
Nuxt	`http://localhost:XXXX`

Regex to match most server output:

https?://(localhost|127\.0\.0\.1|0\.0\.0\.0)(:\d+)

Also check for standalone port patterns:

(listening|started|running|ready|serving).*(port\s*|:)\s*(\d{4,5})

4. Report

Print a summary:

Dev servers found:
  Terminal 1 (pid 12345) — npm run dev → http://localhost:3000 (cwd: /Users/me/app)
  Terminal 3 (pid 67890) — python manage.py runserver → http://127.0.0.1:8000 (cwd: /Users/me/api)

If no servers are found, say so and suggest starting one.

5. Open in Browser (Optional)

If the user wants to view the app, use Cursor's built-in browser:

browser_navigate → http://localhost:<port>

Then take a screenshot to confirm it's rendering:

browser_take_screenshot

Tips

If multiple servers are found, ask the user which one to open
If a terminal shows an error (e.g. EADDRINUSE, address already in use), report the conflict
If the server crashed (process exited), note that too — check for exit_code in the terminal file footer
Common default ports: Next.js (3000), Vite (5173), Django (8000), Rails (3000), Flask (5000), Go (8080)

---name: finding-dev-server-urldescription: Scan running terminals for dev server URLs (localhost ports), report them, and optionally open the app in Cursor's built-in browser.--- # Finding Dev Server URL Detect which dev servers are running, what ports they're on, and open them. ## How It Works Cursor stores live terminal output in text files. Each terminal has a file at: ``` <terminals_folder>/<id>.txt ``` The terminals folder path is provided in your system context. Each file contains metadata (pid, cwd, last command) followed by the full terminal output. ## Workflow ### 1. List All Terminals ```bash ls <terminals_folder>/*.txt ``` ### 2. Read Each Terminal's Metadata Read the first ~10 lines of each terminal file to see: - `pid` — process ID - `cwd` — working directory - `last_command` — what's running (e.g. `npm run dev`, `pnpm dev`, `python manage.py runserver`) Skip terminals where the last command is clearly not a server (e.g. `git status`, `ls`, `cd`). ### 3. Scan for Server URLs Read the full content of terminals that look like they're running a server. Search for these patterns: | Framework | Pattern | |-----------|---------| | Next.js | `Local: http://localhost:XXXX` or `▲ Ready` | | Vite | `Local: http://localhost:XXXX/` | | Create React App | `Local: http://localhost:XXXX` | | Express | `listening on port XXXX` or `listening at http://...` | | Django | `Starting development server at http://127.0.0.1:XXXX/` | | Rails | `Listening on http://127.0.0.1:XXXX` | | Flask | `Running on http://127.0.0.1:XXXX` | | Go | `Listening on :XXXX` or `http server started on :XXXX` | | PHP | `Development Server (http://localhost:XXXX) started` | | Remix | `http://localhost:XXXX` | | Astro | `http://localhost:XXXX` | | Nuxt | `http://localhost:XXXX` | Regex to match most server output: ``` https?://(localhost|127\.0\.0\.1|0\.0\.0\.0)(:\d+) ``` Also check for standalone port patterns: ``` (listening|started|running|ready|serving).*(port\s*|:)\s*(\d{4,5}) ``` ### 4. Report Print a summary: ``` Dev servers found: Terminal 1 (pid 12345) — npm run dev → http://localhost:3000 (cwd: /Users/me/app) Terminal 3 (pid 67890) — python manage.py runserver → http://127.0.0.1:8000 (cwd: /Users/me/api) ``` If no servers are found, say so and suggest starting one. ### 5. Open in Browser (Optional) If the user wants to view the app, use Cursor's built-in browser: ``` browser_navigate → http://localhost:<port> ``` Then take a screenshot to confirm it's rendering: ``` browser_take_screenshot ``` ## Tips - If multiple servers are found, ask the user which one to open - If a terminal shows an error (e.g. `EADDRINUSE`, `address already in use`), report the conflict - If the server crashed (process exited), note that too — check for `exit_code` in the terminal file footer - Common default ports: Next.js (3000), Vite (5173), Django (8000), Rails (3000), Flask (5000), Go (8080)

Frequently asked questions