Urls Le logo

Urls Le

Extracts URLs from supplied text and returns protocols plus 1-based line and column positions over MCP stdio.

Install Urls Le

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "urls-le": {
      "command": "npx",
      "args": [
        "-y",
        "urls-le-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 1 tools correctly (Today).

Overview

The urls-le MCP server extracts URLs from documentation, source code, and configuration text supplied by an MCP client. Its `extract_urls` tool returns each URL, protocol, and 1-based line and column, with optional deduplication and result limits. It does not read files or make network requests; use it when an agent needs URL discovery from file content already in context. The server runs through Node.js over MCP stdio and requires no API key or environment variables.

Use cases

  • Extract URLs from Markdown documentation
  • Audit links in HTML and source files
  • Review URLs embedded in configuration
  • Locate URL positions for automated reporting

Key features

  • Format-aware URL extraction
  • Protocol and source-position results
  • Optional deduplication
  • Configurable result limits
  • MCP stdio transport
  • No API key or environment variables

Tools1

What Urls Le lets your agent do. Expand a tool for its parameters.

Verified live~328 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 47d

What it can do

From the 1 tool this server returned when we ran it.

Makes network requests · 1Read-only tools · 1
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age85 days
Maintainers1

Observed 2026-10-30 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · urls-le-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.4kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed1Callable tools this server registers over MCP.

How Urls Le works

What urls-le does

The urls-le MCP server gives an AI agent a focused URL extraction tool for text from files, documents, and configuration. The agent supplies the content rather than a path, and receives structured matches containing the URL, its protocol, and its 1-based line and column position.

Supported material includes Markdown, HTML, CSS, JavaScript, TypeScript, JSON, YAML, Java properties, TOML, INI, and XML. Extraction follows format-aware rules where described by the project: Markdown code blocks and HTML comments are excluded, while JavaScript and TypeScript string literals, template literals, and comments can be searched. The same engine is also used by the project’s editor and command-line tools, but this listing covers the MCP interface.

The urls-le MCP server is suitable for link inventories, documentation checks, configuration review, and source inspection when the calling agent can provide the text directly. It is not a crawler, file search service, or URL checker.

How it works

The server exposes one MCP tool:

  • extract_urls(content, format?, filename?, dedupe?, maxResults?)

content is the text to inspect. The optional format and filename parameters can provide context for parsing. dedupe controls duplicate handling, and maxResults limits the returned matches. Results are capped at 500 by default, and metadata reports truncation when the limit prevents all matches from being returned.

Communication uses MCP over standard input and output. The server processes the supplied data and returns the extraction result; it does not read local files and does not issue network requests. This makes it appropriate for agents that have already opened a file or received text through another tool.

Setup and configuration

Run the package with Node.js and npx:

Terminal
npx -y urls-le-mcp

An MCP host configuration can launch it with:

config.json
{
  "mcpServers": {
    "urls-le": {
      "command": "npx",
      "args": ["-y", "urls-le-mcp"]
    }
  }
}

The package is published as urls-le-mcp on npm. You can pin a package version in the arguments or install it globally and invoke the urls-le-mcp binary directly. No environment variables, API key, or server-specific configuration is required. A host can verify the installation by sending an MCP tools/list request and checking for extract_urls.

Tools and capabilities

The urls-le MCP server provides:

  • URL extraction from supported text formats
  • Protocol information for each match
  • 1-based line and column positions
  • Optional duplicate removal
  • A configurable result limit with truncation metadata
  • Stdio transport for MCP-compatible hosts

The tool works on one supplied document at a time.

Limitations and notes

The server only analyzes content passed in the tool call. It cannot discover files, inspect unsaved or on-disk workspace content, follow links, validate responses, or fetch remote resources. Large inputs may be limited by maxResults; callers should inspect the truncation metadata before treating a result as complete.

The README identifies use with VS Code agent mode, Claude Code, Cursor, and Windsurf. Other MCP hosts can use the stdio command if they support this transport and configuration style.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Urls Le

urls-le is an MCP server that connects AI agents to a URL extraction engine over stdio.

Run `npx -y urls-le-mcp` and configure your MCP host to launch that command. You can also install the package globally and invoke `urls-le-mcp` directly. The server needs no API key, environment variables, or additional configuration.

Yes, urls-le works with Cursor through the MCP stdio command. Configure Cursor to launch `npx urls-le-mcp`; the README also identifies a VS Code extension path and use with Windsurf.

No, the MCP server only processes content supplied in the tool call. Workspace and folder scanning are provided by the separate editor extension, while the MCP tool does not read files or make network requests.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewUrls Le AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/urls-le?style=directory)](https://allmcps.com/mcp/urls-le)
HTML Embed
<a href="https://allmcps.com/mcp/urls-le"><img src="https://allmcps.com/api/badge/urls-le?style=directory" alt="Urls Le on AllMCPs" /></a>