SpecCapture

com.speccapturePublished by speccapture.comOfficial publisherv1.0.0Updated Oct 25, 2026

Read title blocks, parts lists, revision history and notes from 2D engineering drawings.

VerifiedStreamable HTTPWeb executableFiles & Storage

Overview

AI-generated overview

SpecCapture is a remote MCP server that lets an assistant read title blocks, parts lists, revision history and notes from 2D engineering drawings.

What you can do
Read title blocks from 2D engineering drawings to get drawing identification and metadata. Extract parts lists (bill of materials) from drawings. Retrieve revision history recorded on drawings. Pull notes and annotations from drawing sheets.
When to use it
Useful when an assistant needs to answer questions about engineering drawings, such as what a drawing's title block says, which parts it lists, or what revisions and notes it carries, without opening the drawing manually.
Requirements
A remote endpoint at api.speccapture.com over streamable HTTP. A SpecCapture account and an sc_live_ API key from the SpecCapture dashboard, sent as a bearer token in the Authorization header. Network access is required.
Before you install
The API key is a live credential sent in the Authorization header; keep it out of shared logs and prompts and rotate it if exposed. Drawings and their extracted content are sent to a third-party service, so check that this is acceptable for confidential engineering data.

Installation

In SourceWeft

  1. Open SpecCapture in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.speccapture%2Fspeccapture/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.

{
  "mcpServers": {
    "speccapture": {
      "type": "http",
      "url": "https://api.speccapture.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

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.0LatestOct 14, 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.