mcpField
M
Motozmo Motorcycle Repair Guides

Motozmo Motorcycle Repair Guides

Local
motozmo.comGames & Entertainment0Updated 2w ago

About Motozmo Motorcycle Repair Guides

Motozmo Motorcycle Repair Guides is an MCP server for assistants that need to search and retrieve motorcycle repair guides and gear reviews from motozmo.com. It fetches current articles from the site's WordPress REST API and refreshes its cache every six hours.

Key features

  1. 01Search repair guides and gear reviews
  2. 02Retrieve individual guides
  3. 03List latest articles
  4. 04Browse topics
  5. 05Fetch live WordPress article data

Use cases

  1. 01Find a repair guide for a motorcycle issue
  2. 02Retrieve an article to quote in an assistant response
  3. 03Browse recent posts or available topics

MCP support

Exposes motozmo.com repair guides and gear reviews through the `search_guides`, `get_guide`, `list_latest`, and `list_topics` MCP tools. It can run locally over stdio or remotely over Streamable HTTP.

Configuration

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

mcp.json · Universal config
{
"mcpServers": {
"rehana-a-motozmo": {
"command": "npx",
"args": [
"-y",
"motozmo-mcp"
]
}
}
}
Run commandnpx -y motozmo-mcp

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
npmmotozmo-mcp1.0.5

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project 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)

npm install
node server.js

Claude Desktop config (claude_desktop_config.json):

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

Host remotely (Streamable HTTP)

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

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

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

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.