Spotify Portal Actions Registry

AiKA can use Portal-native actions via the Spotify Portal Actions Registry. These actions are automatically exposed to AiKA via the MCP Actions Backend plugin.

Available Actions in Portal

Portal includes several pre-registered actions in the Actions Registry:

• search - Search for information across company internal systems, documentation, and software catalogs.
• query-semantic-search-engine - Perform semantic (meaning-based) search across indexed knowledge sources.
• get-catalog-entity - Retrieve detailed information about a specific entity in the software catalog.
• get-datasets-by-registry-ids - Fetch datasets from the data registry using their IDs.
• get-dbt-project-by-registry-id - Fetch a dbt project from the data registry using its ID.
• get-entity-overlay - Retrieve overlay metadata for a given entity in the software catalog.

For detailed information about how AiKA uses the search actions, see Searching for Information.

Adding custom actions

To add custom actions and make them available to AiKA:

1. Register the action in the Actions Registry (see MCP Actions Backend documentation for more details)
2. Update the backend.actions.pluginSources configuration in Portal to include the plugin that contains the action.

Related Documentation

Spotify Portal Documentation

• AiKA Overview - Understanding AiKA capabilities
• MCP Servers - Third-party MCP server integration
• AiKA Getting Started - Setting up AiKA in Portal

External Documentation

• MCP Actions Backend - NPM package documentation
• Backstage Actions Registry Service - Core service for action registration