Arche

directory.archePublished by arche.directoryOfficial publisherv1.0.0Updated Oct 30, 2026

Hand-picked landing pages as design references for your agent: design systems, motion, sections.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote MCP endpoint that gives an assistant a curated collection of hand-picked landing pages as design references for design systems, motion and sections.

What you can do
  • Provides access to a hand-picked set of landing pages to use as design references.
  • Covers design systems, motion and page sections as reference material.
  • No individual tools are listed, so the exact operations are not documented; expect reference lookup rather than editing or generation.
When to use it
Useful when an assistant is helping with web or landing page design and needs concrete, curated examples of design systems, motion patterns or section layouts to draw on.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's site; OAuth authentication is required. No packages, environment variables or headers are declared.
Before you install
Access requires OAuth sign-in to the provider's service, so the assistant's use is tied to that account. The specific tools and what data they return are not documented, so review the granted scopes before connecting.

Installation

In SourceWeft

  1. Open Arche 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/directory.arche%2Fmcp/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": {
    "arche": {
      "type": "http",
      "url": "https://arche.directory/mcp"
    }
  }
}

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

1
  1. v1.0.0LatestOct 30, 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.