3D Printer MCP From OctoEverywhere

Created By
OctoEverywherea year ago
A free, community 3D printing MCP server that allows for getting live printer state, webcam snapshots, and printer control.
Overview

What is 3D Printer MCP From OctoEverywhere?

3D Printer MCP is a free community server that allows users to access and control their 3D printers securely via the Model Context Protocol (MCP). It provides live printer status, webcam snapshots, and control features for various 3D printer models.

How to use 3D Printer MCP?

To use the 3D Printer MCP, create an OctoEverywhere account, link your 3D printer, and obtain your MCP access token. You can then use the server URL and access token with any AI agent to manage your printer.

Key features of 3D Printer MCP?

  • Live 3D printer status and print information.
  • Pause and cancel printer controls.
  • Live webcam snapshots.
  • Secure and private access.
  • Compatibility with various 3D printers including OctoPrint, Klipper, and more.
  • Free for the entire 3D printing community.

Use cases of 3D Printer MCP?

  1. Monitoring print jobs remotely.
  2. Controlling printer functions from anywhere.
  3. Integrating with AI agents for enhanced printing capabilities.

FAQ from 3D Printer MCP?

  • Is 3D Printer MCP free to use?

Yes! It is free for the entire 3D printing community.

  • What types of printers are supported?

It works with any 3D printer that supports the Model Context Protocol, including popular brands like Creality, Prusa, and AnyCubic.

  • How do I get started?

Create an account on OctoEverywhere, link your printer, and obtain your access token to start using the MCP.

Server Config

{
  "mcpServers": {
    "octoeverywhere-claude": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://octoeverywhere.com/api/mcp",
        "--header",
        "Authorization: Bearer ${AUTH_TOKEN}"
      ],
      "env": {
        "AUTH_TOKEN": "<Your Access Token>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
OctoEverywhere
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago