Rico

com.tryricoPublished by tryrico.comOfficial publisherv17.0.0Updated Oct 26, 2026

Invents a brand, briefs each screen, and checks agent-built UI against it.

VerifiedStreamable HTTPWeb executableDeveloper ToolsMedia & Design

Overview

AI-generated overview

Rico generates a brand, briefs each UI screen, and checks agent-built interfaces against that brand, exposed as a remote MCP endpoint.

What you can do
  • Create a brand identity that the assistant can reuse across a project.
  • Produce per-screen briefs describing what each interface should contain and look like.
  • Review UI built by an agent and check it against the established brand.
  • No tool list is published, so the exact operations are only described at a high level in the registry entry.
When to use it
Useful when an assistant is building or reviewing user interfaces and needs a consistent brand direction, screen-level briefs, or a check that generated UI matches the intended brand.
Requirements
A remote MCP endpoint at mcp.tryrico.com using streamable HTTP. OAuth authentication is required, and a Rico API key is supplied in the X-Rico-Api-Key header, obtained from the provider's key page. No local runtime or packages are needed.
Before you install
The server requires an API key sent as the X-Rico-Api-Key header, so treat it as a secret and avoid exposing it in logs or shared configs. Brand and screen briefs you submit are sent to a third-party service. Reviewing agent-built UI may involve uploading or sharing your interface content with that service.

Installation

In SourceWeft

  1. Open Rico 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.tryrico%2Frico/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": {
    "rico": {
      "type": "http",
      "url": "https://mcp.tryrico.com/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

2
  1. v17.0.0LatestOct 23, 2026
  2. v14.0.0Oct 22, 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.