App

net.sitesaiPublished by sitesai.netOfficial publisherv1.0.0Updated Oct 24, 2026

SitesAI App for civil/earthworks contractors: leads, jobs, shifts, dockets, sites, compliance.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote SitesAI connector that lets an assistant work with construction and earthworks business data such as leads, jobs, shifts, dockets, sites and compliance.

What you can do
  • Work with leads and jobs for civil and earthworks contracting
  • Track shifts and dockets tied to work performed
  • Reference site records and compliance information
  • Connect through a hosted endpoint with an API key or OAuth
When to use it
Useful when an assistant needs to look up or act on SitesAI company records for civil and earthworks operations, such as checking jobs, shifts, dockets or site compliance. Only relevant if your company already uses SitesAI.
Requirements
A remote streamable HTTP endpoint at app.sitesai.net; no local package. Authentication is required: an API key sent as an Authorization Bearer header, created in the SitesAI app with read or read+write scope for your company, or OAuth 2.1 for clients that support it.
Before you install
The API key is a company-scoped secret sent in the Authorization header; a read+write key can change company data, so prefer read-only scope unless writes are needed. The manifest lists no tools, so the exact actions available are not documented here.

Installation

In SourceWeft

  1. Open App 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/net.sitesai%2Fapp/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": {
    "app": {
      "type": "http",
      "url": "https://app.sitesai.net/api/mcp/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

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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.

  • 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 Sitesai integrations