Stuga

Name: Stuga
Author: stuga-dev

by stuga-devversion 0.2.1i★ –iComputer or cloud

Registry namedev.stuga/stuga

Install

Overview

Description from the maker (original English)

Your AI writes your self-hosted team wiki and answers from it. Its edits await approval by default.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Other
You need to fill in: STUGA_URL

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: STUGA_URL

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://{stuga_host}/mcp

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "stuga": {
      "command": "npx",
      "args": [
        "-y",
        "@stuga/mcp"
      ],
      "env": {
        "STUGA_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http stuga 'https://{stuga_host}/mcp'

Or run it on your computer

claude mcp add stuga --env STUGA_URL=your-value -- npx -y @stuga/mcp

Fill in the empty values before running it.

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "stuga": {
      "url": "https://{stuga_host}/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "stuga": {
      "command": "npx",
      "args": [
        "-y",
        "@stuga/mcp"
      ],
      "env": {
        "STUGA_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "stuga": {
      "type": "http",
      "url": "https://{stuga_host}/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "stuga": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@stuga/mcp"
      ],
      "env": {
        "STUGA_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://{stuga_host}/mcp

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

STUGA_URL required env
The address you open Stuga at.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain stuga.dev (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
The address needs your own account values, so we cannot check it for you
– Not applicable
Sign-in with OAuth
The address needs your own account values, so we cannot check it for you
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32394 servers in this category
Published to the registry more recently than 73% of the other 32394 servers in this category
Basic checks equal to or better than 100% of the other 32394 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Stuga safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: STUGA_URL

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 14 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Hive Intelligence MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Hive Intelligence MCP

by hive-intel

Evidence-backed crypto due diligence with sources, freshness, and a runtime receipt on every call.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Stuga

Your AI writes the team wiki. A colleague approves.

A team wiki of pages and tables, on a Mac or server you run. Say Save to Stuga to Claude, Codex or any MCP client, and it files each point on the right page or in the right table row. By default a change to the wiki waits for whoever asked the AI; set a folder to Reviewed by a colleague and someone else approves it. Ask Stuga answers from what is approved, and says what still waits.

Download for Mac (Apple silicon, macOS 15+) · Install with Docker

Install, then create your account and workspace and connect your AI. Help for people using Stuga: stuga.dev/docs.

How the wiki stays right

Save to Stuga. Your AI finds the page and section a point belongs in, or the row a fact fills, and corrects the sentence it changes rather than adding another. It cites the meeting or email a point came from, and tells you what it saved where and what waits. A point no page is about starts a page in the folder it belongs in, or goes in your own My notes.
Three review levels. In Who reviews AI edits…, a folder, page or database is Reviewed by whoever asked the AI (the default), Reviewed by a colleague (someone else who can edit it, from the folder's approver group if it names one, never the person who asked), or AI edits apply directly (recorded, attributed and revertible). People's own edits go straight in.
One card per change. Filing a meeting across several pages is one change, reviewed on one card laid out for a phone: each edit in its paragraph, with the sources it cites. Approve all, Ask for changes… or Decline… with a note the AI reads. A folder can post each change that waits for a colleague to a Slack channel.
Ask Stuga. Your AI answers from the pages and tables, with who last changed each one and when, and what waits: "the page says 14 days; a change to 30 days waits for a colleague".
Check Stuga. Linked from under each page, Needs checking when a page it cites changes, and Wiki → Index and Wiki → Log. Say Check Stuga and your AI finds stale pages, orphans and broken links, and proposes the fixes as one change.
Instructions that stack. The workspace, folders, pages and databases can each tell agents what goes where. They advise the model; permissions and review decide what a write does.

What's in it

Pages written together. Real-time editing (Tiptap over a Yjs CRDT) with presence, comments, @mentions and version history.
Tables beside the pages. Typed tables, each database its own SQLite file, with saved views, row pages and CSV import. Agents, Ask and the REST API run read-only SQL on them.
Search that follows permissions. Keyword (BM25 over Postgres full-text search) and semantic (pgvector) search in one SQL statement, with access checked inside it. Chinese, Japanese, Korean and Thai work without setup.
Built-in AI, off until set up. A co-author and a table assistant, whose edits are reviewed like an agent's, and Ask, which cites sources. OpenAI, Anthropic, Gemini, DeepSeek and more, or Ollama.
Sharing and sign-in. Workspaces, folders, per-page sharing, groups and guests. People join by invite link and sign in with a password or your OpenID Connect provider.
Import and export. A Notion export, or a zipped Obsidian vault or folder of Markdown, becomes a workspace; a workspace exports as one .stuga.zip of Markdown, JSON Lines and its files.

Connect your AI

Agents connect over MCP. Settings → Your AI agents gives the setup for Claude Code, Claude Desktop, Codex, Antigravity, Cursor, VS Code, Kiro, Goose, LM Studio, DeepSeek Harness and Pi, with your node's address filled in, and the URL any other MCP client needs (docs/agents.md). Each agent brings its own model, so the node needs no AI key.

Scoped sign-in. Most clients sign in through the browser, where you tick the workspaces an app may use and choose Read only or Read and suggest changes. Revoke ends its access.
Narrow keys. A client without sign-in uses an API key, which can be confined to folders, made read-only or given an expiry.
Content only. Agents change documents and databases. Renaming, moving, deleting, sharing and the review setting stay with people.
Full audit. Every MCP call, reads included, is in the workspace's audit log. An event feed and signed webhooks report what changed.

Your data

Stuga sends no telemetry, and nothing reaches us unless a node admin turns on remote access. The node makes outbound requests only for features in use, such as an AI provider, and asks GitHub once a day for the list of releases unless a node admin turns that off. docs/privacy.md lists what the node sends and stores.

Install

A Mac with Apple silicon, on macOS 15 or later: open the package, or Stuga- .pkg from the latest release. It carries its own Postgres and Node.js (docs/install/macos.md).
Docker on x86-64 or arm64, such as a Linux server or a NAS: install.sh starts Postgres and the node with Compose (docs/install/docker.md):

  curl -fsSL https://github.com/stuga-dev/stuga/releases/latest/download/install.sh | bash

A node is one Node.js process and Postgres with pgvector; people open it in a browser. It backs itself up every day by default and before every upgrade (docs/operations.md). docs/getting-started.md walks through the first hour.

Questions and feedback

Ask a question or share an idea in Discussions; report a bug as an issue.

Contributing

Issues and pull requests are welcome. CONTRIBUTING.md covers running Stuga from source, the tests and the conventions, and RELEASING.md how a release is cut. Contributions are accepted under a Contributor License Agreement (CLA.md); a bot asks on your first pull request. Report a vulnerability privately, as SECURITY.md describes.

License

AGPL-3.0-only, except integrations/, which is MIT; copyright notice in NOTICE. If you modify Stuga and offer it to others over a network, you share your changes under the same terms. The name and logo are not covered by the license: TRADEMARKS.md says how you may use them.

Stuga

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Hive Intelligence MCP

README from the maker

Stuga

How the wiki stays right

What's in it

Connect your AI

Your data

Install

Questions and feedback

Contributing

License