Open Design MCP

net.digitalpipe.appPublished by app.digitalpipe.netOfficial publisherv1.0.0Updated Oct 24, 2026

Open Design MCP capability governed by DigitalPipe.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Open Design MCP is a remote DigitalPipe-hosted endpoint that gives an AI assistant access to DigitalPipe's design capabilities, authenticated with a bearer API.

What you can do
Connects an assistant to a remote DigitalPipe service described as an Open Design capability governed by DigitalPipe. The manifest lists no individual tools, so the specific actions available are not documented here. Access is authenticated per connecting agent with a bearer token issued by DigitalPipe.
When to use it
Consider it when you already use DigitalPipe and want an assistant to reach its design-related capability through a hosted endpoint rather than a local package.
Requirements
A remote streamable HTTP endpoint at the provider's host; no local runtime or package is needed. A bearer token issued by DigitalPipe for the connecting agent, sent in the Authorization header, is required. Network access to the endpoint is needed.
Before you install
The connection requires a DigitalPipe-issued bearer token in the Authorization header; treat it as a secret and avoid exposing it in logs or shared configuration. The manifest lists no tools, so what the assistant can read or change on the remote service is not documented; confirm scope before use.

Installation

In SourceWeft

  1. Open Open Design MCP in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/net.digitalpipe.app%2FdCYkJz/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.

{
  "mcpServers": {
    "open-design": {
      "type": "http",
      "url": "https://app.digitalpipe.net/p/dCYkJz/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

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