AI Connections

Connect an AI client to inspect print jobs, submit sliced files, and control printers within your account’s permissions. An administrator must first enable MCP access under Admin → Settings → AI agent access. Access starts disabled.

Connect ChatGPT#

1. Open your account menu in Pluraprint and choose Sessions & connections.
2. Under AI connections, select Connect a client and copy the connection URL. Each deployment has its own URL, such as https://hive.pluraprint.com/api/mcp or https://test.pluraprint.com/api/mcp.
3. In ChatGPT, enable Developer mode under Settings → Security and login.
4. Open Plugins, select the plus button, and create a personal plugin using the copied MCP URL and OAuth authentication.
5. Sign in to Pluraprint, review the client and requested access, then select Allow access.

ChatGPT needs a reachable HTTPS endpoint. Plugin availability may depend on your ChatGPT account or workspace settings. See the current OpenAI plugin quickstart.

Other MCP clients use the same URL with Streamable HTTP and OAuth. Request mcp:read for reads, add mcp:write for changes, and offline_access for renewal. Local clients can connect inside private networks; ChatGPT cannot reach an air-gapped server.

What an agent can do#

• List your jobs, or inspect the fleet queue, active jobs, history, and jobs awaiting approval when your account has permission to view them.
• List printers, sites, and materials within your permissions.
• Submit sliced .3mf and .form files up to 100 MiB, configure processed jobs, and approve eligible jobs.
• Cancel or prioritize queued jobs, pause supported printers, or stop a physical print.

Processing happens after upload. The agent should inspect the job before configuring materials or requesting approval. A queued job has not necessarily started printing. Printer controls must also be confirmed by the printer’s reported state.

Agents cannot provide human sign-offs, satisfy manual requirements, or perform station identification. Jobs with these requirements must be completed in Pluraprint. Printing policies and quotas apply to every connection.

For a local file without a public download URL, a client can upload a multipart file to /api/mcp/upload using its OAuth bearer token, then inspect the returned job ID. The normal preparation and approval steps still apply.

Manage access#

Open Sessions & connections to review devices and authorized AI clients. Under Active sessions, select Sign out beside a device, then confirm. Sign out other devices ends every device session except your current one. Use Log out in the account menu to end your current session.

Device labels come from the sign-in request and may be unavailable. Each row shows when that session was created; it does not indicate the device’s last activity.

Under AI connections, select Disconnect and confirm to revoke a client’s access. Only connect clients you trust: a client’s displayed name is self-reported.

Connections can outlive your browser login. Access tokens last one hour; refresh tokens use the deployment’s mobile session duration, 30 days by default, and rotate on renewal. Signing out of the website does not disconnect an AI client. Disconnect it explicitly when you no longer want it to act on your account.

Permission changes take effect on subsequent operations. Disabling an account, disconnecting a client, or disabling MCP blocks access. Administrators can disable MCP deployment-wide; users can still disconnect their clients while it is disabled.