MCP and agent connections

Connect Claude, Codex, and other MCP clients to Picrowd with a connection that names its projects, its capabilities, and its expiry. Writes are planned, reviewed, and committed, and every call is audited.

What MCP is for

The Model Context Protocol lets an AI agent outside Picrowd, such as Claude Desktop, Codex, or your own assistant, read and change your records through a small set of semantic tools instead of raw API routes. It is designed for least privilege, safe retries, and human-reviewable changes.

Creating a connection

  • Open Settings → MCP and create a connection: name the client, pick one or more projects, grant only the capabilities it needs, and choose an expiry
  • Copy the configuration once; the secret is shown a single time and stored only as a hash
  • Clients that support OAuth can instead discover Picrowd and ask for consent themselves, with project selection and scope reduction on the consent screen
  • A project API token also works as an MCP credential inside its single project

Capabilities

Capabilities cap what a connection may request: Projects, Records, Record changes, Ping commands, Ping command changes, Notes, Files, Whiteboards, Whiteboard changes, Activity, and MCP audit. Tools the connection is not allowed to use are simply absent from what the agent sees.

What an agent can do

  • Resolve which projects it can see and describe their visible columns
  • Search and read records, notes, and file metadata
  • Plan a set of changes (set a field, set a ping with commands, create, archive, restore, add a note), show you the preview, then commit it atomically within 15 minutes
  • Read and change non-binary Whiteboard items in atomic batches
  • Prepare a short-lived download link for a file
  • 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.