Docnify for AI agents

Docnify is a digital signing platform that lets teams send documents for signature and manage templates alongside tools like Jira and Google Docs. 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.

DocumentsAPI keyMCP + RESTdocnify.com
AUDIT LOG · DOCNIFYPOLICY: acme-support
09:41:07 · claude · u_8f2read
docnify.list_documents
List Documents✓ allowed · 212ms
09:41:08 · claude · u_8f2read
docnify.get_document
Get Document✓ allowed · 164ms
09:41:09 · claude · u_8f2write
docnify.create_document_fields
Create Document Fields✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
docnify.delete_document
Delete Document✕ blocked · policy: deny
EVERY DOCNIFY CALL, ON THE RECORD
01 · USE CASES

What agents do in Docnify.

01

Send a document for signature

Send a document to a named recipient once the sender confirms the fields and signing order.

02

Check a document's signing status

Get a document's current status to tell a customer whether their contract has been signed yet.

03

Confirm before deleting a document

Hold a delete request for approval, since removing a document also discards its recipients and fields.

02 · ACTIONS

13 Docnify actions, graded by risk.

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

read

4

Look things up. Allowed by default.

  • docnify.get_document
    Get Document
  • docnify.get_template
    Get Template
  • docnify.list_documents
    List Documents
  • docnify.list_templates
    List Templates

write

6

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

  • docnify.send_document
    Send Document
  • docnify.add_document_recipient
    Add Document Recipient
  • docnify.create_document_fields
    Create Document Fields
  • docnify.update_document_fields
    Update Document Fields
  • docnify.update_document_recipient
    Update Document Recipient
  • docnify.resend_document
    Resend Document

destructive

3

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

  • docnify.delete_document
    Delete Document
  • docnify.delete_document_fields
    Delete Document Field
  • docnify.delete_document_recipient
    Delete document recipient
03 · HOW IT WORKS

Docnify in three steps.

  1. 01Your users connect DocnifyThey add their Docnify api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Document Fields” can wait for the user, and “delete Document” can be denied outright.
  3. 03Any agent can actYour agent calls Docnify 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('docnify', {
  read: 'allow',
  write: 'ask',        // create_document_fields
  destructive: 'deny',  // delete_document
})

# 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 Docnify connects.

Users add their Docnify 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 Docnify 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 Docnify from any agent.

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

Docnify and Arc0, answered.

Q01

Can I use Docnify with Claude, ChatGPT or Cursor?

Yes. Connect Docnify 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 Docnify actions you allow.

Q02

How do users connect Docnify?

Users add their Docnify 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 Docnify actions can my agent take?

13 in total: 4 read, 6 write and 3 destructive, such as “create Document Fields”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Docnify?

Yes. Actions like “delete Document” 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 Docnify too?

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

Get started

Plug Docnify into your agent.

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

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