R3PLICA AI Connector MCP server

• brand_getFree

  Detailed information about a specific brand by name (description, country, designers, catalog presence). Triggers: 'tell me about <brand>', 'info on <brand>', 'who is <brand>', 'parlami di <brand>', 'chi è <brand>'.

• brand_listFree

  List all R3PLICA partner brands (default limit 200). Triggers: 'what brands do you have', 'list the brands', 'which brands are on R3PLICA', 'quali brand avete', 'elenca i brand', 'che marche ci sono'.

• brand_searchFree

  Search R3PLICA brands by name substring. Use when the user mentions a brand but you need to resolve the exact catalog name. Triggers: 'find the brand <x>', 'is <x> on R3PLICA', 'cerca il brand <x>', 'avete <x>'.

• finish_collection_getFree

  Get a finish collection detail with all its individual finishes. Response includes `catalog_url` (deep-link to the collection page on catalog.r3plica.space), `finish_directory[]` (compact flat list with name + mongo_id + asset_name + thumbnail_url — designed to survive context truncation), and `finish_details[]` (full nested data). CRITICAL when generating documents/artifacts: copy the `thumbnail_url` and `catalog_url` fields VERBATIM. Do NOT construct catalog URLs yourself — the route is `/go/finish/<mongo_id>` (singular 'finish', NOT 'finish-collection' or 'finish/collection'). Do NOT construct thumbnail URLs from asset_name. If you need data for a single finish whose parent collection has been pushed out of context, call `finish_get` instead.

• finish_collection_listFree

  List R3PLICA finish collections (e.g. fabric, leather, wood, marble, metal sets sold as one asset). Optional brand/category filters. Default limit 5 collections per call — each can contain 30-50 individual finishes once enriched, so keep limits modest. TERMINOLOGY: a `finish_collection` is the asset sold on the platform; it contains many individual `finishes` inside `finish_details[]`. Do NOT call individual finishes 'variants' — 'variant' is reserved for product dimensional/additional variants. Response shape: { _meta: { terminology, asset_paths, deep_link_routes, thumbnail_rule, catalog_url_rule }, data: [collections] }. Each collection has a `catalog_url` and a flat `finish_directory[]`; each finish in `finish_details[]` carries a `thumbnail_url`. CRITICAL when embedding images: use the `thumbnail_url` field VERBATIM. NEVER construct CDN URLs from `asset_name` yourself — the file prefix is `MI_` (Material Instance) for ALL finishes regardless of brand; agents that infer brand-derived prefixes like `MO_`/`BO_` produce broken links.

• finish_collection_searchFree

  Search finish collections by name. Default limit 10. Response includes `_meta.terminology` + `_meta.asset_paths` notes and each finish in `finish_details[]` carries a `thumbnail_url`. CRITICAL: never construct CDN URLs from asset_name yourself — use the `thumbnail_url` field as-is.

