JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 531
  • Score
    100M100P100Q90873F
  • License UNLICENSED

npm wrapper for the Graphonomous MCP server CLI

Package Exports

    This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (graphonomous) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

    Readme

    graphonomous (npm wrapper)

    This package provides an npm-friendly launcher for the Graphonomous MCP server CLI.

    It installs (or reuses) a platform-specific graphonomous binary and exposes:

    • graphonomous ...
    • npx graphonomous ...

    The underlying server communicates over STDIO, so it works well with MCP-capable editors/clients (for example Zed custom context servers).


    What this package does

    • Detects your OS/arch (darwin|linux + x64|arm64)
    • Downloads a matching release asset at install time
    • Installs the OTP release command path under vendor/<platform>-<arch>/graphonomous/bin/graphonomous when available
    • Creates/uses vendor/<platform>-<arch>/graphonomous as the launcher target for consistent execution
    • Runs the resolved Graphonomous command with all arguments passed through

    Requirements

    • Node.js >= 18
    • Supported platforms:
      • macOS: x64, arm64
      • Linux: x64, arm64

    Install

    Global install

    npm i -g graphonomous

    Then run:

    graphonomous --help

    One-off execution

    npx -y graphonomous --help

    Local project install

    npm i graphonomous
    npx graphonomous --help

    Run examples

    Start Graphonomous MCP server with a local DB path:

    graphonomous --db ~/.graphonomous/knowledge.db --embedder-backend fallback

    Safe laptop-oriented defaults:

    graphonomous \
      --db ~/.graphonomous/knowledge.db \
      --embedder-backend fallback \
      --log-level info

    Zed configuration example

    In Zed settings JSON:

    {
      "context_servers": {
        "graphonomous": {
          "command": "graphonomous",
          "args": ["--db", "~/.graphonomous/knowledge.db", "--embedder-backend", "fallback"],
          "env": {
            "GRAPHONOMOUS_EMBEDDING_MODEL": "sentence-transformers/all-MiniLM-L6-v2"
          }
        }
      }
    }

    If you prefer not to install globally:

    {
      "context_servers": {
        "graphonomous": {
          "command": "npx",
          "args": ["-y", "graphonomous", "--db", "~/.graphonomous/knowledge.db", "--embedder-backend", "fallback"],
          "env": {}
        }
      }
    }

    Release asset override instructions

    By default, the installer resolves the GitHub release source from this package metadata (repository.url, then homepage, then bugs.url).

    Current default source in this package points to:

    • Owner: c-u-l8er
    • Repo: graphonomous

    So for version X.Y.Z, the default asset URL pattern is:

    • https://github.com/c-u-l8er/graphonomous/releases/download/vX.Y.Z/graphonomous-vX.Y.Z-<platform>-<arch>.tar.gz

    You can override this behavior with environment variables for custom repos/tags/asset hosting.

    Override GitHub owner/repo/tag

    GRAPHONOMOUS_GITHUB_OWNER=my-org \
    GRAPHONOMOUS_GITHUB_REPO=graphonomous \
    GRAPHONOMOUS_RELEASE_TAG=v0.1.1 \
    npm i graphonomous

    Override version used for asset naming

    GRAPHONOMOUS_VERSION=0.1.1 npm i graphonomous

    Use custom release base URL (bypass GitHub release URL construction)

    GRAPHONOMOUS_RELEASE_BASE_URL should point to a directory containing assets named like:

    graphonomous-v<version>-<platform>-<arch>.tar.gz

    Example:

    GRAPHONOMOUS_RELEASE_BASE_URL=https://downloads.example.com/graphonomous \
    GRAPHONOMOUS_VERSION=0.1.1 \
    npm i graphonomous

    Private release download token

    GRAPHONOMOUS_GITHUB_TOKEN=ghp_xxx npm i graphonomous

    (You can also use GITHUB_TOKEN.)

    Skip, force, and tune download behavior

    # Skip download entirely
    GRAPHONOMOUS_SKIP_DOWNLOAD=1 npm i graphonomous
    
    # Force re-download even if binary exists
    GRAPHONOMOUS_FORCE_DOWNLOAD=1 npm i graphonomous
    
    # Timeout and redirect controls
    GRAPHONOMOUS_DOWNLOAD_TIMEOUT_MS=120000 \
    GRAPHONOMOUS_DOWNLOAD_MAX_REDIRECTS=10 \
    npm i graphonomous

    Runtime command override

    You can bypass installed vendor binaries/release layout and point directly to a custom executable:

    GRAPHONOMOUS_BINARY_PATH=/absolute/path/to/graphonomous graphonomous --help

    Troubleshooting

    Binary not found after install

    Try reinstalling or rebuilding:

    npm rebuild graphonomous
    # or
    npm i graphonomous@latest

    Unsupported platform message

    Current prebuilt targets are Linux/macOS + x64/arm64.

    Permission issue on command path

    Reinstall the package, or manually set executable bit on unix-like systems:

    chmod +x node_modules/graphonomous/vendor/<target>/graphonomous
    chmod +x node_modules/graphonomous/vendor/<target>/graphonomous/bin/graphonomous

    Source of truth

    The npm package is a distribution wrapper around the Graphonomous Elixir CLI.
    Core implementation and release process live in the Graphonomous repository.