Skip to content

Deploying when MCP connection starts (not needing SystemD for OSX/Linux) #12

@TomLucidor

Description

@TomLucidor

Saw the Readme, the setup has a few quirks. I wonder if it is possible to make it such that

  1. Initial startup without password is possible to reduce friction (credential lockdown should prefer manual install)
  2. Relies on an alternative to systemd for scheduling/restarting under MCP, even for multi-terminal work
  3. When one MCP connection already have kb turned on, the other MCP clients connect to the "live" one
  4. When MCP is turned on, default to initializing kb when it is not present in the specified directory
  5. Assume current working directory is where the knowledge base is similar to bitbonsai/mcpvault@db0e7af

The reasoning here is simple, based on what I usually do:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions