Setup (Experimental)

Experimental: MCP support in fsPulse is experimental. The connection methods described below each have known limitations that are under active investigation. You may need to restart fsPulse or your client if connectivity issues occur.

Enable the MCP Server

The MCP server is disabled by default. Enable it in the fsPulse Settings page under MCP Server (Experimental), or add the following to your config.toml:

[mcp]
enabled = true

Restart fsPulse after changing this setting. You should see MCP server enabled at /mcp in the startup output.

Choosing a Connection Method

There are two ways to connect an AI client to fsPulse’s MCP server:

Claude Desktop

Claude Desktop connects to fsPulse using the Developer settings JSON config with mcp-remote as a stdio-to-HTTP bridge. This requires Node.js (for npx).

Prerequisites

• Node.js must be installed (provides npx)
• On macOS, Node.js must have Local Network access (check System Settings > Privacy & Security > Local Network if connecting to a fsPulse instance on another machine on your network)

Configuration

Open Claude Desktop’s configuration file by going to Settings > Developer (under “Desktop app”) and clicking Edit Config. Add an entry under mcpServers:

{
  "mcpServers": {
    "fspulse": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://localhost:8080/mcp",
        "--allow-http"
      ]
    }
  }
}

Replace localhost:8080 with the hostname and port of your fsPulse instance if it is running on a different machine.

Note: The --allow-http flag is required by mcp-remote when connecting over HTTP. If your fsPulse instance is served over HTTPS, you can omit this flag.

Restart Claude Desktop. fsPulse should appear as an available MCP server.

Claude Code

Claude Code supports Streamable HTTP natively, with no bridge required. Add to your .mcp.json:

{
  "mcpServers": {
    "fspulse": {
      "type": "streamable-http",
      "url": "http://localhost:8080/mcp"
    }
  }
}

Multiple Instances

You can connect to multiple fsPulse instances by giving each a unique name:

Claude Desktop

{
  "mcpServers": {
    "fspulse-local": {
      "command": "npx",
      "args": ["mcp-remote", "http://localhost:8080/mcp", "--allow-http"]
    },
    "fspulse-remote": {
      "command": "npx",
      "args": ["mcp-remote", "http://my-server:8080/mcp", "--allow-http"]
    }
  }
}

Claude Code

{
  "mcpServers": {
    "fspulse-local": {
      "type": "streamable-http",
      "url": "http://localhost:8080/mcp"
    },
    "fspulse-remote": {
      "type": "streamable-http",
      "url": "http://my-server:8080/mcp"
    }
  }
}

Reference a specific instance by name in your prompts:

Show me the integrity report on fspulse-remote