← WebMCP Directory

Tool tree

machvive.com

Developer ToolsTools verified
Website
MachVive is an open source WebMCP toolset. It ships as one npm package of vanilla web components, with zero runtime dependencies and no build step. “I don’t want to use your product’s agent. I want…
Explore capabilities

    page: Every page

    get_install_commandAnswer

    Return the npm install command and buildless CDN import for the MachVive package (@machfivetechchicago/machvive-webmcp-ai).

    View tool JSON
    {
      "name": "get_install_command",
      "kind": "answer",
      "impl": "imperative",
      "description": "Return the npm install command and buildless CDN import for the MachVive package (@machfivetechchicago/machvive-webmcp-ai).",
      "inputSchema": {
        "type": "object",
        "properties": {
          "manager": {
            "type": "string",
            "enum": [
              "npm",
              "yarn",
              "pnpm",
              "cdn"
            ],
            "description": "Package manager, or \"cdn\" for a no-build module script"
          }
        }
      },
      "page": "/docs/"
    }
    list_componentsAnswer

    List the MachVive web components with their tag, import subpath, and purpose.

    View tool JSON
    {
      "name": "list_components",
      "kind": "answer",
      "impl": "imperative",
      "description": "List the MachVive web components with their tag, import subpath, and purpose.",
      "inputSchema": {
        "type": "object",
        "properties": {}
      },
      "page": "/docs/"
    }
    search_docsAnswer

    Search the MachVive documentation on machvive.com and return matching sections with a URL, heading, and excerpt.

    View tool JSON
    {
      "name": "search_docs",
      "kind": "answer",
      "impl": "imperative",
      "description": "Search the MachVive documentation on machvive.com and return matching sections with a URL, heading, and excerpt.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "query": {
            "type": "string",
            "description": "Words to look for"
          },
          "limit": {
            "type": "integer",
            "minimum": 1,
            "maximum": 20,
            "description": "Maximum sections to return (default 5)"
          }
        },
        "required": [
          "query"
        ]
      },
      "page": "/docs/"
    }

    page: Docs

    magnet_describeAction

    Describe the "MachVive" enquiry form: what it asks, what it collects, and whether it can schedule a meeting. Call this first.

    View tool JSON
    {
      "name": "magnet_describe",
      "kind": "act",
      "impl": "imperative",
      "description": "Describe the \"MachVive\" enquiry form: what it asks, what it collects, and whether it can schedule a meeting. Call this first.",
      "inputSchema": {
        "type": "object",
        "properties": {}
      },
      "page": "/docs/"
    }
    magnet_optionsAction

    List the allowed choices for one of the form's multiple-choice fields.

    View tool JSON
    {
      "name": "magnet_options",
      "kind": "act",
      "impl": "imperative",
      "description": "List the allowed choices for one of the form's multiple-choice fields.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "field": {
            "type": "string",
            "description": "Field name",
            "enum": [
              "product_interest"
            ]
          }
        },
        "required": [
          "field"
        ]
      },
      "page": "/docs/"
    }
    magnet_startAction

    Open the enquiry form with answers filled in, so the visitor can review and submit. Known fields: product_interest, name, email. This does NOT submit — the visitor confirms. Fields you leave out are asked of the visitor. Extra keys beyond the known fields are allowed and travel with the lead, which is how context like a campaign or source id is passed through.

    View tool JSON
    {
      "name": "magnet_start",
      "kind": "act",
      "impl": "imperative",
      "description": "Open the enquiry form with answers filled in, so the visitor can review and submit. Known fields: product_interest, name, email. This does NOT submit — the visitor confirms. Fields you leave out are asked of the visitor. Extra keys beyond the known fields are allowed and travel with the lead, which is how context like a campaign or source id is passed through.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "product_interest": {
            "type": "string",
            "description": "What brings you here?",
            "enum": [
              "Evaluating MachVive",
              "Building with it and need help",
              "Enterprise support or consulting",
              "Contributing to the project"
            ]
          },
          "name": {
            "type": "string",
            "description": "Who are we talking with? First and last name."
          },
          "email": {
            "type": "string",
            "description": "Best email to reach you?",
            "format": "email"
          }
        }
      },
      "page": "/docs/"
    }
    magnet_statusAnswer

    Check how far the visitor has got with the enquiry form: whether it has been opened, engaged with, which step they are on, and whether they submitted.

    View tool JSON
    {
      "name": "magnet_status",
      "kind": "answer",
      "impl": "imperative",
      "description": "Check how far the visitor has got with the enquiry form: whether it has been opened, engaged with, which step they are on, and whether they submitted.",
      "inputSchema": {
        "type": "object",
        "properties": {}
      },
      "page": "/docs/"
    }