NiftyPM MCP Server
Click on "Install 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., "@NiftyPM MCP ServerShow tasks in project 'Website Redesign'."
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.
NiftyPM MCP Server
A Model Context Protocol (MCP) server that exposes the NiftyPM project management API as a set of tools for AI assistants (Claude, Cursor, etc.). The server can run locally over stdio for desktop MCP clients or be deployed as an HTTP/streamable endpoint on Cloudflare Workers for remote clients.
It ships with 117 tools spanning projects, tasks, documents, webhooks, and all other available NiftyPM API endpoints, all individually toggleable through environment variables so you can expose only what you need.
Table of Contents
Features
Full coverage of NiftyPM objects — 117 tools across 20 domains covering projects, files, documents, labels/tags, milestones, tasks, task groups, messages, subteams, webhooks, and more.
Two deployment targets —
stdiofor local desktop MCP clients and a Cloudflare Workers HTTP transport for remote/hosted use.Granular tool toggles — turn any of the 20 tool domains on or off without recompiling.
OAuth 2.0 bearer auth — the client sends a
Beareraccess token on every request and the access/refresh token pair is read from the environment.Strongly-typed schemas — every tool parameter is validated with Zod before a request is sent.
Edge-ready — the Workers build uses the
nodejs_compatflag so the SDK runs unmodified on the edge runtime.
Architecture
┌────────────────────┐ stdio / HTTP ┌──────────────────────┐ HTTPS ┌────────────────────┐
│ MCP client │ ────────────────────▶ │ niftypm-mcp server │ ────────────▶ │ openapi.niftypm │
│ (Claude, Cursor) │ │ (FastMCP / Workers) │ │ .com │
└────────────────────┘ └──────────────────────┘ └────────────────────┘
│
├─ src/index.ts → FastMCP, stdio + optional httpStream
└─ src/worker.ts → Cloudflare Workers MCP handlerLayer | File | Purpose |
Entry (local) |
| Bootstraps FastMCP, registers tools, picks |
Entry (edge) |
| Exports a Workers-compatible |
Config |
| Loads OAuth credentials and tool toggles from environment variables. |
HTTP client |
| Thin |
Tool modules |
| One file per resource group, each exporting a |
Tool barrel |
| Re-exports all |
Prerequisites
Node.js 20+ (for the built-in
fetchandHeaderstypes used by the client).Bun ≥ 1.1 (recommended for local dev —
bun --watchgives a fast reload loop). npm/pnpm work too.Wrangler CLI (
npm i -g wrangler) for the Cloudflare Workers deployment target.A NiftyPM account with OAuth credentials (client ID/secret) and a valid access/refresh token pair. See the NiftyPM API docs for the OAuth flow used by your workspace.
Installation
# Clone the repository
git clone https://github.com/<your-org>/niftypm-mcp.git
cd niftypm-mcp
# Install dependencies (bun is used in the lockfile, but npm/pnpm work fine)
bun install
# or
npm installConfiguration
All runtime configuration is provided through environment variables.
Copy the example env file:
cp .env.example .envFill in your credentials:
NIFTYPM_CLIENT_ID=your_client_id_here NIFTYPM_CLIENT_SECRET=your_client_secret_here NIFTYPM_ACCESS_TOKEN=your_access_token_here NIFTYPM_REFRESH_TOKEN=your_refresh_token_here(Optional) Disable any tool group you don't want to expose by setting the corresponding
ENABLE_*flag tofalse. See Environment Variables.
The
validateConfigstep insrc/index.tswill throw on startup ifNIFTYPM_ACCESS_TOKENis missing.
Running Locally (stdio)
stdio is the default transport and is what most desktop MCP clients (Claude Desktop, Cursor, etc.) expect.
# Foreground
bun run start
# Watch mode (auto-reload on change)
bun run devTo switch to an HTTP transport locally (useful for testing the streamable endpoint with a remote client), set TRANSPORT=http and optionally PORT:
TRANSPORT=http PORT=8080 bun run start
# → NiftyPM MCP server listening on http://localhost:8080/mcpBuild the TypeScript output to dist/ with bun run build if you need to run the compiled dist/index.js (this is what package.json bin points to).
Running on Cloudflare Workers
The Workers build lives in src/worker.ts and is wired up via wrangler.jsonc.
# Local Workers dev server
bun run cf:dev
# Deploy to your Cloudflare account
bun run cf:deployFor local development, copy the secrets template and fill in your credentials:
cp .dev.vars.example .dev.vars
# then edit .dev.vars — Wrangler reads it automatically for `wrangler dev`For production secrets, use:
wrangler secret put NIFTYPM_ACCESS_TOKEN
wrangler secret put NIFTYPM_REFRESH_TOKEN
wrangler secret put NIFTYPM_CLIENT_ID
wrangler secret put NIFTYPM_CLIENT_SECRETThe default compatibility_flags: ["nodejs_compat"] in wrangler.jsonc is what lets the MCP SDK and fetch shim run on Workers.
MCP Client Setup
Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"niftypm": {
"command": "bun",
"args": ["run", "/absolute/path/to/niftypm-mcp/src/index.ts"],
"env": {
"NIFTYPM_ACCESS_TOKEN": "your_access_token_here",
"NIFTYPM_REFRESH_TOKEN": "your_refresh_token_here"
}
}
}
}OpenCode (opencode.json)
The recommended approach is to use file-based secrets to avoid token truncation issues with long JWTs.
Step 1: Create the secrets directory and store your tokens:
mkdir -p .secrets
echo "your_client_id" > .secrets/client_id
echo "your_client_secret" > .secrets/client_secret
echo "your_access_token" > .secrets/access_token
echo "your_refresh_token" > .secrets/refresh_tokenStep 2: Add to your opencode.json (typically at ~/.config/opencode/opencode.json):
{
"mcp": {
"niftypm": {
"type": "local",
"command": ["bun", "run", "/absolute/path/to/niftypm-mcp/src/index.ts"],
"environment": {
"NIFTYPM_CLIENT_ID": "{file:/absolute/path/to/niftypm-mcp/.secrets/client_id}",
"NIFTYPM_CLIENT_SECRET": "{file:/absolute/path/to/niftypm-mcp/.secrets/client_secret}",
"NIFTYPM_ACCESS_TOKEN": "{file:/absolute/path/to/niftypm-mcp/.secrets/access_token}",
"NIFTYPM_REFRESH_TOKEN": "{file:/absolute/path/to/niftypm-mcp/.secrets/refresh_token}"
},
"enabled": true
}
}
}Why
{file:}instead of inline values? OpenCode uses{file:path}syntax to read secrets from files, avoiding truncation of long JWT tokens that can occur with inline JSON values. The.secrets/directory is in.gitignoreso tokens never commit.
Cursor / Other stdio Clients
Use the same command/args pattern as Claude Desktop. For HTTP clients, point them at the deployed Workers URL (e.g. https://niftypm-mcp.<your-subdomain>.workers.dev).
Available Tools
All tool names are namespaced with the niftypm_ prefix. Return values are JSON strings formatted with two-space indentation for readability.
Files (ENABLE_FILES, default on)
Tool | Description |
| List files in a project or task. |
| Get a file by ID. |
| Delete a file. |
| Copy a file to another project. |
Labels / Tags (ENABLE_LABELS, default on)
Tool | Description |
| List labels, optionally filtered by project. |
| Get a label by ID. |
| Create a new label (with optional color). |
| Update an existing label. |
| Delete a label. |
Documents (ENABLE_DOCUMENTS, default on)
Tool | Description |
| List documents in a project. |
| Get a document by ID. |
| Create a new document in a project. |
| Update an existing document. |
| Delete a document. |
| Move a document to another project. |
Milestones (ENABLE_MILESTONES, default on)
Tool | Description |
| List milestones in a project. |
| Get a milestone by ID. |
| Create a new milestone. |
| Update an existing milestone. |
| Delete a milestone. |
| Archive a milestone. |
Tasks (ENABLE_TASKS, default on)
Tool | Description |
| List tasks with project / member / milestone / status filters. |
| Get a task by ID. |
| Create a task or subtask (parent via |
| Update an existing task. |
| Delete a task. |
| Mark a task as complete. |
| Archive a task. |
Task Groups (ENABLE_TASK_GROUPS, default on)
Tool | Description |
| List task groups (optionally by project). |
| Get a task group by ID. |
| Create a new task group in a project. |
| Update an existing task group. |
| Delete a task group. |
Messages (ENABLE_MESSAGES, default on)
Tool | Description |
| List messages in a chat, task, document, or file. |
| Get a message by ID. |
| Post a new message to a chat. |
| Edit an existing message. |
| Delete a message. |
| Mark a message as seen. |
Subteams / Portfolios (ENABLE_SUBTEAMS, default on)
Tool | Description |
| List all subteams/portfolios. |
| Get a subteam by ID. |
| Create a new subteam. |
| Update an existing subteam. |
| Delete a subteam. |
Projects (ENABLE_PROJECTS, default on)
Tool | Description |
| List all projects accessible to the user |
| Create a new project |
| Get a specific project by ID |
| Update an existing project |
| Delete a project |
| Invite a user to a project |
| Leave a project |
| Start a project (change status to active) |
| Add a custom field to a project |
| Get all custom fields for a project |
| Update a custom field value for a project |
Folders (ENABLE_FOLDERS, default on)
Tool | Description |
| Get the root folder structure |
| Create a new folder |
| Get a specific folder by ID |
| Get all children of a folder |
| Update a folder |
| Delete a folder |
Members (ENABLE_MEMBERS, default on)
Tool | Description |
| List all team members |
| Get a specific team member by ID |
Webhooks (ENABLE_WEBHOOKS, default on)
Tool | Description |
| List all webhooks for an app |
| Create a new webhook |
| Update an existing webhook |
| Delete a webhook |
Time Tracking (ENABLE_TIME, default on)
Tool | Description |
| Get time tracking report |
| Get total time duration for tasks/projects |
Custom Fields (ENABLE_FIELDS, default on)
Tool | Description |
| List all custom fields definitions |
| Get a specific custom field definition by ID |
Apps (ENABLE_APPS, default on)
Tool | Description |
| List all installed applications |
| Get a specific app by ID |
Chat (ENABLE_CHAT, default on)
Tool | Description |
| List all chat conversations |
| Get a specific chat conversation by ID |
Miscellaneous (ENABLE_INVITE, ENABLE_TEMPLATES, ENABLE_USERS, ENABLE_AUTH)
Tool | Description |
| List all active invite links |
| List all project templates |
| Get the currently authenticated user profile |
| Refresh the authentication token |
Tool coverage is driven by
docs/api-openapi-source.yaml(NiftyPM's published OpenAPI spec). The current set implements all 117 documented operations.
Environment Variables
Required
Variable | Description |
| OAuth 2.0 bearer token. Required. |
| OAuth refresh token (reserved for future auto-refresh). |
| OAuth client ID. |
| OAuth client secret. |
Optional — Tool Toggles
Each toggle defaults to true (enabled). Set to false to skip registration of that group on startup.
Variable | Controls |
| Files tools |
| Labels / tags tools |
| Documents tools |
| Milestones tools |
| Messages tools |
| Task groups tools |
| Tasks tools |
| Subteams / portfolios tools |
| Projects tools |
| Folders tools |
| Members tools |
| Webhooks tools |
| Time tracking tools |
| Custom fields tools |
| Apps tools |
| Chat tools |
| Invite tools |
| Templates tools |
| Users tools |
| Auth tools |
Optional — Runtime
Variable | Default | Description |
|
|
|
|
| Port for the local HTTP transport (only used when |
Project Structure
niftypm-mcp/
├── src/
│ ├── index.ts # Local entry: FastMCP + stdio/httpStream
│ ├── worker.ts # Cloudflare Workers entry (MCP handler)
│ ├── client.ts # NiftyPM HTTP client (Bearer auth)
│ ├── config.ts # Env loading + validation
│ └── tools/
│ ├── index.ts # Barrel export for register*Tools
│ ├── files.ts # niftypm_*_file[... ]
│ ├── labels.ts # niftypm_*_label[...]
│ ├── documents.ts # niftypm_*_document[...]
│ ├── milestones.ts # niftypm_*_milestone[...]
│ ├── tasks.ts # niftypm_*_task[...]
│ ├── taskgroups.ts # niftypm_*_taskgroup[...]
│ ├── messages.ts # niftypm_*_message[...]
│ ├── subteams.ts # niftypm_*_subteam[...]
│ ├── projects.ts # niftypm_*_project[...]
│ ├── folders.ts # niftypm_*_folder[...]
│ ├── members.ts # niftypm_*_member[...]
│ ├── webhooks.ts # niftypm_*_webhook[...]
│ ├── time.ts # niftypm_*_time[...]
│ ├── fields.ts # niftypm_*_field[...]
│ ├── apps.ts # niftypm_*_app[...]
│ ├── chat.ts # niftypm_*_chat[...]
│ ├── invite.ts # niftypm_*_invite[...]
│ ├── templates.ts # niftypm_*_template[...]
│ ├── users.ts # niftypm_*_user[...]
│ └── auth.ts # niftypm_*_auth[...]
├── docs/
│ ├── api-openapi-source.json # NiftyPM OpenAPI spec (source of truth)
│ └── api-openapi-source.yaml
├── dist/ # tsc output (gitignored)
├── .env.example # Template for local stdio env
├── .dev.vars.example # Template for `wrangler dev`
├── wrangler.jsonc # Cloudflare Workers config
├── tsconfig.json # TypeScript config (Node16, ES2022)
├── package.json
├── bun.lock
└── LICENSE # MITScripts
Script | Command | What it does |
|
| Type-check and emit JavaScript to |
|
| Run the local server (stdio). |
|
| Run with file watch for fast local iteration. |
|
| Run the Cloudflare Workers build locally. |
|
| Deploy to Cloudflare Workers. |
Contributing
Contributions are welcome. A few guidelines:
Add one tool group per file. Mirror the existing layout in
src/tools/so registration stays predictable.Validate with Zod. Every tool parameter object should be a
z.object({...})schema —fastmcpuses it to generate JSON Schemas for the client.Keep the client thin. New endpoints should generally reuse the existing
NiftyPMClient(get/post/put/delete) rather than callingfetchdirectly.Update the README. When you add or rename a tool, update the Available Tools table.
Run
bun run buildbefore opening a PR —tscstrict mode is the only static check wired in.
License
This project is licensed under the MIT License. © 2026 Dr Muhammad Aizat Md Hawari & NiftyPM MCP Contributors.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cmdaltctr/niftypm-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server