Skip to main content
Connecting your agent lets Claude Code, Codex or Cursor work with your Pinework tasks. It can list tasks, read one, comment on it and move it to a new status. It acts as you, in your workspace. You have two ways in. The Pinework MCP server gives your agent Pinework tools over MCP. The pinework CLI gives it shell commands. Pick one. Both reach the same tasks.

Before you start

  • You need a Pinework account and a workspace.
  • For the MCP server, your account must belong to exactly one workspace. Sign-in fails when it belongs to more than one.
  • For the CLI, your agent must be able to run shell commands on your machine.

Connect through the MCP server

The server lives at https://api.pinework.ai/mcp. Your agent signs in with OAuth in your browser. You never paste a token.
1

Add the server to your agent

In Claude Code, run /mcp, pick pinework and choose to authenticate.
2

Approve the client in your browser

Your browser opens a Pinework page titled Authorize Pinework MCP. If you are signed out, click Sign in to continue first. Then click Authorize MCP client.The page says Authorized and sends you back to your agent.
3

Check that it works

Ask your agent to list your open Pinework tasks. It calls list_tasks and shows them.In Pinework, open Settings, then Connected devices. Your agent appears under Clients, with when it connected and when it was last used.

Tools your agent gets

By default the server exposes a small task toolset. These are the tools that matter most: The default set also covers dependencies, files and runs. To expose every Pinework tool, add ?toolset=admin to the URL:
The full set is much larger. It also manages agents, automations, secrets and MCP servers. Use it only when your agent needs that.

Connect through the CLI

Your agent runs pinework commands in its shell, with your login.
1

Install the CLI

2

Sign in

Your browser opens to sign in. The terminal prints Logged in successfully. with your workspace name. The CLI picks the workspace for you when your account has exactly one.
3

Check the login

It shows the credential in use and its workspace. It never prints the token.
4

Tell your agent which commands to use

Add a note to your CLAUDE.md or AGENTS.md that names these commands:
Every command accepts --help. Your agent can read it to find flags.

Remove access

To cut off an MCP client, open Settings, then Connected devices. Under Clients, open the client’s menu and click Revoke. Confirm with Revoke client. The client can no longer reach Pinework. To cut off the CLI on a machine, run pinework logout. It deletes the stored token and local config.

Troubleshooting

Sign-in fails with unable to determine target company. The MCP sign-in needs exactly one workspace on your account. Use the CLI instead. Sign-in fails with User has no active company membership. Your account has no workspace yet. Finish signing up in the dashboard, then connect again. Not logged in. Run pinework login first. The CLI has no stored login on this machine. Run pinework login.

Next

Assign a task

Hand a task to a Pinework agent.

Tasks

Statuses, assignees and how a task moves.

Key concepts

The words Pinework uses, in one page.

Mac app

Run Pinework agents on your own Mac.