Fenceline

Local MCP client development

The repository supports local stdio development. A hosted Claude Desktop connection is not currently documented as production ready.

Developer preview: this requires a local repository checkout and the server's environment dependencies. It is not a self-service customer setup flow.

1. Build the package

npm --prefix servers/mcp ci
npm --prefix servers/mcp run build

Review servers/mcp/env.example for variable names and supply credentials through an approved local secret mechanism.

2. Configure an stdio-capable client

{
  "mcpServers": {
    "fenceline-local": {
      "command": "node",
      "args": ["/absolute/path/to/fenceline/servers/mcp/dist/index.cjs"],
      "env": {
        "MCP_TRANSPORT": "stdio",
        "FENCELINE_CONTRACTOR_ID": "YOUR_CONTRACTOR_ID"
      }
    }
  }
}

Use an absolute path and keep secrets outside the checked-in JSON. Your client version may use a different settings workflow; consult its current documentation.

3. Verify the exact tool path

Start with tool discovery, then call only the tool you are developing. Registered agent, vendor, permit, and SEO tools can contain staged or fallback behavior; inspect the handler before using side effects.

← Back to MCP overview