# 3D Print Log [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/HoffmanEngineering/3d-print-log-api  
**GitHub Stars:** 10  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/3d-print-log

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

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "3d-print-log": {
    "url": "https://api.3dprintlog.com/swagger/index.html"
  }
}
```

## Documentation

## What the 3D Print Log MCP server does

The 3D Print Log MCP server gives an AI agent access to records managed by 3D Print Log, a web application for tracking 3D printing activity. It is intended for agents that need to add, inspect, or organize information about print jobs and the equipment and materials behind them.

The service covers print records, printer inventory, filament stock, and projects. Print data can include duration, material consumption, quality ratings, and images. Printers have associated statistics, while filament records can include usage and cost information. Projects group related prints and can contain image galleries.

The MCP interface also exposes the service's documentation for search. That makes it useful when an agent needs to look up API or product behavior in addition to working with stored print data.

## How it works

The 3D Print Log MCP server is hosted by the 3D Print Log API at `https://api.3dprintlog.com/mcp`. An MCP-compatible client connects to that endpoint, and the service handles requests against the application API. The live API documentation is available through Swagger at `https://api.3dprintlog.com/swagger/index.html`.

Authentication for integrations uses an API key sent in the `X-Api-Key` header. The web application also supports Auth0 JWT Bearer authentication, but the README identifies the API-key method as the integration authentication mechanism.

The underlying application is built with ASP.NET Core and uses Entity Framework Core with SQL Server. Azure Blob Storage stores uploaded print and project images. These implementation details matter mainly when evaluating the surrounding API or operating a local deployment; an agent using the hosted MCP endpoint does not need to manage those components directly.

## Setup and configuration

For a hosted connection, configure an MCP client to use the remote endpoint and provide the required API key according to that client's MCP configuration format. The repository does not provide a universal client configuration file in the supplied material, so the exact setup steps depend on the client.

The project includes an agent skill that explains how to use the service. It can be added with:

```bash
npx skills add HoffmanEngineering/3d-print-log-api
```

The repository also publishes a Claude Code plugin. Its documented installation commands are:

```bash
claude plugin marketplace add HoffmanEngineering/3d-print-log-api
claude plugin install 3d-print-log@3d-print-log
```

Local contributors should consult `CONTRIBUTING.md` for application setup, configuration, and tests. The repository describes the production API and hosted MCP endpoint, not a separate set of MCP-specific local environment variables.

## Tools and capabilities

The 3D Print Log MCP server supports agent workflows around:

- Creating and querying print-job records.
- Reviewing printers and per-printer statistics.
- Tracking filament inventory, consumption, and costs.
- Grouping prints into projects and working with project image galleries.
- Searching the 3D Print Log documentation.
- Using print information that can include duration, material usage, quality ratings, and images.

The wider API also supports slicer setting imports from Cura, OrcaSlicer, PrusaSlicer, and Bambu Studio, printer webhooks for OctoPrint and Klipper/Moonraker, and electricity-cost calculations based on recorded printer wattage. The supplied material does not enumerate the individual MCP tool names or state which of these API features are exposed as separate MCP tools.

## Limitations and notes

This integration depends on access to the hosted 3D Print Log service and a valid integration API key. The README does not document offline operation, a local-only MCP transport, or the exact schema of each MCP tool.

Image handling is part of the broader application and uses Azure Blob Storage. Billing is handled through Stripe, while the production environment runs on Azure. Those dependencies may be relevant to deployments or API operations, but they are not additional MCP destinations described for the agent connection.

The repository is licensed under the GNU Affero General Public License v3.0. The frontend is maintained in a separate repository, so this source primarily documents the backend API and its MCP access path.

_Full upstream README: https://allmcps.com/mcp/3d-print-log/readme_