iBuildPro

io.github.hananzlotPublished by GitHub account hananzlotv1.0.1Updated Oct 24, 2026

Your iBuildPro workspace in Claude: jobs, customers, money, calendar. Sign in with your login.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Connects an assistant to an iBuildPro workspace so it can work with jobs, customers, money and calendar data.

What you can do
This remote MCP server links an assistant to an iBuildPro workspace. According to the description, that workspace covers jobs, customers, money and calendar. The manifest does not list individual tools, so the exact operations available are not documented here.
When to use it
Useful when someone already runs their work on iBuildPro and wants an assistant to reach that workspace data instead of copying it by hand. It is aimed at business users rather than developers.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. OAuth authentication is required, and the user signs in with their iBuildPro login. No environment variables or headers are declared.
Before you install
Access is granted through an OAuth sign-in to the user's iBuildPro account, so the assistant can reach the workspace data that account can see. The description mentions money and customer records, so review what the connection is allowed to read or change before authorizing.

Installation

In SourceWeft

  1. Open iBuildPro 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/io.github.hananzlot%2Fibuildpro/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": {
    "ibuildpro": {
      "type": "http",
      "url": "https://mspujwrfhbobrxhofxzv.supabase.co/functions/v1/mcp-server"
    }
  }
}

README

This repository has no README.

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

1
  1. v1.0.1LatestSep 16, 2026

Score

60% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.