Nolt

io.noltPublished by nolt.ioOfficial publisherv2.0.0Updated Oct 27, 2026

A collaborative place for user requests: collect feedback, plan work, keep users in the loop.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote Nolt MCP server that lets an assistant work with a collaborative user-feedback board: collecting requests, planning work and keeping users informed.

What you can do
  • Work with user feedback and feature requests on a Nolt board
  • Plan and organize the work that comes out of that feedback
  • Keep users in the loop on what is being built
  • No individual tools are listed in the manifest, so the exact actions available are not documented here.
When to use it
Useful when a team runs its product feedback and roadmap on Nolt and wants an assistant to help triage requests, plan work or communicate progress without switching tools.
Requirements
A remote MCP endpoint at nolt.io, reachable over the network. OAuth authentication is required, so the user needs a Nolt account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
The server requires OAuth access to a Nolt workspace, so the assistant may be able to read and change feedback, plans and user-facing updates. Review the scopes granted during sign-in and confirm whether write actions are included before connecting it to a live board.

Installation

In SourceWeft

  1. Open Nolt in the dashboard and add it to a workspace.
  2. Connect the required 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.nolt%2Fnolt/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "nolt": {
      "type": "http",
      "url": "https://nolt.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.