Skip to content

Frequently asked questions

A: Contributors create and publish libraries in the web app. Once published, anyone in your organisation can access them through connected tools like Cursor, Claude, or Gemini. It all works through the Model Context Protocol (MCP). See the get started guide to get started.

A: @knowledge files are static reference material like API specs, schemas, or guides. /instructions are prompt templates that reference @knowledge and accept $arguments. Together, they form libraries. See /instructions and @knowledge for details.

Q: How do $arguments and @references work in /instructions?

Section titled “Q: How do $arguments and @references work in /instructions?”

A: $arguments let users provide input to /instructions. Type $variableName in a /instruction to create a $argument. Each $argument needs a description and you set whether it’s required or optional. @references pull in @knowledge files. Type @knowledgeFileName to reference a @knowledge file. @reference descriptions are optional but help explain why that @knowledge is included. See creating /instructions for more.

Q: How do I add existing content (like a JSON schema or README) to Sokket?

Section titled “Q: How do I add existing content (like a JSON schema or README) to Sokket?”

A: Create a new @knowledge file in a library, then copy and paste content into the editor. Sokket uses markdown files (.md), so you can include JSON, code blocks, or any text content. See creating @knowledge files for details.

Q: What’s the difference between Draft and Published?

Section titled “Q: What’s the difference between Draft and Published?”

A: Draft files are private and only visible to Contributors in the web app. They’re not available to team tools. Published files are the live version teams can access through connected tools. When you create or edit a file, it starts as a Draft. Select Publish when you’re ready to make it available. See the publishing workflow for more.

Q: What happens when I edit a Published file?

Section titled “Q: What happens when I edit a Published file?”

A: When you edit a Published file, Sokket automatically creates a private Draft. The team continues to use the stable Published version until you select Publish on the new changes. See the publishing workflow for more.

Q: I see a library called “Sample Library” in my workspace. What is it?

Section titled “Q: I see a library called “Sample Library” in my workspace. What is it?”

A: The Sample Library is a regular library pre-installed in every new organisation. It contains example /instructions and @knowledge to help test the first tool connection. You can edit, publish, or delete it like any other library. See /instructions and @knowledge to understand how to create libraries.

A: Select the Connect button in the dashboard, copy the hosted MCP endpoint URL, and paste it into the tool’s MCP settings (Cursor, Claude, or Gemini). You’ll be prompted to authorise Sokket in the browser. See the connect tools guide for step-by-step instructions.

A: Sokket works with any tool that supports the Model Context Protocol. Specific setup instructions are provided for Cursor, Claude Desktop, and Gemini. Other MCP-compatible tools can connect using the organisation’s hosted MCP endpoint URL.

Q: Does Sokket support version history or Git-sync?

Section titled “Q: Does Sokket support version history or Git-sync?”

A: Sokket does not currently support version history or Git-sync. The Draft and Published workflow provides safe editing by keeping changes private until you publish.

Q: Can I have multiple libraries in my organisation?

Section titled “Q: Can I have multiple libraries in my organisation?”

A: Yes. Each organisation can have multiple libraries. Create separate libraries for different projects, teams, or contexts. Each library is published independently.

A: Deleting a library removes it from the organisation. Published content becomes unavailable to connected tools immediately. This action cannot be undone, so make sure the team no longer needs it.

A: Yes. You can rename libraries and files from the dashboard. If you rename a @knowledge file, make sure any /instructions that reference it use the new name.

Q: What happens if I reference a @knowledge file that doesn’t exist in a /instruction?

Section titled “Q: What happens if I reference a @knowledge file that doesn’t exist in a /instruction?”

A: You cannot publish a /instruction with broken @references. Sokket validates that all @references match existing @knowledge files before publishing. Fix or remove broken @references to publish.

Q: Can I use the same MCP endpoint URL for multiple tools?

Section titled “Q: Can I use the same MCP endpoint URL for multiple tools?”

A: Yes. The organisation’s hosted MCP endpoint URL works with all MCP-compatible tools. You can connect Cursor, Claude, Gemini, and other tools to the same endpoint to access libraries.

Q: How do I know if my connection is working?

Section titled “Q: How do I know if my connection is working?”

A: After connecting, check the tool’s context menu (e.g., type @ in Cursor). You should see commands from the Sample Library. If you don’t see them, check the MCP configuration and authorisation.

Q: What file formats are supported for @knowledge files?

Section titled “Q: What file formats are supported for @knowledge files?”

A: @knowledge files use Markdown (.md). You can include JSON, code blocks, diagrams, and other text content within Markdown. Paste content directly into the editor.

A: Unpublishing makes the library unavailable to connected tools. Team members can no longer access it. You can republish it later. Draft versions remain in the Sokket web app.

Q: Can I use Sokket with tools other than Cursor, Claude, or Gemini?

Section titled “Q: Can I use Sokket with tools other than Cursor, Claude, or Gemini?”

A: Yes. Sokket works with any tool that supports the Model Context Protocol. Use the organisation’s hosted MCP endpoint URL in the tool’s MCP settings. Some tools may require specific configuration formats.

Q: What happens if I delete a @knowledge file that’s referenced by a /instruction?

Section titled “Q: What happens if I delete a @knowledge file that’s referenced by a /instruction?”

A: You cannot delete a @knowledge file that’s referenced by a Published /instruction. Unpublish or remove the @reference first, then delete the @knowledge file. This prevents broken @references.