MCP.Market

Nestr MCP server

online · 100% uptime
by nestr.io·io.nestr/mcp·v0.2.7·5 stars

Connect AI to Nestr for Holacracy, Sociocracy, and self-organizing teams.

A98/100grade A
What users say
No reviews yet
Be the first
Safety scan
A98/100

not scanned yet

Adoption
Growing

5 stars291 downloads/wk

Reviews

Write one

Nobody has reviewed Nestr yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Nestr tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Nestr compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
98/100
higher than 99% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
84 ms
faster than 87% of 30,031 servers
GitHub stars
5
more than 83% of 28,688 servers
Downloads a week
291
more than 81% of 12,191 servers with a package

Release history: 9 versions in the registry since 2026-09-11, latest 2026-11-03, typically one every 6 days.

Install Nestr in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://mcp.nestr.io/mcp
Add to Cursor

What the publisher says

From the Nestr repository's README, as published. We do not edit it. Read it on GitHub

@nestr/mcp

MCP (Model Context Protocol) server for Nestr - connect AI assistants like Claude to your workspace.

What is this?

This MCP server allows AI assistants to interact with your Nestr workspace:

  • Search for tasks, projects, and roles
  • Create and update nests
  • View organizational structure (circles, roles, accountabilities)
  • Get workspace insights and metrics
  • Add comments and collaborate

Quick Start

Visit mcp.nestr.io for the easiest setup with step-by-step instructions for Claude Desktop, Claude Code, and Cursor.

Claude Desktop

  1. Go to Settings → Connectors → Add custom connector
  2. Set Name to Nestr and Remote MCP URL to https://mcp.nestr.io/mcp
  3. Click "Add" then "Authenticate" to log in with Nestr

Claude Code

claude mcp add nestr --transport http https://mcp.nestr.io/mcp

Then run /mcp in Claude Code and click "Authenticate" to log in.

Using the npm Package (Local)

If you prefer to run the MCP server locally:

npx @nestr/mcp

Configure your AI client with:

{
  "mcpServers": {
    "nestr": {
      "command": "npx",
      "args": ["-y", "@nestr/mcp"],
      "env": {
        "NESTR_API_KEY": "your-api-key-here"
      }
    }
  }
}

To get an API key:

  1. Go to your Nestr workspace
  2. Click Settings → Integrations → Workspace API access → Configure
  3. Click "New API key" and copy it

Start Using It

Ask your AI assistant things like:

  • "What workspaces do I have access to?"
  • "Search for tasks related to marketing"
  • "Create a new project called 'Q1 Planning'"
  • "What are my current projects and their status?"
  • "Who is responsible for customer support?"

Available Tools

Workspace & Search

Nests (Tasks, Projects, Roles)

Recurrence

Comments & Discussion

Organization Structure

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Nestr: common questions

Is Nestr MCP server safe?
Yes, by our scan: it is graded A (98/100). Read the Nestr safety report
How do I install Nestr?
It runs remotely at mcp.nestr.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Nestr need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Nestr maintained?
The last commit was 25 days ago (2026-10-10). The latest release is v0.2.7.
Is Nestr up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Nestr compare with other MCP servers?
safety score 98/100 (higher than 99% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 84 ms (faster than 87% of 30,031 servers). Full comparison.