pagefind-mcp

Created By
tkellogga year ago
An MCP server for searching static sites that are indexed with pagefind
Overview

what is pagefind-mcp?

pagefind-mcp is an MCP server designed for searching static sites that have been indexed using Pagefind.

how to use pagefind-mcp?

To use pagefind-mcp, run the command npx pagefind-mcp --host <base-url> [--no-resources]. The --host option specifies the base site to index, and the --no-resources flag can be used to skip pushing full page resources.

key features of pagefind-mcp?

  • Efficiently indexes static sites for search functionality.
  • Allows customization of indexing through command-line options.
  • Supports both HTTP and HTTPS protocols for site indexing.

use cases of pagefind-mcp?

  1. Enabling search functionality on static websites.
  2. Indexing content for faster retrieval on personal or business static sites.
  3. Customizing search indexing based on specific site requirements.

FAQ from pagefind-mcp?

  • Can pagefind-mcp index any static site?

Yes! As long as the site is accessible via a URL, pagefind-mcp can index it.

  • Is there a limit to the number of sites I can index?

No, you can index as many sites as you need, provided you have the necessary resources.

  • What programming language is pagefind-mcp written in?

pagefind-mcp is written in JavaScript and is designed to be run in a Node.js environment.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tkellogg
Star
0
Language
JavaScript
License
MIT license
Category
search

Recommend Servers

View All
Voyei

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago