Libraries

Libraries are collections of /instructions and @knowledge organised by project, team, or purpose. A library groups related context together and publishes it as a unit to your MCP endpoint.

How to manage libraries

As a Contributor or Owner, you can manage all your libraries from the Sokket sidebar.

Create a new library

1. In the sidebar, select the + button next to the library selector
2. Enter a name for your new library
3. Press Enter to create the library

Rename or delete a library

1. First, select the library you wish to change using the main library dropdown
2. Once it’s selected, select the (...) menu icon next to its name
3. Select Rename or Delete from the dropdown menu to perform that action on the selected library

A strategy for organising libraries

A good library structure makes context discoverable as your team grows. Use clear naming conventions so team members know what each library contains. Here are three approaches: By Project — Use project-specific names like Mobile-App-Refactor or Project-Phoenix-API when context (like API schemas) is specific to that project. By Team — Use team names like Frontend-Team or Platform-SRE for team-wide best practices, style guides, and common workflows. By Purpose — Use purpose-based names like Code-Generation, Debugging-Tools, or Documentation for general-purpose utilities that multiple teams might use.

The sample library

Every new organisation comes with a “Sample Library.” This is a regular library pre-filled with example /instructions and @knowledge that you can edit, publish, or delete like any other library.

It is designed to give you a working example of how to structure context. It helps you test your first tool connection right away.

Next Steps

Learn more about /instructions, @knowledge, or context engineering.