MCP and agent connections

Connect Claude, Codex, and other MCP clients to selected projects or your whole account. Agents can manage projects, sharing, ordering, records and workspaces within your current permissions and plan.

What MCP is for

The Model Context Protocol lets an AI agent outside Picrowd discover and run native app actions. Whole-account connections can manage the account root and newly accessible projects, while selected-project connections retain their narrower record and Whiteboard tools. Actions follow the connected user’s current access and paid-tier limits.

Creating a connection

  • Open Settings → MCP: name the client, choose Whole account or Selected projects, grant the capabilities it needs, and choose an expiry. Select Never for no automatic expiry; you can revoke the connection in Settings anytime. Whole account works even when you have no projects yet
  • Copy the configuration once; the secret is shown a single time and stored only as a hash
  • Clients that support OAuth can instead request consent, with explicit whole-account approval or project selection and scope reduction. Existing credentials do not gain broader access automatically
  • A project API token also works as an MCP credential inside its single project

Capabilities

Whole-account Read and Whole-account Changes expose discoverable native app actions. Selected-project capabilities cover projects, records, pings, notes, files, Whiteboards and activity. MCP audit is available to user connections. Ungranted tools are absent from discovery; a scope never grants a higher role or paid tier.

What an agent can do

  • With whole-account access: create, rename, delete and share projects; manage collaborators, roles, ownership transfers, folders and sidebar order
  • Discover and execute native actions for columns, views, records, notes, attachments, Board, AI sessions and automations, Whiteboard, connected tools and account preferences
  • Run ordinary actions directly without extra MCP approval prompts, with idempotency keys to avoid duplicate writes; follow asynchronous job status before claiming completion
  • Resolve which projects it can see and describe their visible columns
  • Search and read records, notes, and file metadata
  • Alternatively use the specialized project tools to plan record changes, inspect the preview and commit atomically within 15 minutes
  • Read and change non-binary Whiteboard items in atomic batches
  • Prepare a short-lived download link for a file or a large account export; upload through the native presigned-upload and confirmation actions
  • Read the project activity feed and its own audit history

Permissions stay live

A granted capability never freezes your permissions. Picrowd re-checks the connected user’s project role, membership, hidden columns, record locks, and Whiteboard access on every call, so removing someone from a project also cuts off every agent they connected.

Audit and revocation

Every tool call records the client, tool, status, duration, project, and a trace id, with field values, note text, searches, and payloads redacted. Review it under Recent MCP activity in Settings → MCP. Revoking a connection takes effect on its next request.