integration-metadata

Name: integration-metadata
Availability: InStock
Author: Seer

Clarify how integration metadata configures the Seer frontend UI.

5|1|Updated Oct 14, 2025

Search Tags:#frontend #integration #oauth #config #metadata #providers #dynamic-ui

Ready to run

npx skills add https://github.com/seer-engg/seer --skill integration-metadata

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: integration-metadata
Source: https://github.com/seer-engg/seer/tree/main/.claude/skills/integration-metadata
Command: npx skills add https://github.com/seer-engg/seer --skill integration-metadata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarifies how integration metadata configures the frontend UI in Seer.

Core Features & Use Cases

Describes how INTEGRATION_CONFIGS drives the UI for integration cards (icon, display_name, scopes, and connect behavior).
Explains how dynamic discovery from registered tools augments metadata and how get_all_integration_metadata() merges data.
Shows how the frontend consumes the metadata API at startup to render providers, scopes, and detection patterns.

Quick Start

Review the frontend dynamic UI behavior by opening the integration metadata endpoint and inspecting the UI cards.

Frequently Asked Questions about integration-metadata

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How does integration metadata configure frontend UI for OAuth providers?▼

Integration metadata configures frontend UI by mapping static INTEGRATION_CONFIGS and dynamic tool discovery to render integration cards, group providers, and support OAuth connections. The frontend consumes this metadata API at startup to display icons, display names, and scopes.

How do I render dynamic integration cards from provider metadata?▼

To render dynamic integration cards, the frontend consumes the metadata API assembled by get_all_integration_metadata() at startup. This function merges static INTEGRATION_CONFIGS with dynamically discovered tools to provide display names, icons, scopes, and connect behaviors for UI rendering.

What is the difference between static INTEGRATION_CONFIGS and dynamic tool discovery?▼

Static INTEGRATION_CONFIGS provides fixed UI properties like icons, display names, scopes, and connect behavior, while dynamic tool discovery augments this metadata with registered tools. The get_all_integration_metadata() function merges both sources to assemble the complete metadata used by the frontend.

Can I use integration metadata to group OAuth providers in the frontend?▼

Yes, integration metadata supports grouping OAuth providers in the frontend. The metadata assembled by get_all_integration_metadata() specifies how the frontend renders integration cards and groups them by provider, while also supporting OAuth connection behaviors and scope displays.

Where do I inspect integration metadata to debug frontend dynamic UI behavior?▼

To debug frontend dynamic UI behavior, inspect the integration metadata endpoint to review the UI cards. This endpoint exposes the merged output of static INTEGRATION_CONFIGS and dynamic tool discovery, showing exactly how providers, scopes, and detection patterns are configured for rendering.