Checkvist for AI agents

Checkvist manages hierarchical lists and tasks with tags, due dates, and assignees, giving a team a lightweight outliner for tracking work. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Project managementAPI keyMCP + RESTcheckvist.com
AUDIT LOG · CHECKVISTPOLICY: acme-support
09:41:07 · claude · u_8f2read
checkvist.list_checklists
List Checklists✓ allowed · 212ms
09:41:08 · claude · u_8f2read
checkvist.search_tasks
Search Tasks✓ allowed · 164ms
09:41:09 · claude · u_8f2write
checkvist.create_task
Create Task✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
checkvist.delete_task
Delete Task✕ blocked · policy: deny
EVERY CHECKVIST CALL, ON THE RECORD
01 · USE CASES

What agents do in Checkvist.

01

Create a task in a checklist

Create a new task inside a checklist and assign it a due date.

02

Search across tasks

Search across tasks for a keyword before deciding where new work belongs.

03

Confirm before deleting a checklist

Confirm before deleting a checklist, since every task and note inside it goes with it.

02 · ACTIONS

16 Checkvist actions, graded by risk.

Every Checkvist action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

6

Look things up. Allowed by default.

  • checkvist.search_tasks
    Search Tasks
  • checkvist.get_checklist
    Get Checklist
  • checkvist.get_task_tree
    Get Task Tree
  • checkvist.get_tasks_page
    Get Tasks Page
  • checkvist.list_checklists
    List Checklists
  • checkvist.get_tasks_outline
    Get Tasks Outline

write

8

Create and change things. Allow, or ask the user first.

  • checkvist.create_task
    Create Task
  • checkvist.update_task
    Update Task
  • checkvist.create_checklist
    Create Checklist
  • checkvist.update_checklist
    Update Checklist
  • checkvist.update_task_tags
    Update Task Tags
  • checkvist.import_tasks
    Import Tasks
  • checkvist.replace_tasks
    Replace Tasks
  • checkvist.set_task_status
    Set Task Status

destructive

2

Delete, cancel or archive. Ask first, or deny outright.

  • checkvist.delete_task
    Delete Task
  • checkvist.delete_checklist
    Delete Checklist
03 · HOW IT WORKS

Checkvist in three steps.

  1. 01Your users connect CheckvistThey add their Checkvist api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Task” can wait for the user, and “delete Task” can be denied outright.
  3. 03Any agent can actYour agent calls Checkvist through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('checkvist', {
  read: 'allow',
  write: 'ask',        // create_task
  destructive: 'deny',  // delete_task
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Checkvist connects.

Users add their Checkvist api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Checkvist connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Checkvist from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Checkvist and Arc0, answered.

Q01

Can I use Checkvist with Claude, ChatGPT or Cursor?

Yes. Connect Checkvist to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Checkvist actions you allow.

Q02

How do users connect Checkvist?

Users add their Checkvist api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Checkvist actions can my agent take?

16 in total: 6 read, 8 write and 2 destructive, such as “create Task”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Checkvist?

Yes. Actions like “delete Task” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Checkvist too?

Yes. The same Checkvist connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Checkvist into your agent.

Your users connect Checkvist once, under your brand. Your agent gets 16 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan