TakeOn

com.takeonbidPublished by takeonbid.comOfficial publisherv1.0.0Updated Oct 24, 2026

Electrical takeoff and bid software: drawings, counts, schedules, specs and priced estimates.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

TakeOn is a remote MCP server for electrical takeoff and bid software, giving an assistant access to drawings, counts, schedules, specs and priced estimates.

What you can do
Work with electrical takeoff and bid data: drawings, counts, schedules, specifications and priced estimates. The manifest lists no individual tools, so the exact operations an assistant can perform are not documented here. Access is through a remote endpoint with OAuth sign-in.
When to use it
Consider it when an assistant should work with electrical estimating material — takeoffs, counts, schedules, specs or priced bids — inside the TakeOn platform rather than in local files.
Requirements
A remote MCP endpoint at the provider's app host, reached over streamable HTTP. OAuth authentication is required, so a TakeOn account with access to the relevant bid data is needed. No environment variables or headers are declared.
Before you install
The server requires OAuth sign-in, so it will be granted access to your TakeOn account data. Bid, estimate and project information is held by the third-party provider. No tool list is published, so what the assistant can read or change cannot be verified in advance.

Installation

In SourceWeft

  1. Open TakeOn 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.takeonbid%2Ftakeon/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": {
    "takeon": {
      "type": "http",
      "url": "https://app.takeonbid.com/api/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.0LatestOct 23, 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.