​
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?

​
How Registry Forking Works

When you fork a registry, Pylee performs the following actions:
1

Registry Structure Copy

Creates a new registry under your organization with the same structure as the original
2

Server References

Establishes references to all MCP servers in the original registry without duplicating them
3

Configuration Inheritance

Copies server configurations, descriptions, and metadata that you can then customize
4

Permission Setup

Sets up initial permissions based on your organization’s default policies

​
Forking a Registry

​
Finding Registries to Fork

  1. Navigate to Registry Browser in your Pylee dashboard
  2. Browse Community section to find popular public registries
  3. Filter by category (Developer Tools, Data & Analytics, Productivity, etc.)
  4. Review server lists to find registries that match your needs

​
Forking Process

1

Select Registry

Navigate to the registry you want to fork and click the “Fork Registry” button
2

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
3

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
4

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

  1. Check for Updates - Review changes in the source registry
  2. Select Changes - Choose which updates to apply to your fork
  3. Test Changes - Validate updates in a staging environment
  4. Apply Updates - Merge approved changes into your fork

​
Fork Maintenance

1

Monitor Server Health

Track the status of referenced servers and receive alerts for issues
2

Review Usage Analytics

Analyze which servers are being used and optimize your registry accordingly
3

Update Permissions

Regularly review and update access controls as your team grows
4

Manage Dependencies

Handle updates when referenced servers change or become unavailable

​
Fork Types and Strategies

​
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 policiesSolution: Override specific configurations in your fork or exclude problematic servers

​
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.