MCP registry
The MCP registry is your source of reusable bridge templates for common SaaS tools.
What a template includes
Section titled “What a template includes”- Product target and expected page context.
- Selector mappings and extraction types.
- Normalization hints and field semantics.
- Version metadata and compatibility notes.
Example catalog
Section titled “Example catalog”| Template | Domain | Version | Typical fields |
|---|---|---|---|
| Salesforce | CRM | v2.1.0 | Lead IDs, opportunity stage, owner |
| Jira Software | DevOps | v1.4.2 | Issue key, sprint, assignee |
| Zendesk | Support | v1.0.5 | Ticket status, priority, requester |
| Stripe | Finance | v3.0.0 | Payment amount, customer ID, status |
| Linear | DevOps | v1.1.2 | Issue state, project, cycle |
| HubSpot | CRM | v2.0.1 | Contact fields, campaign metadata |
Installation workflow
Section titled “Installation workflow”- Select a template by domain.
- Validate selector compatibility against your tenant UI.
- Install into local config namespace.
- Run a dry extraction in Console playground.
- Promote version to team baseline.
Template quality rules
Section titled “Template quality rules”- Prefer semantic selectors over brittle nth-child chains.
- Include fallback selectors where possible.
- Version bump for any mapping-breaking change.
- Document known UI variants by environment.
Search and filtering strategy
Section titled “Search and filtering strategy”- Search by product first.
- Filter by domain second.
- Compare versions before install.
- Keep local override notes for tenant-specific customization.