Motozmo Motorcycle Repair Guides

io.github.Rehana-APublished by GitHub account Rehana-Av1.0.5Updated Oct 24, 2026

Search motozmo.com's motorcycle repair guides and gear reviews.

VerifiedSTDIODesktop onlyWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

A local MCP server that lets an assistant search and quote motozmo.com's motorcycle repair guides and gear reviews.

What you can do
Search repair guides and gear reviews on motozmo.com by keyword and retrieve a full guide for quoting or reference. List the latest published articles and browse available topics. Article data is fetched live from the site's WordPress REST API and cached for six hours, so new posts appear without reinstalling.
When to use it
Useful when you want an assistant to look up motorcycle maintenance or repair instructions, or to find and cite gear reviews from motozmo.com while working on a bike.
Requirements
Runs as a local Node.js process (Node.js 18+ per the README) installed from the npm package motozmo-mcp, configured in the client to start the server script. Network access to motozmo.com is needed to fetch articles. No accounts, API keys or environment variables are declared.
Before you install
The server fetches content from an external site, so queries and usage go to motozmo.com. Results are limited to that site's articles and may be incomplete or outdated; treat repair guidance as reference, not professional advice. The README also describes an optional HTTP hosting mode, which would expose the server beyond your machine.

Installation

In SourceWeft

  1. Open Motozmo Motorcycle Repair Guides in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Motozmo MCP Server

Exposes motozmo.com's motorcycle repair guides and gear reviews as MCP tools, so AI assistants (Claude, Cursor, etc.) can search and quote them directly.

Tools: search_guides · get_guide · list_latest · list_topics

Auto-updates: yes

Article data is not baked into the code. The server fetches the live WordPress REST API (/wp-json/wp/v2/posts) and caches it for 6 hours. When Rehana publishes a new article, it appears in tool results automatically after the cache refreshes — no redeploy, no manual re-indexing.

Run locally (stdio)

bash
npm installnode server.js

Claude Desktop config (claude_desktop_config.json):

json
{  "mcpServers": {    "motozmo": { "command": "node", "args": ["/absolute/path/to/motozmo-mcp/server.js"] }  }}

Host remotely (Streamable HTTP)

bash
node server.js --http --port 3000   # serves POST /mcp, GET /health

Options, cheapest first:

  1. Render / Railway / Fly.io — deploy this folder as a Node service (npm install && node server.js --http --port $PORT). Free tiers work for this workload (tiny traffic, 6h cache).
  2. Own VPS/shared hosting — any host that runs persistent Node.js 18+.
  3. Cloudflare Workers — needs a small adapter (workers-mcp); ask before going this route.

Remote servers are what MCP directories list and what other people's assistants can connect to.

Publish for directories

bash
npm publish          # then directories can reference it via npx -y motozmo-mcp

See SUBMIT.md for the per-directory submission checklist, and server.json for the official MCP registry (mcp-publisher publish).

Test

bash
npm test   # boots over stdio, lists tools, calls each one against the live site

Source: README.md at commit e74fff5

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.5LatestOct 13, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts