Nitrozen

io.nitrozenPublished by nitrozen.ioOfficial publisherv1.0.0Updated Oct 30, 2026

Manage Nitrozen.io changelog projects, entries and API tokens from any MCP client.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Hosted Nitrozen.io MCP server that lets an assistant create changelog projects, write and publish entries, and manage API tokens.

What you can do
  • Read account details: authenticated user profile, plan and usage statistics with plan limits
  • Manage projects: list, create, get, update and delete changelog projects, including their public URLs
  • Manage entries: list, create, get, update and delete changelog entries per project
  • Manage API tokens: list, create and revoke tokens
  • Read published entries by project slug without authentication
When to use it
Useful when you keep a public changelog on Nitrozen.io and want an assistant to draft, publish or edit release notes and manage projects directly from chat, or to check plan usage and token inventory.
Requirements
A remote Streamable HTTP endpoint; nothing to install. Authentication is required: Claude.ai clients sign in via OAuth 2.0, while other clients send an API token in the Authorization header as a bearer token, created on the Nitrozen API Tokens page. Network access to the hosted endpoint is needed.
Before you install
The server can create, update and delete projects and entries, and can create or revoke API tokens, so changes are live on your changelog. The API token is a credential passed in the Authorization header; store it carefully and prefer a read-scope token when write access is not needed. Deleting a project or entry and revoking a token are destructive actions.

Installation

In SourceWeft

  1. Open Nitrozen in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.nitrozen%2Fnitrozen/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "nitrozen": {
      "type": "http",
      "url": "https://mcp.nitrozen.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

[Nitrozen logo]

Nitrozen MCP Server

Official remote Model Context Protocol server for Nitrozen.io, the hosted changelog platform. Let your AI assistant create projects, write and publish changelog entries, and read your public changelog.

Nothing to install: it is a hosted server. This repository holds the Worker source.

Tools

ToolDescription
get_userGet authenticated user profile and plan
get_usageGet usage statistics and plan limits
list_projectsList all changelog projects (each includes public_url)
create_projectCreate a new project
get_projectGet a project by ID, including its public_url
update_projectUpdate project name/description
delete_projectDelete a project
list_entriesList entries for a project (paginated)
create_entryCreate a changelog entry
get_entryGet an entry by ID
update_entryUpdate an entry
delete_entryDelete an entry
list_tokensList API tokens
create_tokenCreate a new API token
revoke_tokenRevoke an API token
get_public_entriesList published entries by project slug (no auth)

Authentication

  • Claude.ai uses OAuth 2.0: add the server URL and authorize in the browser. No token needed.
  • All other clients send an API token in a header: Authorization: Bearer <your-api-token>. Create a token on the API Tokens page (choose the read scope for read-only access).

Requests without a valid token get 401 with a WWW-Authenticate header pointing to https://mcp.nitrozen.io/.well-known/oauth-protected-resource.

Connect your client

Claude.ai

Settings → Connectors (Integrations) → Add custom connector → https://mcp.nitrozen.io/mcp, then sign in to Nitrozen and approve.

Claude Code

bash
claude mcp add --transport http nitrozen https://mcp.nitrozen.io/mcp \  --header "Authorization: Bearer <your-api-token>"

Cursor (~/.cursor/mcp.json) / Windsurf / other JSON configs

json
{  "mcpServers": {    "nitrozen": {      "url": "https://mcp.nitrozen.io/mcp",      "headers": { "Authorization": "Bearer <your-api-token>" }    }  }}

Cline (cline_mcp_settings.json)

json
{  "mcpServers": {    "nitrozen": {      "type": "streamableHttp",      "url": "https://mcp.nitrozen.io/mcp",      "headers": { "Authorization": "Bearer <your-api-token>" },      "disabled": false    }  }}

VS Code (.vscode/mcp.json)

json
{  "servers": {    "nitrozen": {      "type": "http",      "url": "https://mcp.nitrozen.io/mcp",      "headers": { "Authorization": "Bearer <your-api-token>" }    }  }}

Docker (stdio bridge)

For stdio-only clients, the included Dockerfile bridges to the hosted server with mcp-remote:

bash
docker build -t nitrozen-mcp .docker run -i --rm -e NITROZEN_API_TOKEN=<your-api-token> nitrozen-mcp

Development

bash
npm installnpm run dev      # local Workernpm run deploy   # deploy to Cloudflare

License

See LICENSE.

Source: README.md at commit 7a9d450

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 30, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts