Forking Registries
Learn how to fork registries to create your own customized collections of MCP servers
Forking Registries
Forking allows you to copy an existing registry into your organization while maintaining references to the original servers. This creates a customizable collection that you can modify without affecting the source registry.
Registry Forking: When you fork a registry, Pylee creates a new registry under your organization that references the same MCP servers as the original. The servers remain in their original locations - only the registry configuration is copied.
What is Registry Forking?
Registry forking is the process of creating a copy of an existing registry (community, organization, or personal) into your own organization’s registry collection. Unlike traditional code forking, registry forking creates references rather than duplicates.
Reference-Based
Servers stay in their original locations and are referenced by your forked registry
Customizable
Modify server configurations, permissions, and metadata in your fork
Why Fork a Registry?
Customization
Customization
Tailor registries to your needs
- Remove servers you don’t need
- Add your own custom servers to the collection
- Modify server configurations and permissions
- Create organization-specific documentation and naming
Control and Governance
Control and Governance
Maintain organizational control
- Review and approve servers before team access
- Set organization-specific usage policies
- Control version updates and server changes
- Maintain compliance with internal security requirements
Team Collaboration
Team Collaboration
Create shared team resources
- Build curated collections for specific projects
- Share customized workflows across teams
- Maintain consistent tooling across departments
- Create training and onboarding registries
How Registry Forking Works
When you fork a registry, Pylee performs the following actions:
Registry Structure Copy
Creates a new registry under your organization with the same structure as the original
Server References
Establishes references to all MCP servers in the original registry without duplicating them
Configuration Inheritance
Copies server configurations, descriptions, and metadata that you can then customize
Permission Setup
Sets up initial permissions based on your organization’s default policies
Forking a Registry
Finding Registries to Fork
- Navigate to Registry Browser in your Pylee dashboard
- Browse Community section to find popular public registries
- Filter by category (Developer Tools, Data & Analytics, Productivity, etc.)
- Review server lists to find registries that match your needs
- Navigate to Registry Browser in your Pylee dashboard
- Browse Community section to find popular public registries
- Filter by category (Developer Tools, Data & Analytics, Productivity, etc.)
- Review server lists to find registries that match your needs
- Access Registry Directory through the dashboard
- Browse Public Organization Registries shared by other companies
- Search by industry or use case to find relevant registries
- Check permissions to ensure you can fork the registry
- Visit Partner Registries section if you have partnership agreements
- Access Educational Registries if you’re part of academic programs
- Browse Industry Collections for sector-specific tool sets
Forking Process
Select Registry
Navigate to the registry you want to fork and click the “Fork Registry” button
Configure Fork Settings
Registry Details:
- Name your forked registry
- Add a description for your organization
- Choose visibility settings (private, organization, public)
Server Selection:
- Choose which servers to include in your fork
- Set initial access permissions for each server
- Configure any organization-specific settings
Set Permissions
Access Control:
- Define who can use the forked registry
- Set server-level permissions
- Configure admin and contributor roles
Usage Policies:
- Set rate limits and quotas
- Define allowed usage scenarios
- Configure monitoring and logging
Review and Create
- Review your fork configuration
- Verify server references are correct
- Click “Create Fork” to complete the process
Managing Forked Registries
Customizing Your Fork
After forking, you can customize your registry:
Add Custom Servers
Include your organization’s proprietary MCP servers alongside the forked ones
Modify Configurations
Adjust server settings, descriptions, and usage parameters
Update Permissions
Fine-tune access controls for different user groups
Create Documentation
Add organization-specific guides and usage instructions
Syncing with Source Registry
- Check for Updates - Review changes in the source registry
- Select Changes - Choose which updates to apply to your fork
- Test Changes - Validate updates in a staging environment
- Apply Updates - Merge approved changes into your fork
- Check for Updates - Review changes in the source registry
- Select Changes - Choose which updates to apply to your fork
- Test Changes - Validate updates in a staging environment
- Apply Updates - Merge approved changes into your fork
- Configure Auto-Sync in your fork settings
- Set Update Policies - Define which types of changes to sync automatically
- Review Notifications - Monitor sync activities and conflicts
- Handle Conflicts - Resolve any conflicts between your customizations and source updates
Fork Maintenance
Monitor Server Health
Track the status of referenced servers and receive alerts for issues
Review Usage Analytics
Analyze which servers are being used and optimize your registry accordingly
Update Permissions
Regularly review and update access controls as your team grows
Manage Dependencies
Handle updates when referenced servers change or become unavailable
Fork Types and Strategies
Complete Fork
Complete Fork
Copy the entire registry
- Include all servers from the source registry
- Maintain the same organizational structure
- Best for: Teams wanting a complete toolkit with custom modifications
Selective Fork
Selective Fork
Choose specific servers to include
- Pick only the servers your team needs
- Create focused, lightweight registries
- Best for: Specialized teams or specific project requirements
Enhanced Fork
Enhanced Fork
Fork and extend with custom servers
- Include servers from the source registry
- Add your organization’s proprietary tools
- Best for: Organizations with both public and private tool requirements
Best Practices
Plan Before Forking
Identify your specific needs and which servers you actually require
Organize Thoughtfully
Structure your fork logically for your team’s workflows
Document Changes
Keep clear records of customizations and why they were made
Regular Maintenance
Schedule periodic reviews and updates of your forked registries
Common Use Cases
Development Teams
Fork popular developer tool registries and add your organization’s internal APIs and custom development servers.
Data Science Teams
Start with community data and analytics registries, then add proprietary data sources and custom model APIs.
Customer Support
Fork productivity tool registries and customize them with your ticketing systems and internal knowledge bases.
Sales Teams
Build from CRM and communication tool registries, adding your specific sales tools and customer data integrations.
Troubleshooting Forks
Server Unavailability: If a referenced server becomes unavailable, your fork will show warnings. You can either wait for the server to return or remove it from your fork.
Common Issues
Problem: Server configurations conflict with your organization’s policies
Solution: Override specific configurations in your fork or exclude problematic servers
Problem: Server configurations conflict with your organization’s policies
Solution: Override specific configurations in your fork or exclude problematic servers
Problem: Team members can’t access forked servers
Solution: Review and update permission settings in your fork configuration
Problem: Unable to sync updates from the source registry
Solution: Check for conflicts with your customizations and resolve manually
Next Steps
Browse Registries
Explore available registries to find ones worth forking
Manage Forks
View and manage your existing forked registries
Need Help?
If you encounter issues with registry forking, check our troubleshooting guide or contact support through your dashboard.
Forking Registries
Learn how to fork registries to create your own customized collections of MCP servers
Forking Registries
Forking allows you to copy an existing registry into your organization while maintaining references to the original servers. This creates a customizable collection that you can modify without affecting the source registry.
Registry Forking: When you fork a registry, Pylee creates a new registry under your organization that references the same MCP servers as the original. The servers remain in their original locations - only the registry configuration is copied.
What is Registry Forking?
Registry forking is the process of creating a copy of an existing registry (community, organization, or personal) into your own organization’s registry collection. Unlike traditional code forking, registry forking creates references rather than duplicates.
Reference-Based
Servers stay in their original locations and are referenced by your forked registry
Customizable
Modify server configurations, permissions, and metadata in your fork
Why Fork a Registry?
Customization
Customization
Tailor registries to your needs
- Remove servers you don’t need
- Add your own custom servers to the collection
- Modify server configurations and permissions
- Create organization-specific documentation and naming
Control and Governance
Control and Governance
Maintain organizational control
- Review and approve servers before team access
- Set organization-specific usage policies
- Control version updates and server changes
- Maintain compliance with internal security requirements
Team Collaboration
Team Collaboration
Create shared team resources
- Build curated collections for specific projects
- Share customized workflows across teams
- Maintain consistent tooling across departments
- Create training and onboarding registries
How Registry Forking Works
When you fork a registry, Pylee performs the following actions:
Registry Structure Copy
Creates a new registry under your organization with the same structure as the original
Server References
Establishes references to all MCP servers in the original registry without duplicating them
Configuration Inheritance
Copies server configurations, descriptions, and metadata that you can then customize
Permission Setup
Sets up initial permissions based on your organization’s default policies
Forking a Registry
Finding Registries to Fork
- Navigate to Registry Browser in your Pylee dashboard
- Browse Community section to find popular public registries
- Filter by category (Developer Tools, Data & Analytics, Productivity, etc.)
- Review server lists to find registries that match your needs
- Navigate to Registry Browser in your Pylee dashboard
- Browse Community section to find popular public registries
- Filter by category (Developer Tools, Data & Analytics, Productivity, etc.)
- Review server lists to find registries that match your needs
- Access Registry Directory through the dashboard
- Browse Public Organization Registries shared by other companies
- Search by industry or use case to find relevant registries
- Check permissions to ensure you can fork the registry
- Visit Partner Registries section if you have partnership agreements
- Access Educational Registries if you’re part of academic programs
- Browse Industry Collections for sector-specific tool sets
Forking Process
Select Registry
Navigate to the registry you want to fork and click the “Fork Registry” button
Configure Fork Settings
Registry Details:
- Name your forked registry
- Add a description for your organization
- Choose visibility settings (private, organization, public)
Server Selection:
- Choose which servers to include in your fork
- Set initial access permissions for each server
- Configure any organization-specific settings
Set Permissions
Access Control:
- Define who can use the forked registry
- Set server-level permissions
- Configure admin and contributor roles
Usage Policies:
- Set rate limits and quotas
- Define allowed usage scenarios
- Configure monitoring and logging
Review and Create
- Review your fork configuration
- Verify server references are correct
- Click “Create Fork” to complete the process
Managing Forked Registries
Customizing Your Fork
After forking, you can customize your registry:
Add Custom Servers
Include your organization’s proprietary MCP servers alongside the forked ones
Modify Configurations
Adjust server settings, descriptions, and usage parameters
Update Permissions
Fine-tune access controls for different user groups
Create Documentation
Add organization-specific guides and usage instructions
Syncing with Source Registry
- Check for Updates - Review changes in the source registry
- Select Changes - Choose which updates to apply to your fork
- Test Changes - Validate updates in a staging environment
- Apply Updates - Merge approved changes into your fork
- Check for Updates - Review changes in the source registry
- Select Changes - Choose which updates to apply to your fork
- Test Changes - Validate updates in a staging environment
- Apply Updates - Merge approved changes into your fork
- Configure Auto-Sync in your fork settings
- Set Update Policies - Define which types of changes to sync automatically
- Review Notifications - Monitor sync activities and conflicts
- Handle Conflicts - Resolve any conflicts between your customizations and source updates
Fork Maintenance
Monitor Server Health
Track the status of referenced servers and receive alerts for issues
Review Usage Analytics
Analyze which servers are being used and optimize your registry accordingly
Update Permissions
Regularly review and update access controls as your team grows
Manage Dependencies
Handle updates when referenced servers change or become unavailable
Fork Types and Strategies
Complete Fork
Complete Fork
Copy the entire registry
- Include all servers from the source registry
- Maintain the same organizational structure
- Best for: Teams wanting a complete toolkit with custom modifications
Selective Fork
Selective Fork
Choose specific servers to include
- Pick only the servers your team needs
- Create focused, lightweight registries
- Best for: Specialized teams or specific project requirements
Enhanced Fork
Enhanced Fork
Fork and extend with custom servers
- Include servers from the source registry
- Add your organization’s proprietary tools
- Best for: Organizations with both public and private tool requirements
Best Practices
Plan Before Forking
Identify your specific needs and which servers you actually require
Organize Thoughtfully
Structure your fork logically for your team’s workflows
Document Changes
Keep clear records of customizations and why they were made
Regular Maintenance
Schedule periodic reviews and updates of your forked registries
Common Use Cases
Development Teams
Fork popular developer tool registries and add your organization’s internal APIs and custom development servers.
Data Science Teams
Start with community data and analytics registries, then add proprietary data sources and custom model APIs.
Customer Support
Fork productivity tool registries and customize them with your ticketing systems and internal knowledge bases.
Sales Teams
Build from CRM and communication tool registries, adding your specific sales tools and customer data integrations.
Troubleshooting Forks
Server Unavailability: If a referenced server becomes unavailable, your fork will show warnings. You can either wait for the server to return or remove it from your fork.
Common Issues
Problem: Server configurations conflict with your organization’s policies
Solution: Override specific configurations in your fork or exclude problematic servers
Problem: Server configurations conflict with your organization’s policies
Solution: Override specific configurations in your fork or exclude problematic servers
Problem: Team members can’t access forked servers
Solution: Review and update permission settings in your fork configuration
Problem: Unable to sync updates from the source registry
Solution: Check for conflicts with your customizations and resolve manually
Next Steps
Browse Registries
Explore available registries to find ones worth forking
Manage Forks
View and manage your existing forked registries
Need Help?
If you encounter issues with registry forking, check our troubleshooting guide or contact support through your dashboard.