# go-tokenless MCP server

> Migrates npm publishing in GitHub Actions from long-lived tokens to OIDC-based trusted publishing.

- Repository: https://github.com/Continuous-Actions/go-tokenless
- Page: https://hostedmcp.org/servers/continuous-actions/go-tokenless
- Transport: stdio
- Stars: 2
- License: MIT
- Latest version: 1.1.0

## Install

### Claude Code

```sh
claude mcp add go-tokenless -- npx -y go-tokenless
```

### Cursor (`~/.cursor/mcp.json`)

```json
{
  "mcpServers": {
    "go-tokenless": {
      "command": "npx",
      "args": [
        "-y",
        "go-tokenless"
      ]
    }
  }
}
```

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "go-tokenless": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "go-tokenless"
      ]
    }
  }
}
```

### VS Code CLI

```sh
code --add-mcp '{"name":"go-tokenless","type":"stdio","command":"npx","args":["-y","go-tokenless"]}'
```

### Claude Desktop (`claude_desktop_config.json`)

```json
{
  "mcpServers": {
    "go-tokenless": {
      "command": "npx",
      "args": [
        "-y",
        "go-tokenless"
      ]
    }
  }
}
```

### Codex

```sh
codex mcp add go-tokenless -- npx -y go-tokenless
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.go-tokenless]
command = "npx"
args = ["-y", "go-tokenless"]
```

### Gemini CLI

```sh
gemini mcp add -s user go-tokenless npx -- -y go-tokenless
```

### Gemini settings.json (`~/.gemini/settings.json`)

```json
{
  "mcpServers": {
    "go-tokenless": {
      "command": "npx",
      "args": [
        "-y",
        "go-tokenless"
      ]
    }
  }
}
```

## FAQ

### What does go-tokenless change in my workflow?

It removes NODE_AUTH_TOKEN or NPM_TOKEN from publish jobs, adds id-token: write permissions, ensures npm version compatibility, and updates package.json repository fields.

### Can I use it with private packages?

Yes, you can provide a read-only token for installation steps while keeping the publishing steps tokenless.

### What happens if I have a publish job triggered by pull_request_target?

The tool will stop and refuse to make changes because granting OIDC to such triggers could allow a fork to publish to your registry.
