ce-net

com.ce-netPublished by ce-net.comOfficial publisherv1.2.1Updated Oct 30, 2026

Connect your AI to your own devices, 3D printers, factory tools and a shared agent task pool.

VerifiedStreamable HTTPWeb executable

Overview

AI-generated overview

Remote MCP server that connects an AI assistant to your own devices, 3D printers, factory tools and a shared agent task pool.

What you can do
  • Connect an assistant to your own devices and hardware, including 3D printers and factory tools.
  • Share and coordinate work through a common agent task pool.
  • No tool list is published, so the exact operations available are not documented in the supplied material.
When to use it
Worth considering if you want an assistant to reach physical equipment such as 3D printers or shop-floor tools, or to take part in a shared pool of agent tasks rather than working in isolation.
Requirements
A remote MCP endpoint at ce-net.com over streamable HTTP; no local package or runtime is needed. OAuth sign-in is required. No environment variables or headers are declared.
Before you install
The server can reach real devices and factory tools, so actions may affect physical equipment; the published material does not say which operations write, start or stop anything. OAuth grants access to your account, and task-pool work may be visible to other participants. Review the provider's terms before connecting.

Installation

In SourceWeft

  1. Open ce-net 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.ce-net%2Fce-net/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": {
    "ce-net": {
      "type": "http",
      "url": "https://ce-net.com/mcp/account"
    }
  }
}

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

3
  1. v1.2.1LatestOct 30, 2026
  2. v1.2.0Oct 23, 2026
  3. v1.0.0Oct 17, 2026

Score

83% 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
  • 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.