Frequently asked questions
These FAQs cover how Sokket behaves in real workflows, including MCP, publishing, seats, and billing.
We’d love your input: use the feedback button in your dashboard to suggest changes or new features.
Q: How does MCP work with Sokket -who decides what’s sent?
Section titled “Q: How does MCP work with Sokket -who decides what’s sent?”A: Your AI coding assistant connects to Sokket’s MCP endpoint and requests the prompts and resources it needs (e.g. when you run an instruction or the model needs referenced knowledge). Sokket sends only what the tool asks for. Context is not injected automatically -the tool and you decide what the model sees.
Q: How does Sokket deliver context to my AI coding assistant?
Section titled “Q: How does Sokket deliver context to my AI coding assistant?”A: Sokket delivers context via MCP, on demand, only when your tool requests it. For typical library sizes, this is fast and should feel close to local. Only the fetch request hits Sokket’s servers, response content is not stored as part of model usage.
Q: What naming rules prevent broken @references?
Section titled “Q: What naming rules prevent broken @references?”A: Reference names (the @reference syntax) must match the knowledge filename exactly, including casing. Avoid spaces in filenames and references; use hyphens or underscores. Avoid special characters; use letters, numbers, hyphens, and underscores.
Q: What do I need to set for instruction arguments?
Section titled “Q: What do I need to set for instruction arguments?”A: Each $argument in an instruction is defined in the editor: type $, then the argument name, then press Enter to open the argument popover. In the popover you can set a description and mark it as required or optional. These map directly to the MCP shape (name, description, required). The instruction description is still set in the Properties panel. Without a description and with arguments configured, Publish stays disabled until validation passes.
Q: Does Sokket version prompts? Is there version history or Git-sync?
Section titled “Q: Does Sokket version prompts? Is there version history or Git-sync?”A: Not yet. You have a single published version per file; the Draft and Published workflow keeps changes private until you publish. The editor autosaves; there is no Save button. In Properties you can Revert to last saved version to restore the last autosaved draft, or use undo/redo in the editor. Version history is planned.
Q: What happens when a published file has unpublished edits?
Section titled “Q: What happens when a published file has unpublished edits?”A: MCP keeps serving the last published version until you use Publish changes. The editor autosaves, so your draft diverges from what’s live. The sidebar shows an amber status and the Properties panel shows a warning so you know the tool isn’t seeing your latest draft yet.
Q: Why not just store prompts in GitHub (or Cursor rules, or a Google Doc)?
Section titled “Q: Why not just store prompts in GitHub (or Cursor rules, or a Google Doc)?”A: GitHub is file storage with no MCP integration; Cursor rules are per-user and not shared; a shared doc doesn’t connect to AI coding assistants. Sokket is a hosted MCP server with publish gating and role-based access -one team-owned context layer that connects to MCP-compatible tools so everyone uses the same instructions and knowledge in their assistant. Sensitive prompts and internal docs stay in a private library and never touch git history; your repos stay focused on the product.
Q: What’s the difference between an editor seat and a read-only seat?
Section titled “Q: What’s the difference between an editor seat and a read-only seat?”A: Editor seats are paid seats for users who create, edit, and manage team libraries. Read-only seats are free. Users with read-only seats can connect to and use libraries in their tools but can’t edit them. The Team plan includes unlimited read-only seats. See sharing and seat types for more.
Q: What’s the difference between an organisation owner seat and an editor seat?
Section titled “Q: What’s the difference between an organisation owner seat and an editor seat?”A: Organisation owners can manage billing, seats, and team settings in addition to creating and editing content. Editors can create, edit, and publish libraries but cannot manage billing. Both use paid seats.
Q: What happens if I remove a user who created content?
Section titled “Q: What happens if I remove a user who created content?”A: The content stays in the organisation. Ownership is organisational, not per-user -libraries and files are not orphaned. Any editor or owner can continue to edit and publish it. Only the removed user loses access.
Q: Can we have more than one organisation owner?
Section titled “Q: Can we have more than one organisation owner?”A: Yes. An organisation can have multiple organisation owner seats, each with full access to billing, seats, and team settings. See the billing guide for more.
Q: How many editor seats can I have on the free trial?
Section titled “Q: How many editor seats can I have on the free trial?”A: The 14-day trial includes one editor seat (the organisation owner). Unlimited read-only seats can be added; they receive a welcome email and the seat is claimed when they sign in. See billing and subscriptions for full details.
Q: What happens when my trial ends?
Section titled “Q: What happens when my trial ends?”A: All users (including the owner) become read-only. Published libraries remain available via MCP; no one can create or edit until you upgrade. You are not charged without explicit action -upgrade when ready to restore editor access.
Q: What happens to published libraries if all editor seats are removed or the subscription lapses?
Section titled “Q: What happens to published libraries if all editor seats are removed or the subscription lapses?”A: Published content remains available to connected tools for read-only access. Users with read-only seats (and anyone still connected) can continue to use published libraries via MCP. No one can create or edit until editor seats are restored or the subscription is reactivated.
Q: Can I change my plan or cancel at any time?
Section titled “Q: Can I change my plan or cancel at any time?”A: Yes. Subscription, payment, and cancellation are managed in Polar (Settings > Billing > Manage Billing). Seat add/remove and role changes are done in Sokket (Settings > Team). See billing and subscriptions and team management for steps.
Q: If I remove an editor seat, when does it take effect?
Section titled “Q: If I remove an editor seat, when does it take effect?”A: Seat count changes in Polar (Manage Billing) take effect at the start of your next billing cycle. To revoke a user’s editor access immediately, change their role to read-only in Settings > Team -that frees the seat in Sokket for someone else but does not reduce your bill until you also reduce the seat count in the Polar billing portal.
Q: Why do I have to re-authorise Sokket in my assistant after a while?
Section titled “Q: Why do I have to re-authorise Sokket in my assistant after a while?”A: Sessions can expire after a period of inactivity. When your assistant asks you to sign in again, complete the browser auth flow - you don’t need to change your MCP URL or config. We’re tracking this in GitHub #198.
Q: Why don’t new libraries or new files appear until I reset MCP?
Section titled “Q: Why don’t new libraries or new files appear until I reset MCP?”A: Most MCP clients don’t yet support the “list changed” notification that would tell them to refresh. So new libraries and new or updated instructions and knowledge often don’t show up until you refresh the MCP connection. In Cursor: Settings → Tools & MCP → remove and re-add the Sokket server (same URL). Other tools may have a “reload MCP” option. We’re tracking this in GitHub #198. A full fix would require MCP clients to support these notifications and/or a persistent connection (we may explore the latter later).
Q: Why are my published changes not showing in my tool?
Section titled “Q: Why are my published changes not showing in my tool?”A: Some tools cache MCP content. Try refreshing the MCP connection or restarting the tool, then run the instruction again. If you still see the old version, confirm the file is Published in Sokket (not Draft) and that Publish changes completed if you edited an already-published file. New instructions or knowledge won’t appear in tools until they’re published - and as above, you may need to reset/reload MCP in your assistant for new content to show up.
Q: Why is Publish disabled for my instruction?
Section titled “Q: Why is Publish disabled for my instruction?”A: All instructions need a Description (in the Properties panel), every $argument needs to be configured in the editor (type $ + name + Enter, then set description and required in the popover), and every @reference must point to an existing, published knowledge file. Fix any missing or broken references to enable publishing. For knowledge files, a Description is required.
Q: Can I recover a deleted file?
Section titled “Q: Can I recover a deleted file?”A: No. Deleted files cannot be recovered. Export or copy content elsewhere before deleting if you might need it later.
Q: Can I rename the Sokket MCP server in my assistant?
Section titled “Q: Can I rename the Sokket MCP server in my assistant?”A: Yes. You can customise the library name that appears in your assistant’s interface. Edit your MCP configuration and change the key from "sokket" to any name you prefer (e.g. "skt"). The name only affects how it appears in your assistant; it doesn’t change the connection to Sokket.
E.g. in Cursor:
{ "mcpServers": { "skt": { "url": "https://mcp.sokket.ai/your-org-name" } }}Q: Why can’t I assign an editor seat?
Section titled “Q: Why can’t I assign an editor seat?”A: The organisation has no available paid seats. Increase your subscription in Polar (Settings > Billing > Manage Billing) to add seats; then assign them in Settings > Team. Only users with organisation owner seats can manage billing and team. An editor seat can be assigned only if there’s an unassigned paid seat. Seats are claimed automatically when the new member signs in. You can add unlimited read-only seats for free.
Q: How do I get support?
Section titled “Q: How do I get support?”A: Contact support at contact@sokket.ai.
Q: Is my data private? Is it encrypted? Is it used to train models?
Section titled “Q: Is my data private? Is it encrypted? Is it used to train models?”A: Yes. Organisation data is private to the organisation and isolated from other organisations. Data is encrypted in transit (TLS) and at rest. Sokket does not use your content to train models. Access is scoped by role (owner, editor, read-only). Sokket staff do not access customer content unless explicitly required for support.
Q: What data leaves my AI coding assistant, and what do you log?
Section titled “Q: What data leaves my AI coding assistant, and what do you log?”A: When your tool requests context (e.g. an instruction or referenced knowledge), the request and response are sent to Sokket’s MCP endpoint. MCP request/response content is not stored as part of model usage; the endpoint serves and returns what’s stored in your organisation. Model outputs from your assistant are not accessed or stored.
Logging: Only minimal operational metadata (e.g. timing, errors) is logged to operate the service. Prompts and knowledge are stored so they can be served on demand.
Q: Does Sokket have audit logs?
Section titled “Q: Does Sokket have audit logs?”A: Not yet. Today you can control access via roles (owner, editor, read-only) and publish gating. Audit logs are planned.
Q: Can I export my libraries?
Section titled “Q: Can I export my libraries?”A: Not right now. Content stays accessible in the Sokket web app. Contact support at contact@sokket.ai if you need to export data.
Q: Is there a size limit for knowledge or instruction files?
Section titled “Q: Is there a size limit for knowledge or instruction files?”A: Large content is supported however very large files can affect performance - keep files focused and split very large content into multiple knowledge files if needed.