• finish_getFree

  Look up a single individual finish by its mongo_id. Returns its exact `name` (e.g. 'Saffron', 'Walnut'), `asset_name`, `thumbnail_url`, `catalog_url` (deep-link to the PARENT collection page — individual finishes don't have their own page), and parent finish collection identity. Use this when composing documents and you need the precise URL for a specific finish without re-fetching the whole collection — avoids the URL-guessing trap when the collection has already been pushed out of your context window.

• finish_searchFree

  Search individual finishes across all collections by finish name (e.g. 'Walnut', 'Saffron') or asset_name substring. Optional `collection` filter narrows by finish collection name. Default limit 50. Returns each match with `asset_name`, `thumbnail_url`, and parent collection identity attached. Use when you know the finish name but not its mongo_id — e.g. 'find me the Walnut finish in the Bolzan Wood collection'.

• product_collection_listFree

  List product collections (a brand's product lines, e.g. 'Eclipse', 'Charisma'). Default limit 100. A product collection is a named product line within a brand — NOT a finish set (use finish_collection_* for those). Triggers: 'what collections does <brand> have', 'list <brand> product lines', 'quali collezioni ha <brand>', 'le linee di <brand>'.

• product_collection_searchFree

  Search product collections by name substring (product lines, not finish sets). Triggers: 'find the <x> collection', 'cerca la collezione <x>', 'la linea <x>'.

• product_compareFree

  Compare two products side by side. Returns two markdown cards under `## Product 1` / `## Product 2`, each with a 2-column spec table. Triggers: 'compare X and Y', 'X vs Y', 'which is bigger/better', 'differenza tra X e Y', 'confronta X e Y', 'meglio X o Y'. CRITICAL: preserve both card structures verbatim — the side-by-side tables are how the user visually compares.

• product_getFree

  Get detailed information about a specific product. Returns one structured markdown card (heading + `` image + spec table + description + catalog link). CRITICAL: preserve the markdown image and table verbatim. Do not flatten into prose. Do NOT reconstruct the thumbnail URL from asset_name — copy the provided `` line as-is.

• product_listFree

  List R3PLICA products with optional structured filters (brand, category, collection, designer, year). Use this for browsing/filtering by attribute (e.g. 'all Cassina sofas', 'chairs from 2020'); use product_search instead when the user gives a free-text query or keyword. Triggers: 'show me <category>', 'list <brand> products', 'browse the catalog', 'mostrami <categoria>', 'fammi vedere i prodotti di <brand>', 'sfoglia il catalogo'. Default limit is 50 products per call — raise via the `limit` argument if needed. Returns a sequence of structured markdown product cards: each has a `###` heading with name and brand, an inline `` markdown image, a 2-column markdown table with the spec rows (Designer, Year, Collection, Dimensions, Materials, Category), a blockquote description, and a catalog deep-link. CRITICAL when replying to the user: emit the cards VERBATIM as returned. Keep every `###` heading, the full markdown image line, the markdown table (`| ... |`), the blockquote, and the `[View on R3PLICA catalog →](url)` link untouched. Do NOT flatten the table into a comma-separated paragraph. Do NOT rewrite specs as prose. Do NOT construct alternate URLs from the asset_name — the CDN prefix is `SM_` (Static Mesh) for all products regardless of brand; pattern-matching brand-derived prefixes produces broken links.

• product_searchFree

  Search R3PLICA products by free-text query. Returns structured markdown product cards (heading + thumbnail image + spec table + description + catalog link). Use this when the user gives a keyword or descriptive phrase (e.g. 'find a curved velvet sofa', 'lounge chairs'); use product_list when filtering purely by structured attributes. Triggers: 'find <x>', 'search for <x>', 'do you have <x>', 'I'm looking for <x>', 'cerca <x>', 'trova <x>', 'avete <x>', 'sto cercando <x>'. Default limit is 50. CRITICAL: preserve the markdown structure verbatim — keep the `` image lines and the tables, do not flatten into prose. NEVER reconstruct image URLs from asset_name yourself — the CDN file prefix is constant (`SM_`), not brand-derived.

• product_statsFree

  Catalog statistics grouped by category, brand, designer or year. Returns aggregate counts only — small, fixed-size payload. Triggers: 'how many products', 'catalog breakdown', 'how many sofas/chairs', 'products per brand', 'quanti prodotti', 'quanti per brand', 'statistiche catalogo', 'quante sedie avete'.

• style_guide_getFree

  Return the R3PLICA brand and output style guide as markdown. Covers card structure, typography, color palette, image aspect ratio (always square), hierarchy, mandatory link footer, and ready-to-copy empty card scaffolds (product card, finish swatch, both markdown and HTML). CALL THIS FIRST whenever you are about to generate any document, report, artifact or branded output about R3PLICA catalog content. The guide ensures outputs feel consistent across users and align with the platform's visual identity. Costs ~2KB of context but saves the conversation from inconsistent formatting and from inventing fields the platform doesn't expose (prices, lead times, certifications).

• Code scan41 source files scanned25/25
• Live reliabilityremote reachable in 1049ms20/20
• Tool poisoning16 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityverified namespace with website, no repo4/10

Safety score

77/100

higher than 50% of 4,460 AI and agents servers

Tools

16

the typical AI and agents server has 6

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote AI and agents server answers 100%

Response time

76 ms

faster than 91% of 2,331 AI and agents servers

Downloads a week

35

more than 25% of 1,538 AI and agents servers with a package

R3PLICA AI Connector: common questions

Is R3PLICA AI Connector MCP server safe?

Mostly: it is graded B (77/100). Read the R3PLICA AI Connector safety report

How do I install R3PLICA AI Connector?

It runs remotely at mcp.r3plica.space. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does R3PLICA AI Connector need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is R3PLICA AI Connector maintained?

The latest release is v2.3.3.

Is R3PLICA AI Connector up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of R3PLICA AI Connector?

Servers from other publishers that do the same job: Agent-Native Assets MCP server, Figma Context MCP server and Memanto MCP server.

How does R3PLICA AI Connector compare with other AI and agents MCP servers?

safety score 77/100 (higher than 50% of 4,460 AI and agents servers); tools 16 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.