Brand.dev Mcp

Name: Brand.dev Mcp
Author: brand-dot-dev

@brand-dot-dev

代码仓库

关于 Brand.dev Mcp

Logos, primary colors, descriptions, classifications, and more from any domain with a single api call.

#api #brand-dev

基本信息

分类

其他

传输方式

stdio

发布者

brand-dot-dev

提交者

Yahia Bakour

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "brand_dev_api": {
      "command": "npx",
      "args": [
        "-y",
        "brand.dev-mcp",
        "--client=claude",
        "--tools=all"
      ],
      "env": {
        "BRAND_DEV_API_KEY": "My API Key"
      }
    }
  }
}

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Brand.dev MCP?

Brand.dev MCP is a TypeScript client library that provides convenient access to the Brand Dev REST API. It is generated with Stainless and intended for server‑side TypeScript or JavaScript applications needing brand data retrieval by domain.

How to use Brand.dev MCP?

Install the library via npm install brand.dev, import BrandDev, and create a client with your API key (defaults to process.env['BRAND_DEV_API_KEY']). Use the client’s methods, e.g., client.brand.retrieve({ domain: 'example.com' }), to make API calls. The full API documentation is available in api.md.

Key features of Brand.dev MCP

Full TypeScript definitions for all request params and response fields.
Automatic retries (2 times by default) with exponential backoff.
Configurable request timeouts (default 1 minute).
Access to raw HTTP response headers and status via .asResponse() or .withResponse().
Customisable logging with multiple log levels and support for third‑party loggers.
Supports Node.js 20+, Deno, Bun, modern browsers, Cloudflare Workers, Vercel Edge Runtime, and more.

Use cases of Brand.dev MCP

Retrieve brand information for a given domain.
Build server‑side applications that integrate with the Brand Dev API.
Add brand intelligence features to TypeScript or JavaScript projects.
Automate brand data lookups in CI/CD pipelines or backend services.

FAQ from Brand.dev MCP

What errors can occur when using Brand.dev MCP?

The library throws subclasses of APIError for non‑success status codes (4xx, 5xx). Specific error types include BadRequestError (400), AuthenticationError (401), PermissionDeniedError (403), NotFoundError (404), UnprocessableEntityError (422), RateLimitError (429), and InternalServerError (500+). Connection errors are also raised as APIConnectionError.

How are retries handled?

Certain errors (connection errors, 408, 409, 429, and >=500) are automatically retried up to 2 times with exponential backoff. You can disable or adjust this using the maxRetries option on the client or per request.

What runtimes are supported?

Supported runtimes include Node.js (20 LTS or later), Deno (v1.28+), Bun (1.0+), up‑to‑date web browsers (Chrome, Firefox, Safari, Edge), Cloudflare Workers, Vercel Edge Runtime, Jest (with "node" environment), and Nitro v2.6+. React Native is not supported.

Does Brand.dev MCP follow semantic versioning?

Yes, it generally follows SemVer conventions. Backwards‑incompatible changes may be released as minor versions only when they affect static types, undocumented internals, or are not expected to impact the vast majority of users.

How can I configure logging?

Set the log level via the BRAND_DEV_LOG environment variable or the logLevel client option (e.g., 'debug'). You can also provide a custom logger (e.g., pino, winston) using the logger option. Log messages are intended for debugging only and may change between releases.