Defuddle MCP Server
Fetches webpages and returns clean, structured Markdown with metadata (title, author, publish date, description, domain, word count).
README
Defuddle MCP Server
A thin MCP wrapper around the Obsidian team's Defuddle tool. It fetches a webpage and returns clean, structured Markdown with metadata (title, author, publish date, description, domain, word count).
What it does
- Exposes one MCP tool:
webpage_to_markdown - Converts webpages into focused Markdown, stripping ads, navigation, and other clutter.
- Returns both plain Markdown text and structured metadata.
- Requires Bearer-token authorization on every HTTP endpoint.
Endpoints
| Endpoint | Method | Auth | Purpose |
|---|---|---|---|
/mcp |
POST | Bearer token | MCP tool calls |
/health |
GET | Bearer token | Health check |
Default listening port is 3000 inside the container. The included docker-compose.yml exposes it on host port 3007.
Quick start
With Docker Compose
-
Copy the example environment file and set a real token:
cp .env.example .env # edit .env # DEFUDDLE_MCP_TOKEN=your-secret-bearer-token -
Build and run:
docker compose up --build -d -
The server is now available at
http://localhost:3007/mcp.
Locally with Node.js
-
Install dependencies and build:
npm install npm run build -
Set the required token:
export DEFUDDLE_MCP_TOKEN=your-secret-bearer-token # optional: export PORT=4000 -
Start the server:
npm start
Configuration
| Variable | Default | Description |
|---|---|---|
DEFUDDLE_MCP_TOKEN |
(required) | Bearer token clients must send as Authorization: Bearer <token> |
PORT |
3000 |
Port the server listens on inside the container |
To use a custom port, set both PORT and adjust the Docker Compose port mapping, e.g.:
ports:
- "4000:4000"
Connect an MCP client
Add a server config like this (example for a client that supports streamable HTTP):
{
"mcpServers": {
"defuddle": {
"url": "http://localhost:3007/mcp",
"headers": {
"Authorization": "Bearer your-secret-bearer-token"
}
}
}
}
Development
npm run dev— run directly from TypeScript.npm run build— compile todist/.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.