MCP Hub
Back to servers

mcp

Connect AI assistants to Nestr to manage tasks, projects, and organizational structures like circles and roles for self-organizing teams.

Tools
26
Updated
Jan 21, 2026

Quick Install

npx -y @nestr/mcp

@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 SettingsIntegrationsWorkspace API accessConfigure
  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

ToolDescription
nestr_list_workspacesList accessible workspaces
nestr_get_workspaceGet workspace details
nestr_searchSearch for nests (tasks, projects, roles)
nestr_get_nestGet details of a specific nest
nestr_get_nest_childrenGet child nests
nestr_create_nestCreate a new nest
nestr_update_nestUpdate nest properties
nestr_delete_nestDelete a nest
nestr_add_commentAdd a comment to a nest
nestr_get_commentsGet comments/discussion on a nest
nestr_list_circlesList organizational circles
nestr_get_circleGet circle details
nestr_get_circle_rolesGet roles in a circle
nestr_list_rolesList all roles
nestr_list_usersList workspace members
nestr_get_userGet user details
nestr_list_labelsList available labels
nestr_get_labelGet label details
nestr_get_projectsList projects with status
nestr_get_insightsGet workspace metrics
nestr_get_insight_historyGet historical trend data for a metric
nestr_get_workspace_appsList enabled apps/features
nestr_list_inboxList items in user's inbox (OAuth only)
nestr_create_inbox_itemQuick capture to inbox (OAuth only)
nestr_get_inbox_itemGet inbox item details (OAuth only)
nestr_update_inbox_itemUpdate inbox item (OAuth only)

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

VariableDescriptionRequired
NESTR_API_KEYNestr API key (full workspace access)Yes*
NESTR_OAUTH_TOKENOAuth token (respects user permissions)Yes*
NESTR_API_BASEAPI base URL (default: https://app.nestr.io/api)No

* Either NESTR_API_KEY or NESTR_OAUTH_TOKEN is required for local usage.

Development

# Clone the repository
git clone https://github.com/nestr-dev/nestr-mcp.git
cd nestr-mcp

# Install dependencies
npm install

# Set your API key
export NESTR_API_KEY=your-api-key

# Run in development mode (stdio)
npm run dev

# Run HTTP server for local testing
npm run dev:http

# Build for production
npm run build

# Test with MCP Inspector
npm run inspect

Security

  • 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
  • Rotate credentials if you suspect they've been compromised

Resources

License

MIT - see LICENSE

Support

Reviews

No reviews yet

Sign in to write a review