3D Print Log

com.3dprintlogPublished by 3dprintlog.comOfficial publisherv1.1.0Updated Oct 24, 2026

Log and query 3D prints, printers, filament, and projects on 3dprintlog.com, and search its docs.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Remote MCP server for 3D Print Log that lets an assistant log and query 3D prints, printers, filament, and projects, and search the service's docs.

What you can do
Log and query print jobs with duration, material usage, quality ratings, and images; search the documentation for guidance on using the service.
When to use it
Useful if you already track 3D printing on 3dprintlog.com and want an assistant to record prints, look up printer or filament history, or answer questions about the service's documentation.
Requirements
A remote endpoint at api.3dprintlog.com with OAuth authentication; a 3D Print Log account is required. No local runtime, packages, environment variables, or headers are declared.
Before you install
OAuth grants the assistant access to your 3D Print Log account, so it can read and write your prints, printers, filament stock, and projects, including image uploads. Review what the connection is allowed to change before enabling it.

Installation

In SourceWeft

  1. Open 3D Print Log 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.3dprintlog%2Fprintlog/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": {
    "3d-print-log": {
      "type": "http",
      "url": "https://api.3dprintlog.com/mcp"
    }
  }
}

README

3D Print Log API

[CI] [License: AGPL v3]

The backend API powering 3D Print Log — a web application for tracking 3D prints, printers, and filaments. Running in production at api.3dprintlog.com/swagger.

Features

  • Prints — log print jobs with duration, material usage, quality ratings, and images
  • Printers — manage your printer inventory with per-printer statistics
  • Filaments — track filament stock, usage, and costs
  • Projects — group related prints together with project-level image galleries
  • Slicer integration — import print settings directly from Cura, OrcaSlicer, PrusaSlicer, and Bambu Studio
  • Printer webhooks — automatic print logging via OctoPrint and Klipper/Moonraker integrations
  • Electricity cost tracking — record wattage per printer and calculate per-print power costs
  • Dual authentication — Auth0 JWT Bearer for the web app and API key (X-Api-Key header) for integrations
  • Image uploads — per-print and per-project image storage via Azure Blob Storage

API Documentation

Explore the live API: api.3dprintlog.com/swagger

Getting Started

See CONTRIBUTING.md for local setup, configuration, and running tests.

The frontend lives at HoffmanEngineering/3d-print-log-ui. Most feature work requires both running locally.

Tech Stack

  • ASP.NET Core (.NET 10)
  • Entity Framework Core + SQL Server
  • Auth0 (JWT Bearer authentication)
  • Azure Blob Storage (file storage)
  • Stripe (subscription billing)

Infrastructure

The production environment runs on Azure (App Service, SQL Server, Blob Storage). That part is manually managed. Email is the exception: Amazon SES, its DNS and the event webhook topic are defined in Terraform in HoffmanEngineering/3d-print-log-infra.

Email is configured through the Email section (PrintLogApi/Email/EmailOptions.cs lists every key and default; the example appsettings files show the shape). It is off by default: nothing is sent until Email:Enabled is true. docs/email-runbook.md covers dry runs, going live, key rotation and the single-instance requirement, and docs/email-metrics.md the holdout measurements.

If your contribution requires infrastructure changes (new environment variables, Azure resource configuration, etc.), call this out explicitly in your PR description so the maintainer can coordinate the changes before the code ships.

Questions & Discussions

Usage questions are best asked in 3D Print Log Discussions. That board is the front door for the whole project — the web app, this repository, and both slicer plugins — so you do not have to work out which repository your question belongs to, and answers stay searchable for whoever asks next.

Bug reports and feature requests still belong in this repository's issues.

Use It With an AI Agent

The API hosts an MCP server at https://api.3dprintlog.com/mcp, and this repo publishes an agent skill that teaches an agent to use it well: skills/3d-print-log.

bash
# The skill, for any agent the skills CLI supportsnpx skills add HoffmanEngineering/3d-print-log-api
# The skill and the MCP server together, as a Claude Code pluginclaude plugin marketplace add HoffmanEngineering/3d-print-log-apiclaude plugin install 3d-print-log@3d-print-log

The repo root is also an Agent Plugins package (plugin.json and mcp.json).

Support Development

If you find 3D Print Log useful, consider supporting its development:

License

GNU Affero General Public License v3.0

Source: README.md at commit 8c75c05

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.1.0LatestOct 10, 2026

Score

85% 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
  • License10 pts