Nusk MCP

Let your AI agent read and update your projects. A remote MCP server for Nusk, a project management tool with sprints, Gantt schedules, RAID logs and a wiki.

What this is

Nusk is where your team keeps tasks, schedules, risks and docs. This server lets an AI agent, such as Claude Code, Cursor or Codex, work with that same data from your editor or terminal. You skip the copy and paste between the tracker and the chat.

Ask things like:

• "What is on my plate this week?"

• "What are the top risks on project HQ?"

• "Which tasks are on the critical path?"

• "Create a task under HQ-12 for the login timeout bug and add it to the current sprint."

The server runs on nusk.dev. This repository holds the setup guide, config examples and the registry file. There is no code to install.

Related MCP server: plugins

Quick start

You need a Nusk workspace. If you don't have one, create one.

1. Create a token. In Nusk, open Profile → API tokens and create one. Start with read-only. The token is shown once, so copy it.

2. Connect your agent. Replace YOUR-WORKSPACE with your workspace name (the part after nusk.dev/ in the address bar).

Claude Code:

claude mcp add --transport http nuskpm \
  https://nusk.dev/YOUR-WORKSPACE/api/mcp \
  --header "Authorization: Bearer nusk_..."

Cursor and other clients that read mcp.json (file):

{
  "mcpServers": {
    "nuskpm": {
      "url": "https://nusk.dev/YOUR-WORKSPACE/api/mcp",
      "headers": { "Authorization": "Bearer nusk_..." }
    }
  }
}

Codex, in ~/.codex/config.toml (file):

[mcp_servers.nuskpm]
url = "https://nusk.dev/YOUR-WORKSPACE/api/mcp"
bearer_token_env_var = "NUSKPM_TOKEN"

Any client that supports remote HTTP MCP servers with a bearer header should work the same way.

3. Ask a question. Try list my projects. If the agent answers with your project codes, you're connected.

Self-hosting Nusk? The address is https://<your-server>/api/mcp.

What it looks like

These are real screens from the sample workspace the tools read from.

Tools

30 tools. Sixteen only read data. Fourteen change data and are hidden when you use a read-only token.

Read

Write

Projects are named by their two-letter code, for example HQ. Work items use keys such as HQ-0012.

Safety

• The agent is you. It has your project roles and nothing more. It cannot see or change what you can't.

• Read-only tokens expose only the read tools.

• Tokens expire. You choose the expiry, and you can revoke a token any time under Profile → API tokens.

• Changes are traceable. Edits made through MCP are marked "via AI agent (MCP)" in revision history and can be reverted.

• Rate limit: 600 requests per minute per token.

Treat a token like a password. Don't commit it. Use an environment variable where your client supports it, as in the Codex example.

Troubleshooting

Try Nusk without installing anything

• Live demo: a sample workspace with three projects, no signup. It lasts one hour. Connecting an agent needs your own workspace.

• Full MCP guide

• Features

• Jira alternative: how Nusk compares and how to import your Jira issues

• Self-hosted option: run Nusk on your own servers

• Learn project management

Feedback

Missing a tool? Something broke? Open an issue. A bug report with the tool name and the error text gets fixed fastest. If Nusk is useful to you, a star helps other people find it.

License

The docs and examples in this repository are MIT licensed (LICENSE). The Nusk service, name and logo are not part of that license.