Connect your agent

NEWWORK Projects is an MCP server. Your agent connects to it with one URL and a personal token, and gets the brief, the checks and over 30 tools for the work around the code. It works on every plan, including Free, and MCP calls are never counted or metered.

1. Create a token

Open Workspace settings → Agents & MCP and choose Create token. The token:

• acts as you, with your permissions, in this one workspace;
• is shown once, starts with nwmcp_ and is valid for 90 days;
• can be revoked any time from the same page, which also shows when it was last used.

Give each agent or machine its own token, so you can revoke one without the others.

2. Add it to your agent

The endpoint is https://app.newworkprojects.com/api/mcp over Streamable HTTP, with the token as a bearer token. Replace nwmcp_… with your token.

{
  "mcpServers": {
    "newwork-projects": {
      "url": "https://app.newworkprojects.com/api/mcp",
      "headers": {
        "Authorization": "Bearer nwmcp_…"
      }
    }
  }
}

The settings page shows the same snippets with your token already filled in, and for Cursor an Add to Cursor button.

3. Ask for work

Pick up my next ready ticket in NEWWORK Projects and build it.

A typical run: pm-my-work finds your tickets with their readiness, pm-item-get reads the brief and its checks, pm-item-start moves the ticket to In progress and suggests a branch name and commit prefix, pm-check-tick passes each check with the pull request or test that proves it, and pm-item-status moves it to review with the time it logged.

If a brief isn’t ready, pm-item-start says what is missing, so the agent can ask you instead of guessing.

The tools

pm-docs-search and pm-doc-get read a product’s documentation on every plan. The four proposal tools need Business: an agent that built a ticket can propose the docs change itself, every change quoting the diff, and a person applies it.

pm-utilities-list reads a project’s environments with their live status, links, accesses, notes and contacts, so an agent knows where staging is and which version runs there. It says whether an access has a password saved and who has access, but never returns a password: agents ask a person instead.

Agents work under your name: tickets they change, comments they write and time they log carry your name. Timers and checks that came through MCP are marked “via AI agent”.

Rules agents follow

• Evidence to pass a check. Agents must attach the pull request, commit, test run or link. A failed check needs a note saying what failed.
• Briefs before building. pm-brief-check scores a draft by the same rules as the app, so an agent that writes tickets can make them ready first.
• Nothing outside your access. The token sees what you see. Team-only projects you aren’t on don’t exist for it, and a guest’s token sees only the projects the guest works on.

Clients that only run local servers

Some clients start MCP servers as local commands. Use the newwork-projects-mcp package, which needs Node.js 18.17 or newer:

{
  "mcpServers": {
    "newwork-projects": {
      "command": "npx",
      "args": ["-y", "newwork-projects-mcp"],
      "env": { "NEWWORK_PROJECTS_TOKEN": "nwmcp_…" }
    }
  }
}

NEWWORK_PROJECTS_MCP_URL points it at another endpoint, for example a test workspace.