Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@@nestr/mcp List my current projects and their status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP (Model Context Protocol) server for Nestr - connect AI assistants like Claude to your workspace.
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
Related MCP server: Caipher MCP
Visit mcp.nestr.io for the easiest setup with step-by-step instructions for Claude Desktop, Claude Code, and Cursor.
Go to Settings → Connectors → Add custom connector
Set Name to Nestr and Remote MCP URL to https://mcp.nestr.io/mcp
Click "Add" then "Authenticate" to log in with Nestr
claude mcp add nestr --transport http https://mcp.nestr.io/mcpThen run /mcp in Claude Code and click "Authenticate" to log in.
If you prefer to run the MCP server locally:
npx @nestr/mcpConfigure 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:
Go to your Nestr workspace
Click Settings → Integrations → Workspace API access → Configure
Click "New API key" and copy 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?"
Tool | Description |
| List accessible workspaces |
| Get workspace details |
| Create a new workspace (OAuth only) |
| Search for nests (tasks, projects, roles) |
| Get current user identity and workspace list |
Tool | Description |
| Get details of a specific nest (supports batch fetch with comma-separated IDs; single-nest |
| Diagnose one nest: field/property provenance (which label/circle defines each), the caller's composed rights with a deny trace, and (with |
| Get child nests |
| Create a new nest |
| Update nest properties |
| Delete a nest |
| Reorder a nest relative to another |
| Bulk reorder multiple nests |
| Add a label to a nest |
| Remove a label from a nest |
Tool | Description |
| Set or remove a task, project or meeting's recurrence rule |
| List a series' occurrences, virtual and materialized, each with the |
| Skip one occurrence without ending the series, or with |
| Edit one occurrence, materializing it first if it is still virtual |
| Delete a whole series, past occurrences included |
Tool | Description |
| Add a comment to a nest |
| Get comments/discussion on a nest |
| Update a comment |
| Delete a comment |
Tool | Description |
| List organizational circles |
| Get circle details |
| Get roles in a circle with accountabilities and domains |
| List all roles |
| List workspace members |
| Get user details |
| Add a user to the workspace and email them an invite (API provisioning needs a verified domain; the in-app invite does not) |
Tool | Description |
| Create a tension on a circle or role |
| Get tension details |
| List tensions on a circle or role |
| Update a tension |
| Delete a tension |
| Get proposal parts of a tension |
| Add a proposal part (new/changed governance item) |
| Modify a proposal part |
| Remove a proposal part |
| Get children (accountabilities/domains) of a proposal part |
| Add a child to a proposal part |
| Update a proposal part child |
| Delete a proposal part child |
| Preview the diff a proposal part would apply |
| Get voting status for a tension |
| Submit for voting or retract to draft |
Tool | Description |
| Get nests linked via a named relation (e.g., meeting agenda items) |
| Create a bidirectional link between two nests |
| Remove a link between two nests |
Tool | Description |
| List workspace labels |
| Get label details |
| List projects with status |
Tool | Description |
| Get workspace metrics |
| Get historical trend data for a metric |
| List enabled apps/features |
Tool | Description |
| Get current user identity and workspaces |
| List items in user's inbox |
| Quick capture to inbox |
| Get inbox item details |
| Update inbox item |
| Reorder inbox items |
| List user's personal labels |
| Create a personal label |
| Get items marked for today |
| Add items to today's focus |
| Remove items from today's focus |
| List tensions authored by or assigned to you |
| List governance proposals needing your vote |
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.
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.
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 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.
Variable | Description |
| Nestr API key (full workspace access) |
| OAuth token (respects user permissions) |
* Either NESTR_API_KEY or NESTR_OAUTH_TOKEN is required for local usage.
Variable | Description | Default |
| API base URL |
|
These are used when running the HTTP server for hosted deployments:
Variable | Description | Default |
| HTTP server port |
|
| OAuth client ID for hosted OAuth flow | - |
| OAuth client secret | - |
| 32-byte base64 key for encrypting OAuth sessions at rest | - |
| Google Tag Manager container ID for landing page | - |
Server-side analytics options:
GA4 Measurement Protocol:
Variable | Description |
| GA4 Measurement ID (e.g., |
| Measurement Protocol API secret |
| Set to |
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):
Variable | Description |
| MCPcat project ID (from mcpcat.io) |
| Enable session replay (default: |
# 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 inspectSECURITY.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
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
Setup Guide - Step-by-step setup instructions
MIT - see LICENSE
This server cannot be deployed
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Hosted MCP server connecting AI assistants to 9,000+ apps and 40,000+ actions via Zapier.
AI-native Kanban board — connect Claude to claim, work and move your tasks over MCP.
