Integration

Connect MOCO and SignNow

When something happens in MOCO or SignNow, your agent does the next thing in the other. Describe it and it is built, tested on every scenario and kept running.

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

Build solutions, not workarounds.

What do you want MOCO and SignNow to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

Set it up in your client
Claude Code

Run this in the directory you want to work in.

claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide (opens in a new tab)
Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

Setup guide (opens in a new tab)
Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide (opens in a new tab)
Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide (opens in a new tab)
Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

Setup guide (opens in a new tab)
Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

Setup guide (opens in a new tab)

Example flows

What MOCO and SignNow can do together

From MOCO to SignNow

From SignNow to MOCO

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with MOCO and SignNow

Triggers and actions 28 triggers · 36 actions

Each app on its own

Reviews

What our customers say

More from MOCO

More into SignNow

Questions

MOCO and SignNow, answered

What can start an automation from MOCO?

Any of MOCO's 26 triggers in the catalog, including New Client, New Company, New Expense and New Exported Invoice (Bookkeeping). Describe the moment in plain language and your agent picks the right one.

What can your agent do in SignNow when something happens in MOCO?

Any of SignNow's 12 actions, including Upload Document, Upload Document & Extract Fields, Add signing link and Add template. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from SignNow to MOCO?

Yes. When something happens in SignNow, your agent can act in MOCO too. This page covers both directions: SignNow's triggers and MOCO's actions are listed here as well.

Do I have to build a connector for MOCO or SignNow?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.