Archetype

com.heyarchetypePublished by heyarchetype.comOfficial publisherv3.7.0Updated Nov 7, 2026

Your brand for AI agents: tokens, components, templates, voice, assets and a brand check.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Archetype gives an AI assistant a brand system — tokens, components, templates, voice, assets and a brand check — through a remote, OAuth-protected endpoint.

What you can do
  • The manifest lists no tools, so capabilities come from the short description only.
  • It is described as supplying brand tokens, components and templates for AI agents.
  • It also covers brand voice and brand assets.
  • A brand check is mentioned, suggesting a way to verify output against the brand.
When to use it
Worth considering when an assistant should produce or check work against a specific brand system — design tokens, components, templates, tone of voice or assets — rather than generic styling.
Requirements
A remote streamable HTTP endpoint at the provider's site; no local package or runtime. OAuth authentication is required, so the user must sign in and authorize the connection. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to a third-party hosted service, so review what account data and brand material are shared with it. The tool list is not published, so what the brand check does and whether anything is written or changed cannot be confirmed before connecting.

Installation

In SourceWeft

  1. Open Archetype 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.heyarchetype%2Farchetype/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": {
    "archetype": {
      "type": "http",
      "url": "https://www.heyarchetype.com/api/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. v3.7.0LatestNov 7, 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.