Connect tools

Connect your MCP-compatible tools to Sokket to give your team access to all Published context through the Model Context Protocol (MCP). The Sokket MCP-server provides a zero-config endpoint for your organisation.

Sokket’s MCP endpoint

MCP is an open standard that allows MCP-compatible tools to securely fetch context from a server. Your Sokket MCP Endpoint is the unique and secure URL that acts as this hosted MCP server. When you paste this URL into an MCP-compatible tool, it allows that tool to access all Published context from your organisation after you authorise it. You can find your unique URL by selecting the Connect button in the Sokket dashboard.

Connect your tool

Cursor

1. Log in to your Sokket dashboard
2. Select Connect in the header
3. Select Cursor
4. Copy your organisation’s MCP endpoint URL
5. In Cursor, open Settings and go to Tools & MCP
6. Click Add new custom MCP server. This will automatically open your settings.json file
7. Paste in the configuration below and save the file

{
  "mcpServers": {
    "sokket": {
      "url": "https://mcp.sokket.ai/your-org-name"
    }
  }
}

8. Approve the browser authentication prompt
9. Open Cursor and run /sokket in the agent chat to view available libraries

Claude

1. Log in to your Sokket dashboard
2. Select Connect in the header
3. Select Claude
4. Copy your organisation’s MCP endpoint URL
5. Open your terminal or command prompt
6. Run: claude mcp add https://mcp.sokket.ai/your-org-name
7. Follow the authentication prompts in Claude Code
8. Open Claude and access your libraries to view available /instructions

Gemini (coming soon)

Antigravity (coming soon)

Rename your Sokket MCP server

You can customise the library name that appears in your tool’s interface. Edit your MCP configuration and change the library name from "sokket" to any name you prefer (e.g., "skt"). E.g. In Cusor:

{
  "mcpServers": {
    "skt": {
      "url": "https://mcp.sokket.ai/mcp"
    }
  }
}

The library name only affects how it appears in your tool. It doesn’t change the connection or available /instructions and @knowledge.

Troubleshooting

Don’t see your new /instruction? Make sure you selected Publish in the Sokket web app. Drafts are not sent to your tool.

Next Steps

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