Back to Details

birdeye-mcp-skill

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Birdeye MCP Skill

Birdeye MCP 技能

Use this skill to run Birdeye MCP operations through 
uxc
.
Reuse the 
uxc
skill for shared protocol discovery, output parsing, and generic auth/binding flows.
使用本技能通过
uxc
执行Birdeye MCP操作。
复用
uxc
技能以实现共享协议发现、输出解析以及通用认证/绑定流程。

Prerequisites

前置条件

  • uxc
    is installed and available in 
    PATH
    .
  • Network access to 
    https://mcp.birdeye.so/mcp
    .
  • A Birdeye API key is available.
  • uxc
    已安装且可在
    PATH
    中访问。
  • 可访问网络地址
    https://mcp.birdeye.so/mcp
    。
  • 拥有Birdeye API密钥。

Core Workflow

核心工作流

  1. Confirm endpoint and protocol with help-first probing: 
    • uxc https://mcp.birdeye.so/mcp -h
    • expected unauthenticated behavior today: 
      401 Unauthorized
  2. Configure credential/binding for repeatable auth: 
    • uxc auth credential set birdeye-mcp --auth-type api_key --header "X-API-KEY={{secret}}" --secret-env BIRDEYE_API_KEY
    • uxc auth credential set birdeye-mcp --auth-type api_key --header "X-API-KEY={{secret}}" --secret-op op://Engineering/birdeye/api-key
    • uxc auth binding add --id birdeye-mcp --host mcp.birdeye.so --path-prefix /mcp --scheme https --credential birdeye-mcp --priority 100
  3. Use fixed link command by default: 
    • command -v birdeye-mcp-cli
    • If missing, create it: 
      uxc link birdeye-mcp-cli https://mcp.birdeye.so/mcp
    • birdeye-mcp-cli -h
  4. Inspect the live tool list before execution: 
    • birdeye-mcp-cli -h
    • then inspect the specific operation you need with 
      <operation> -h
  5. Prefer read-only discovery first, then broader monitoring queries.
  1. 通过以帮助为导向的探测确认端点和协议： 
    • uxc https://mcp.birdeye.so/mcp -h
    • 当前预期的未认证行为：
      401 Unauthorized
  2. 配置凭证/绑定以实现可重复认证： 
    • uxc auth credential set birdeye-mcp --auth-type api_key --header "X-API-KEY={{secret}}" --secret-env BIRDEYE_API_KEY
    • uxc auth credential set birdeye-mcp --auth-type api_key --header "X-API-KEY={{secret}}" --secret-op op://Engineering/birdeye/api-key
    • uxc auth binding add --id birdeye-mcp --host mcp.birdeye.so --path-prefix /mcp --scheme https --credential birdeye-mcp --priority 100
  3. 默认使用固定链接命令： 
    • command -v birdeye-mcp-cli
    • 若缺失，创建链接：
      uxc link birdeye-mcp-cli https://mcp.birdeye.so/mcp
    • birdeye-mcp-cli -h
  4. 执行前查看实时工具列表： 
    • birdeye-mcp-cli -h
    • 随后使用
      <operation> -h
      查看你所需的具体操作
  5. 优先选择只读发现操作，再进行更广泛的监控查询。

Capability Focus

能力聚焦

Birdeye MCP is a fit for these read-heavy workflows:
  • token market data
  • trending or discovery views
  • price monitoring
  • DEX liquidity or trading context
  • token or pair lookup
Inspect 
birdeye-mcp-cli -h
after auth setup for the current tool list. Birdeye MCP is still in beta and the live tool surface may evolve independently of this wrapper skill.
Birdeye MCP适用于以下读密集型工作流：
  • 代币市场数据
  • 趋势或发现视图
  • 价格监控
  • DEX流动性或交易场景
  • 代币或交易对查询
完成认证设置后，查看
birdeye-mcp-cli -h
获取当前工具列表。Birdeye MCP仍处于测试阶段，实时工具界面可能独立于本包装技能进行更新。

Recommended Usage Pattern

推荐使用模式

  1. Start from one focused read goal:
    • current market data for a token
    • trending token or narrative discovery
    • DEX liquidity or price movement checks
  2. Run host help first, then operation help.
  3. Prefer narrow symbol, address, or chain scopes before broad scans.
  4. Parse the JSON envelope first, then inspect 
    data
    .
  1. 从一个明确的读取目标开始：
    • 某代币的当前市场数据
    • 热门代币或叙事发现
    • DEX流动性或价格变动检查
  2. 先查看主机帮助，再查看操作帮助。
  3. 在进行广泛扫描前，优先选择范围狭窄的代币符号、地址或链。
  4. 先解析JSON信封，再查看
    data
    字段。

Guardrails

防护规则

  • Keep automation on JSON output envelope; do not rely on 
    --text
    .
  • Parse stable fields first: 
    ok
    , 
    kind
    , 
    protocol
    , 
    data
    , 
    error
    .
  • Use 
    birdeye-mcp-cli
    as default command path.
  • birdeye-mcp-cli <operation> ...
    is equivalent to 
    uxc https://mcp.birdeye.so/mcp <operation> ...
    .
  • If unauthenticated probe or runtime call returns 
    401 Unauthorized
    :
    • confirm auth binding matches endpoint with 
      uxc auth binding match https://mcp.birdeye.so/mcp
    • confirm credential shape with 
      uxc auth credential info birdeye-mcp
    • reset credential as API-key header if needed: 
      uxc auth credential set birdeye-mcp --auth-type api_key --header "X-API-KEY={{secret}}" --secret-env BIRDEYE_API_KEY
  • Birdeye MCP is beta. Do not hardcode assumptions about the live tool list or argument names; inspect 
    -h
    first.
  • Keep initial queries small and specific because market/discovery tools can return wide datasets.
  • Treat this skill as read-only market and discovery access, not a trading or execution surface.
  • 自动化操作仅基于JSON输出信封；不要依赖
    --text
    参数。
  • 优先解析稳定字段：
    ok
    、
    kind
    、
    protocol
    、
    data
    、
    error
    。
  • 使用
    birdeye-mcp-cli
    作为默认命令路径。
  • birdeye-mcp-cli <operation> ...
    等同于
    uxc https://mcp.birdeye.so/mcp <operation> ...
    。
  • 若未认证探测或运行时调用返回
    401 Unauthorized
    ：
    • 使用
      uxc auth binding match https://mcp.birdeye.so/mcp
      确认认证绑定与端点匹配
    • 使用
      uxc auth credential info birdeye-mcp
      确认凭证格式
    • 若需要，重置凭证为API密钥头：
      uxc auth credential set birdeye-mcp --auth-type api_key --header "X-API-KEY={{secret}}" --secret-env BIRDEYE_API_KEY
  • Birdeye MCP处于测试阶段。不要硬编码关于实时工具列表或参数名称的假设；先查看
    -h
    。
  • 初始查询保持小范围且具体，因为市场/发现工具可能返回大量数据集。
  • 将本技能视为只读的市场与发现访问工具，而非交易或执行平台。

References

参考资料

  • Invocation patterns: 
    • references/usage-patterns.md
  • 调用模式： 
    • references/usage-patterns.md