Design Engine

io.aidc-aiPublished by aidc-ai.ioOfficial publisherv1.0.0Updated Oct 24, 2026

AI data-center design engine: size, validate & lay out Rubin-era data centers. Korea live.

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

A remote design engine that lets an assistant size, validate, and lay out Rubin-era AI data centers.

What you can do
This server exposes an AI data-center design engine over a remote streamable HTTP endpoint. Based on its description, it lets an assistant size, validate, and lay out Rubin-era data centers. The registry lists no individual tools, so the exact operations are not documented here.
When to use it
Worth considering when an assistant needs to work through data-center sizing, validation, or layout questions for Rubin-era hardware. It is a hosted service, so it suits users who want that capability without running anything locally.
Requirements
A remote MCP client that supports streamable HTTP, connecting to the provider's endpoint. The manifest declares no authentication, environment variables, or headers, and no local package or runtime. Network access to the provider is required.
Before you install
The manifest declares no authentication, so it is unclear what, if anything, protects the endpoint or who can use it. The description mentions a Korea region, which suggests design data may be processed on the provider's infrastructure. No tool list is published, so verify what the server can read or change before relying on it.

Installation

In SourceWeft

  1. Open Design Engine 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/io.aidc-ai%2Fdesign-engine/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": {
    "design-engine": {
      "type": "http",
      "url": "https://aidc-ai.io/api/mcp"
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

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