SKUit BOM Builder

ai.skuitPublished by skuit.aiOfficial publisherv0.1.1Updated Nov 1, 2026

Network hardware BOMs, built inside your AI assistant

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

SKUit BOM Builder is a remote MCP server that lets an AI assistant build bills of materials for network hardware.

What you can do
  • Build network hardware bills of materials from within an AI assistant.
  • The server is hosted remotely at a fixed endpoint and requires OAuth sign-in; no tool list is published, so the exact operations are not documented in the supplied material.
When to use it
Worth considering when you need to assemble or draft bills of materials for network hardware and want that work done conversationally in an assistant instead of a separate quoting tool.
Requirements
A remote MCP client that supports streamable HTTP transport, plus an OAuth sign-in with the provider (authentication is required). No packages, environment variables or headers are declared.
Before you install
OAuth grants the server access to your account with the provider; review the scopes requested at sign-in. The tool set is not published, so what it can read or change in your account is unclear before connecting.

Installation

In SourceWeft

  1. Open SKUit BOM Builder in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.skuit%2Fbom-builder/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "skuit-bom-builder": {
      "type": "http",
      "url": "https://mcp.skuit.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.1.1LatestNov 1, 2026
  2. v0.1.0Oct 1, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Skuit integrations