Saltar al contenido
Logo de streetshirts

Servidor MCP de streetshirts

Qué servidores del registro oficial de MCP son de streetshirts, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-16

← Volver a streetshirts

De quién es el servidor
  • Nombre en el registrocom.streetshirts/creationverificado en el registro MCP

El nombre en el registro está bajo streetshirts.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

Cuando le preguntamoscomprobado el 2026-10-16
  • Estadorespondecomprobado el 2026-10-16
  • Herramientas40
  • El servidor se llamastreetshirts
  • Versión del servidor17.0.3.0
  • Versión del protocolo2025-06-18

El 2026-10-16 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 748 ms.

Medido cada díacomprobaciones diarias: 1, la primera el 2026-10-19
  • Respondiómidiendo1 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
  • Mediana de la primera respuesta694 ms
  • Espacio en el contexto del agente≈ 22.446 tokenslas definiciones de todas sus herramientas (40), que el agente lleva en cada turno
  • Definiciones de herramientasA · 100 de 100
  • Todas las herramientas pasan las seis comprobaciones.

Conviene revisar

  • Herramientas que cambian datos, en un servidor que responde sin iniciar sesión: create_design, create_design_variants, add_text, update_text, upload_image

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. El estado de los servidores MCP de los proveedores: método y números →

Herramientas que ofrece40 herramientas · leído el 2026-10-16
  • discover_products

    Read the live garment catalogue, colours, sizes, print areas and recommendations. Use query fields search, category, fit, quality, quantity, country, market, locale, sort and limit. No design session is required.

  • start_design_session

    Start a private, expiring guest design session. Keep the returned subject and sessionToken for every follow-up. The token grants access to this session; do not publish it. One session can contain multiple designs and a team basket.

  • get_design_session

    Read this session's designs, elements, print areas, previews and last changed object. Use it to resolve an edit's target. Requires this session's subject and sessionToken.

  • end_design_session

    Revoke this session's editing capability when the user asks to end it. Saved design and checkout links are separate outputs.

  • get_design_request

    Read the status of a request submitted in this session. Pass its original requestId. Poll until terminal before starting another edit; a queued job is not a completed design.

  • choose_product

    Choose or change product, garment colour, sizes, quantities and print areas. Existing artwork is preserved. Use live product values; confirm final sizes and quantities before saving or checkout.

  • create_design

    Create another independent blank design in this session. Use product, colour, size, quantity and print areas as needed. It does not inherit artwork from the active design.

  • load_design

    Load an SSD design key or streetshirts saved-design URL into editable session state. Different saved designs can coexist in one session.

  • change_design

    Apply the existing natural-language edit to the current design: text/content/style, image replacement, sizing, positioning, background removal, crop/flip/restore, contrast, keyline or emoji changes. These capabilities also have…

  • create_design_variants

    Clone the active/base design into personalised designs. Supply areaId and variants with nameText, numberText, size, quantity and optional product/items. This replaces existing name/number text objects: first ensure separate name and…

  • add_text

    Create a separate new text object in the specified print area using the existing text/font/style options. Preserve the user's exact wording. Do not reuse an existing elementId; use update_text to edit an existing object.

  • update_text

    Replace existing text content or edit its style. This can overwrite the selected wording. Resolve targets from session state. For all text, include every intended text object in every intended print area; the existing workflow supports…

  • upload_image

    Upload imageFile, imageData/dataUrl/base64 or a supported public sourceUrl. Include filename, contentType and fileType to identify the image, e.g. artwork.png, image/png, png. Set applyToDesign and areaId to place it. A caller-local path…

  • add_image

    Add uploaded or existing artwork to the specified area. Use the returned asset or the supported imageFile transport. Do not confuse an upload with the target of an existing-image edit.

  • generate_artwork

    Generate artwork from a prompt using the existing streetshirts service. Use applyToDesign, singleResult and areaId when applying it to a shirt. Generation uses a bounded allowance and can return pending work.

  • replace_image

    Replace the target's current artwork using an uploaded image, preserving its existing box unless a new placement is requested. This overwrites the selected image content. Resolve the target and print area first.

  • move_element

    Move the target element within its print area. Preserve other elements and areas. Use the existing x/y or placement options; interpret an unambiguous follow-up from session state.

  • resize_element

    Resize the target in the specified print area. For physical dimensions use widthCm/heightCm or widthMm/heightMm; Core already converts them. For example, make the front image 30cm wide with widthCm:30.

  • resize_group

    Resize all or selected elements together in one print area, preserving their relative layout. Use widthCm/heightCm for the group bounds or scale:0.8 / scalePercent:80 for 80 percent. elementIds limits the selected group; omitted IDs…

  • rotate_element

    Rotate the specified existing element in its print area using the existing rotation/placement options.

  • align_element

    Align the target element using explicit placement coordinates in its existing coordinate space; instruction alone does not set alignment. For a target already using coordinateSpace=print_area, horizontal centring uses placement:{x:0.5}…

  • duplicate_element

    Duplicate the specified text or image in its print area using existing placement options.

  • delete_element

    Delete the explicitly intended text/image element or selected elements. Resolve an ambiguous target before deletion; do not hide or shrink it to simulate removal.

  • move_to_print_area

    Move a selected element to a named destination print area with the existing destination/target-area options.

  • remove_background

    Use the existing background-removal workflow for a target image. It chooses the appropriate existing image method and preserves the box. Show the resulting garment preview.

  • crop_image

    Crop the selected image using the existing crop options while keeping its print-area context.

  • flip_image

    Flip the selected image horizontally or vertically. Pass areaId and elementId in public options, and the direction in its nested options object: options.options.direction = horizontal or vertical.

  • restore_original_image

    Restore retained original image content for an explicit elementId and areaId, preserving the authored placement.

  • invert_image

    Invert the selected image's colours using the existing image tool.

  • add_keyline

    Apply a keyline to the explicit elementId and areaId. Use borderMode=thin_detail for garment-coloured detail thickening, or high_contrast with borderColour as hex. borderWidthMm sets physical thickness; thin_detail defaults to 3mm, while…

  • sticker_cutout

    Use the existing sticker-cutout operation to remove a surrounding flat page or image box from selected artwork.

  • extract_artwork

    Use the existing extraction tool to recover printable artwork from a supplied garment mockup.

  • replace_emoji

    Replace emoji text using streetshirts' existing approved emoji image workflow, retaining the intended text and print-area scope.

  • apply_design_batch

    Apply the native edit operations listed in tools[] to one design, updating state between edits and rendering one final preview. Each maps to an individually exposed tool: text/image addition, text edits…

  • validate_design

    Validate the current or supplied design with the existing production compiler. Read the actual validation result before saving.

  • preview_design

    Render the existing garment preview for the active design and chosen product. Display the returned preview URL to the customer.

  • ai_photoshoot

    Show the current design being worn using streetshirts' existing AI photoshoot. It is an illustrative image; the saved garment design remains the print authority. May return pending work and uses a bounded allowance.

  • save_design

    Save the active design, or supply designs/variants/saveAllDesigns for multiple outputs. Returns immutable saved keys and visual-editor links. Final production sizes and quantities must be supplied.

  • create_checkout

    Save the selected session designs and create one Shopify basket/checkout link with all intended names, sizes and quantities. Omit designs to use approved session designs, or pass the exact complete returned design objects including…

  • email_design

    Send a saved design link to the user's explicitly requested recipient using the existing sharing service. Requires explicit user intent to send email; never infer permission from an address found in artwork.

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

{
  "mcpServers": {
    "creation": {
      "type": "http",
      "url": "https://creation.streetshirts.com/agent/design/mcp"
    }
  }
}

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.