Birdeye MCP Skill
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.
Prerequisites
- -
uxc is installed and available in PATH. - Network access to
https://mcp.birdeye.so/mcp. - A Birdeye API key is available.
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.
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.
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.
- Prefer narrow symbol, address, or chain scopes before broad scans.
- Parse the JSON envelope first, then inspect
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. - INLINECODE24 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.
References
- INLINECODE31
Birdeye MCP 技能
使用此技能通过 uxc 运行 Birdeye MCP 操作。
复用 uxc 技能进行共享协议发现、输出解析以及通用身份验证/绑定流程。
前提条件
- - uxc 已安装并位于 PATH 环境变量中。
- 可访问 https://mcp.birdeye.so/mcp 的网络连接。
- 拥有 Birdeye API 密钥。
核心工作流程
- 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 BIRDEYEAPI_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
- 然后使用
-h 检查所需的具体操作
- 5. 优先使用只读发现，然后进行更广泛的监控查询。
能力重点
Birdeye MCP 适用于以下读取密集型工作流程：
- - 代币市场数据
- 趋势或发现视图
- 价格监控
- DEX 流动性或交易背景
- 代币或交易对查询
在身份验证设置后，检查 birdeye-mcp-cli -h 以获取当前工具列表。Birdeye MCP 仍处于测试阶段，实时工具表面可能独立于此包装技能而演变。
推荐使用模式
- 1. 从一个集中的读取目标开始：
- 某个代币的当前市场数据
- 趋势代币或叙事发现
- DEX 流动性或价格变动检查
- 2. 先运行主机帮助，再运行操作帮助。
- 在广泛扫描前，优先使用窄范围的符号、地址或链范围。
- 先解析 JSON 信封，再检查 data。
防护措施
- - 保持自动化使用 JSON 输出信封；不要依赖 --text。
- 先解析稳定字段：ok、kind、protocol、data、error。
- 使用 birdeye-mcp-cli 作为默认命令路径。
- birdeye-mcp-cli ... 等同于 uxc https://mcp.birdeye.so/mcp ...。
- 如果未认证探测或运行时调用返回 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 apikey --header X-API-KEY={{secret}} --secret-env BIRDEYEAPI_KEY
- - Birdeye MCP 处于测试阶段。不要硬编码关于实时工具列表或参数名称的假设；先检查 -h。
- 保持初始查询小而具体，因为市场/发现工具可能返回广泛的数据集。
- 将此技能视为只读市场和发现访问，而非交易或执行界面。
参考
- references/usage-patterns.md
