Advanced MCP server for fetching websites and converting to markdown with AI-powered features and stealth capabilities
Advanced MCP server for fetching websites and converting to markdown with AI-powered features and stealth capabilities. Exposed over MCP by the website to markdown mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Please list all configured websitesEverything the assistant can do here goes through one of these:
fetch_petstore_openapi — Fetch Petstore OpenAPI 3.0 specfetch_petstore_swagger — Fetch Petstore Swagger 2.0 specfetch_github_api — Fetch GitHub API specfetch_tailwind_css — Fetch Tailwind CSS documentationVersion — 2.1.0Description — A powerful example API for modern applicationsFeature — OpenAPI 3.xfetch_website — Fetch any websitelist_configured_websites — List configured websitesInstallation on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 2 environment variables: WEBSITES_CONFIG_PATH, WEBSITES_CONFIG. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Website To Markdown MCP's toolset — fetch_petstore_openapi, fetch_petstore_swagger, fetch_github_api and 6 more — is a fair guide to whether it matches your workflow. It is maintained by SunZhi-Will; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| fetch_petstore_openapi | Fetch Petstore OpenAPI 3.0 spec |
| fetch_petstore_swagger | Fetch Petstore Swagger 2.0 spec |
| fetch_github_api | Fetch GitHub API spec |
| fetch_tailwind_css | Fetch Tailwind CSS documentation |
| Version | 2.1.0 |
| Description | A powerful example API for modern applications |
| Feature | OpenAPI 3.x |
| fetch_website | Fetch any website |
| list_configured_websites | List configured websites |
{
"mcpServers": {
"website-to-markdown": {
"command": "npx",
"args": ["-y", "website-to-markdown-mcp"],
"disabled": false,
"env": {
"WEBSITES_CONFIG_PATH": "./my-websites.json"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| WEBSITES_CONFIG_PATH | Filesystem location the server is allowed to use. | Optional |
| WEBSITES_CONFIG | Configuration value read at startup. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.