Class JebMcpServerInstance

java.lang.Object
com.pnfsoftware.jeb.client.mcp.JebMcpServerInstance

public class JebMcpServerInstance extends Object
Factory for an MCP server bound to the current JEB engines context.

How to start the MCP server:

  • Automatic start when VIBRE dialog is brought up in the GUI.
  • Manual start from the GUI (File menu).
  • Programmatically, call one of the start(...) methods.

VIBRE automatically uses JEB's MCP server. However, it can be used by any agent that supports the registration of external MCP servers. Several tools use a standardized mcpServers key in their Json configuration file (Claude's claude_desktop_config.json, LM Studio's mcp.json, etc.). If you use the default settings for JEB's MCP, you add something like:

 "jeb-mcp-server": {
    "command": "npx",
    "args": [
      "-y",
      "mcp-remote",
      "http://localhost:8425/mcp"
    ]
  }

 
  • Field Details

  • Constructor Details

    • JebMcpServerInstance

      public JebMcpServerInstance()
  • Method Details

    • get

      public static JebMcpServer get()
      Get the current singleton server instance.
      Returns:
      the running server, or null if none was started
    • start

      public static JebMcpServer start()
      Start the singleton MCP server bound to the current JEB engines, using the default port and default endpoint.
      Returns:
      the running server instance, or null if startup failed
    • start

      public static JebMcpServer start(String hostname, int preferredServerPort, String endpoint)
      Start the singleton MCP server bound to the current JEB engines.
      Parameters:
      hostname - hostname to bind to; null to use the default
      preferredServerPort - port to listen on; 0 to use the default
      endpoint - endpoint for clients; null to use the default
      Returns:
      the running server instance, or null if startup failed
    • start

      public static JebMcpServer start(String hostname, int preferredServerPort, String endpoint, IClientContext clientContext)
      Start the singleton MCP server bound to the current JEB engines.
      Parameters:
      hostname - hostname to bind to; null to use the default
      preferredServerPort - port to listen on; 0 to use the default
      endpoint - endpoint for clients; null to use the default
      clientContext - an optional client context (the MCP server may offer a different set of tools based on the JEB context; example: if a GUI context is provided, the server will attempt to provide UI-specific tools on top of the standard tool set)
      Returns:
      the running server instance, or null if startup failed
    • stop

      public static boolean stop()
      Stop the singleton MCP server bound to the current JEB engines.
      Returns:
      success indicator