Skip to content

Quick start guide

Start by connecting your MCP-compatible tool and exploring the sample library, or build your first library.

  • Consume context — Use shared /instructions and @knowledge in your tools.
  • Curate context — Create and publish context libraries for your team.

Connect your tool to use shared /instructions and @knowledge from Sokket.

  1. Log in to your Sokket dashboard
  2. Select Connect in the header
  3. Select your tool
  4. Copy your organisation’s MCP endpoint URL
  5. Configure your tool with the MCP endpoint using your tool’s MCP settings
  6. Approve authentication
  7. In your tool, access your libraries in the agent chat
  8. Run a Sample Library /instruction (e.g., test-prompt) to confirm the connection

See Connect tools for tool-specific setup instructions.


Contributors and Owners can create and publish context libraries. A library usually contains:

  • /instructions - reusable prompt templates
  • @knowledge - reference material for your tools
  • $arguments - user input that makes /instructions dynamic
  • @references - how /instructions pull in @knowledge files
  1. Select + Library in the sidebar
  2. Name your library, e.g. build
  3. Press Enter to create the library
  1. Inside your library, select + Instruction
  2. Add a Name, e.g. create-spec.md
  3. Add a Description, e.g. “Create or update a product specification from a natural language feature description”
  4. In the content editor, add your guidelines or any other content you want your tool to use
  5. Save the file

If you want the /instruction to accept input, add an $argument directly into the content using $argumentName, e.g. “Summarise this feature request: $featureDetails”. Learn more about $arguments in the context section.

  1. Select + Knowledge
  2. Name the file, e.g. repository-cleanliness.md
  3. Add your content, e.g. “workflows, guidelines, API docs or schemas”
  4. Add a Description, e.g. “Guide to maintaining clean Git repositories with branch management and daily cleanup habits”
  5. Save the file

You can reference a @knowledge file from an /instruction using @fileName, e.g. “Use the guidelines in @repository-cleanliness”. Learn more about @knowledge in the context section.

Each file has its own Publish toggle. A library becomes available in tools only when its files are published. Drafts save automatically and remain visible only in the Sokket web app.

If you have not connected your tool yet, follow the Connect tools guide.

Open your tool’s context menu. Your published /instructions and @knowledge now appear in your MCP-compatible tool. Select one of your /instructions to generate output.