Skip to main content
Glama
Dorkside

siteone-mcp-server

by Dorkside

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SITEONE_BINNoPath to the SiteOne crawler binary (auto-detected if not set)
SITEONE_OUTPUT_DIRNoWorking directory for crawl outputs (default: current working directory)

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
crawl_siteA

Run a full site crawl with SiteOne Crawler. Returns structured JSON with all crawled URLs and their SEO, performance, and security metrics. Use for comprehensive site audits.

crawl_single_pageA

Analyze a single page with SiteOne Crawler. Returns JSON data for just the specified URL. Fast and lightweight — use for quick page-level audits.

generate_sitemapA

Crawl a website and generate an XML sitemap file. Returns the sitemap file path and a crawl summary. Use for SEO audits or submitting sitemaps to search engines.

export_markdownA

Crawl a website and export each page as a markdown file. Returns the export directory path and a crawl summary. Use for content migration, offline analysis, or feeding pages into other tools.

get_crawl_summaryA

Run a quick, shallow crawl and return only high-level statistics: status code distribution, response times, and error counts. Best for fast site health checks before running a full crawl.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a distinct purpose: full site crawl, single page crawl, sitemap generation, markdown export, and summary statistics. Even the overlapping crawl operations differ clearly in scope and output. An agent can reliably select the right tool based on whether it needs metrics, a sitemap, markdown files, or a quick health check.

Naming Consistency5/5

All tool names follow a consistent verb-first snake_case pattern: crawl_site, crawl_single_page, generate_sitemap, export_markdown, get_crawl_summary. The verbs are descriptive and the noun targets are clear. This is a textbook example of predictable naming.

Tool Count5/5

Five tools is well-scoped for a website crawling server. Each tool covers a distinct use case without redundancy, and the count is neither too sparse nor bloated. The set feels complete for the domain.

Completeness5/5

The tool surface covers the core operations expected from a crawler: full audit, single page check, sitemap generation, content export, and summary stats. There are no obvious gaps that would block an agent from achieving typical crawl-related tasks. Combined with the provided descriptions, the set appears comprehensive.

Maintenance

ActivityInactive
ResponsivenessNo issues