Packages MCP Latest 2026-10-18

`niiko-mcp-server`

The remote MCP server. Connect Claude or any OAuth-capable client and every action and read you grant becomes a tool, the reads marked read-only.

Last updatedOct 18, 2026

Runtime: Any MCP client with OAuth
License: MIT
Source: vorluno/niiko-mcp-server
Registry: niiko.org/api/mcp

Install

claude mcp add --transport http niiko https://niiko.org/api/mcp

Use

Add it to Claude (or any MCP client that speaks OAuth): it registers itself, sends you to niiko's consent screen, and every action and read you grant appears as a tool with the same purpose text the SDKs carry — the reads marked read-only.

claude mcp add --transport http niiko https://niiko.org/api/mcp

claude mcp add --transport http niiko https://niiko.org/api/mcp
# or: Settings → Connectors → Add custom connector → https://niiko.org/api/mcp

Two permissions, not one

Both are needed: a key with that scope, and the workspace owner having switched the permission on. Holding the key is not enough — they are two decisions made by different people.

What it does not do

Run locally — the token is validated by niiko's identity system.
Resources or prompts — only tools; the person's screen is the resource.
API keys — the MCP server authenticates people, through OAuth.

Versions

The MCP server is not published to a registry: each entry below is a plan that changed its tools.