Site Crawler for Links and Tables MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token; a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| crawl_site_links_tablesA | Crawl a website from a start address over plain HTTP and return one row per page with internal links, external links, file download links, HTML tables as rows, and lists. No AI and no browser, so pages built by JavaScript return little. Obeys robots.txt by default. Pay per event on Apify: 0.006 USD per page. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possible overlap or misselection risk. Its purpose (crawl a site and return links, tables, and lists) is stated explicitly and leaves no ambiguity about when to use it.
The single name crawl_site_links_tables follows snake_case with a leading verb, which is a predictable convention. It is descriptive but concatenates multiple output types into one long name, which is slightly less clean than a tighter verb_noun form.
One tool is thin for a server, though this tool is substantial and bundles several extraction outputs rather than being trivial. A single entry point is workable for a focused crawler, but splitting configuration or output modes would make the surface easier to target.
The tool covers the stated domain well: internal/external/file links, tables, and lists, with robots.txt compliance noted. Gaps are minor-to-moderate: no depth or max-page control surfaced, no JS rendering fallback, and no way to isolate a single page versus a full crawl.