Other MCP Clients

SHARC works with any MCP-compatible client. For agentic CLIs and TUIs (Claude Code, Codex, Droid, OpenCode), see their dedicated setup pages — they have one-command installers. The clients below are typically configured by editing a JSON file.

Cursor

Add to your Cursor MCP config (~/.cursor/mcp.json for global, or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "sharc": {
      "command": "npx",
      "args": ["-y", "@sharc-code/mcp@latest"],
      "env": {
        "SHARC_API_KEY": "sk_mcp_..."
      }
    }
  }
}

VS Code (Cline)

Add to your VS Code settings (settings.json):

{
  "cline.mcpServers": {
    "sharc": {
      "command": "npx",
      "args": ["-y", "@sharc-code/mcp@latest"],
      "env": {
        "SHARC_API_KEY": "sk_mcp_..."
      }
    }
  }
}

Windsurf

Add to your Windsurf MCP config:

{
  "mcpServers": {
    "sharc": {
      "command": "npx",
      "args": ["-y", "@sharc-code/mcp@latest"],
      "env": {
        "SHARC_API_KEY": "sk_mcp_..."
      }
    }
  }
}

Claude Desktop

Add to Claude Desktop’s MCP config:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "sharc": {
      "command": "npx",
      "args": ["-y", "@sharc-code/mcp@latest"],
      "env": {
        "SHARC_API_KEY": "sk_mcp_..."
      }
    }
  }
}

Zed

Add to your Zed settings (~/.config/zed/settings.json):

{
  "context_servers": {
    "sharc": {
      "command": {
        "path": "npx",
        "args": ["-y", "@sharc-code/mcp@latest"],
        "env": {
          "SHARC_API_KEY": "sk_mcp_..."
        }
      }
    }
  }
}

Void

{
  "mcp": {
    "sharc": {
      "command": "npx",
      "args": ["-y", "@sharc-code/mcp@latest"],
      "env": {
        "SHARC_API_KEY": "sk_mcp_..."
      }
    }
  }
}

Roo Code

{
  "mcpServers": {
    "sharc": {
      "command": "npx",
      "args": ["-y", "@sharc-code/mcp@latest"],
      "env": {
        "SHARC_API_KEY": "sk_mcp_..."
      }
    }
  }
}

Generic stdio MCP configuration

For any MCP-compatible client that accepts stdio servers, the shape is the same:

{
  "mcpServers": {
    "sharc": {
      "command": "npx",
      "args": ["-y", "@sharc-code/mcp@latest"],
      "env": {
        "SHARC_API_KEY": "sk_mcp_..."
      }
    }
  }
}

Troubleshooting

Tools don’t appear

Restart the client after editing config — most clients only load MCP servers at startup.
Confirm the JSON is valid (no trailing commas, balanced braces).
Check that SHARC_API_KEY is on the SHARC server entry.

`npx` not found on Windows

If a client can’t find npx, point at the full path:

{
  "command": "C:/Program Files/nodejs/npx.cmd",
  "args": ["-y", "@sharc-code/mcp@latest"]
}

Getting started

MCP reference

Packages

Architecture

Other MCP Clients

Cursor

VS Code (Cline)

Windsurf

Claude Desktop

Zed

Void

Roo Code

Generic stdio MCP configuration

Troubleshooting

Tools don’t appear

`npx` not found on Windows

​Cursor

​VS Code (Cline)

​Windsurf

​Claude Desktop

​Zed

​Void

​Roo Code

​Generic stdio MCP configuration

​Troubleshooting

​Tools don’t appear

​npx not found on Windows

Cursor

VS Code (Cline)

Windsurf

Claude Desktop

Zed

Void

Roo Code

Generic stdio MCP configuration

Troubleshooting

Tools don’t appear

`npx` not found on Windows