mcpField
S
siteguide

siteguide

Local
github.com/CloudCorpRecordsBusiness & Marketing0Updated 1w ago
Repository

About siteguide

siteguide is a forwarding MCP server for reading and linking content from the ikeytz locksmith website. It exposes the site's service, pricing, area, FAQ and guide information through 47 tools, without maintaining its own website data.

Key features

  1. 0147 tools for ikeytz site content
  2. 02Service, price, and area lookups
  3. 03FAQ and guide discovery
  4. 04Link and contact composers

Use cases

  1. 01Check locksmith service areas and prices
  2. 02Find answers in FAQs and guides
  3. 03Compose contact links for the site

MCP support

It exposes the ikeytz website service's tools to MCP clients and forwards tool calls to the upstream MCP endpoint. Tool definitions are served locally from a captured list.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "cloudcorprecords-siteguide": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/siteguide"
      ]
    }
  }
}
Run commandnpx -y @reneturcios/siteguide

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@reneturcios/siteguide0.1.0
ocighcr.io/cloudcorprecords/siteguide:0.1.0

Tools

47

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
localeenumNoHTML locale for canonicalUrl and path prefixes. de = default, URLs have no prefix (https://www.ikeytz.com/preise). en|fr|ru|fa|ar|tr = prefix /{locale}/ (https://www.ikeytz.com/en/preise). Omit or empty = de. Does not change prices, phone numbers, or legal German names. Not a maps.ikeytz.com locale (maps is German-only).de | en | fr | ru | fa | ar | tr

Details

From the project README

siteguide

A forwarding client for the ikeytz website read/link service — the public, read-only service behind a Ludwigsburg locksmith's main website. It covers services, fixed prices, service areas, FAQ entries, knowledge articles and guides, discovery files, and link composers for that site.

siteguide contains no website logic of its own. It serves tools/list locally from a verbatim capture of the upstream server's 47 tools (name, title, description and inputSchema; the capture's outputSchema fields and annotations are not reproduced), and forwards every tools/call to the upstream endpoint. Upstream results pass through unchanged; a failed hop comes back as a siteguide error: ... text result with isError set.

Upstream

  • Default endpoint: https://www.ikeytz.com/mcp
  • Override: set IKEYTZ_WEBSITE_MCP_URL to another streamable-HTTP MCP endpoint. (The override is a reconstruction; the default endpoint is the pinned one.)
  • No account and no API key are needed.
  • The forwarding hop runs initialize (protocolVersion 2025-03-26, clientInfo siteguide / 0.1.0), then notifications/initialized, then tools/call, and honours an Mcp-Session-Id header when the upstream issues one. Replies may be plain JSON or server-sent events.

CLI usage

npx @reneturcios/siteguide get_service_area '{"slug":"pattonville"}'
npx @reneturcios/siteguide site_overview '{}'
npx @reneturcios/siteguide --version

Each tool subcommand takes a single JSON argument string, forwards the call and prints the result as JSON. Exit codes: 0 success, 1 a forwarded-call error, 2 usage error.

MCP usage

npx @reneturcios/siteguide mcp

MCP client config:

{
  "mcpServers": {
    "siteguide": {
      "command": "npx",
      "args": ["-y", "@reneturcios/siteguide", "mcp"]
    }
  }
}

Unknown tool names, and arguments that are not a JSON object, are rejected locally with InvalidParams before any network hop.

Docker

docker run -i ghcr.io/cloudcorprecords/siteguide          # stdio MCP server (CMD defaults to "mcp")
docker run --rm ghcr.io/cloudcorprecords/siteguide get_service_area '{"slug":"pattonville"}'

Tools (47)

site_overview, get_business_identity, list_nav, list_footer, list_locales, resolve_locale_url, get_prices, get_ort_datetime, get_invoice_line_items, list_services, get_emergency, list_auswahl, get_auswahl_item, list_service_areas, get_service_area, get_geo_office, get_contact, get_legal, get_about, get_partner_info, get_links, get_it, get_mcp_hub, get_review_url, list_faq, get_faq, list_wissen, get_wissen_entry, list_ratgeber, get_ratgeber, get_page_summary, get_ai_page, get_serp_snippet, find_by_keyword, get_discovery, get_llms_txt, get_llms_jsonld, get_llms_serp_txt, get_llms_mcp_server, get_llms_mcp_web, get_ai_txt, get_sitemap_txt, list_whatsapp_options, compose_tel_mobile, compose_tel_landline, compose_whatsapp, compose_mailto.

Development

npm install
npm run build   # tsc -> dist/ (dist/cli.js is the bin)
npm test        # tsx --test test/*.test.ts (fake fetch only, no network)
npm run dev     # tsx src/cli.ts

License

MIT — Copyright (c) 2026 Rene Turcios.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.