Fieldstub

com.fieldstubPublished by fieldstub.comOfficial publisherv1.0.0Updated Oct 24, 2026

Capture extra work on a jobsite and file it into Procore as a Change Event on real budget codes.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Fieldstub is a remote MCP server that lets an assistant capture extra jobsite work and file it into Procore as a Change Event on real budget codes.

What you can do
Capture extra work performed on a jobsite through the assistant connection to Fieldstub, a remote server at app.fieldstub.com. File that captured work into Procore as a Change Event. Attach the Change Event to real budget codes. No individual tools are listed in the supplied material, so the exact operations available are not documented here.
When to use it
Useful for construction or field teams that need to record unplanned or extra jobsite work and push it into Procore as a Change Event against existing budget codes, without leaving the assistant workflow.
Requirements
A remote MCP connection to the Fieldstub endpoint at app.fieldstub.com over streamable HTTP. OAuth authentication is required. A Procore account or connection is implied by the described Procore filing, but the supplied material does not specify the setup details.
Before you install
The server writes data into Procore by creating Change Events, which can affect project records and budget tracking. Access is granted through OAuth, so review the scopes requested during authorization. Jobsite and budget information is sent to a third-party service, Fieldstub.

Installation

In SourceWeft

  1. Open Fieldstub 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/com.fieldstub%2Ffieldstub/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": {
    "fieldstub": {
      "type": "http",
      "url": "https://app.fieldstub.com/mcp"
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

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

    Publish an icon in the registry entry.

  • 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.