Nestr

@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

Tensions

Graph Links

Labels & Projects

Insights & Apps

Personal (OAuth only)

MCP Apps (Interactive UI)

MCP Apps are interactive UI components that can be embedded in MCP clients that support them (like Claude.ai). They provide rich, visual interfaces for working with Nestr data.

Completable List

Resource URI: ui://nestr/completable-list

An interactive list for viewing and completing tasks and projects.

Features:

• Projects show a box icon, todos show a checkbox
• Check items to mark them complete (strikethrough)
• Inline editing of titles (auto-saves)
• Drag-and-drop reordering
• Shows parent path for context
• Quick link to open item in Nestr

Usage: When an AI assistant returns task or project results, supporting clients can render this interactive UI instead of plain text, allowing you to complete items, edit titles, and reorder directly in the chat.

Authentication

OAuth (Recommended)

The hosted service at mcp.nestr.io handles OAuth automatically. Just add the server and authenticate through your browser.

OAuth respects user-specific permissions - the AI assistant can only access what the authenticated user can access.

API Key

API keys provide full workspace access and work with the local npm package. See Quick Start above.

Note: API keys have full workspace access regardless of user permissions.

Environment Variables

Authentication (Required)

* Either NESTR_API_KEY or NESTR_OAUTH_TOKEN is required for local usage.

Configuration (Optional)

Hosting/Server (HTTP transport only)

These are used when running the HTTP server for hosted deployments:

Analytics (Optional)

Server-side analytics options:

GA4 Measurement Protocol:

Note: Both GA4_MEASUREMENT_ID and GA4_API_SECRET are required for GA4 tracking. If only the measurement ID is set, a warning is logged and tracking is disabled.

MCPcat (MCP-specific analytics):

Development

# Clone the repositorygit clone https://github.com/nestr-dev/nestr-mcp.gitcd nestr-mcp
# Install dependenciesnpm install
# Set your API keyexport NESTR_API_KEY=your-api-key
# Run in development mode (stdio)npm run dev
# Run HTTP server for local testingnpm run dev:http
# Build for productionnpm run build
# Test with MCP Inspectornpm run inspect

Security

SECURITY.md is the full policy: how to report a vulnerability, what the three authorisation surfaces reach, and what this server does and does not store. The essentials:

• Never commit your API key or OAuth token to version control
• OAuth tokens respect user permissions and are recommended
• API keys provide full workspace access - use OAuth for granular permissions
• Use /mcp/readonly for any integration that only needs to read

Credential lifetime and rotation

OAuth tokens expire and are refreshed for you. The server holds the refresh token with the session and renews the access token as it nears expiry, so a long-lived client keeps working without re-authorising. Revoke a session from Nestr and the next refresh fails - access stops there. Nothing to rotate by hand.

API keys do not expire. A workspace API key stays valid until a workspace admin revokes it in Nestr under Settings > Integrations > Workspace API access. That makes rotation your job rather than the server's:

• Rotate when anyone with access to a key leaves, and on a schedule you set
• Revoke dormant keys rather than leaving them in place - an unused key is still a live workspace-wide credential
• Rotate immediately if a key may have been exposed
• Issue a read-only key, and point it at /mcp/readonly, whenever the integration only reads

Resources

• Setup Guide - Step-by-step setup instructions
• Nestr Help Center
• Nestr API Documentation
• Model Context Protocol

License

MIT - see LICENSE

Support

• GitHub Issues
• Nestr Support