Docsautomator MCP connector for AI agents

Tools your document agent reaches for on Docsautomator MCP, scoped per user.

CALL ANY TOOL

20 tools for creating documents, managing automations, orchestrating e-signature workflows, and monitoring job status in DocsAutomator.

docsautomatormcp_cancel_esign_session

Cancel Esign Session

Cancel an in-progress signing session. Cannot cancel already completed sessions. Optionally provide a cancellation reason.

Parameters

Name

Type

Required

Description

sessionId

string

Required

The unique ID of the signing session to act on.

reason

string

Optional

Optional reason for cancelling the signing session.

docsautomatormcp_create_automation

Create Automation

docsautomatormcp_create_document

Create Document

docsautomatormcp_delete_automation

Delete Automation

docsautomatormcp_duplicate_automation

Duplicate Automation

docsautomatormcp_duplicate_template

Duplicate Template

docsautomatormcp_get_automation

Get Automation

docsautomatormcp_get_esign_audit

Get Esign Audit

docsautomatormcp_get_esign_session

Get Esign Session

docsautomatormcp_get_job_status

Get Job Status

docsautomatormcp_get_queue_stats

Get Queue Stats

docsautomatormcp_get_signing_links

Get Signing Links

docsautomatormcp_list_automations

List Automations

docsautomatormcp_list_esign_sessions

List Esign Sessions

docsautomatormcp_list_placeholders

List Placeholders

docsautomatormcp_poll_job_until_complete

Complete poll job until

docsautomatormcp_resend_esign_invite

Resend Esign Invite

docsautomatormcp_send_test_email

Send Test Email

docsautomatormcp_update_automation

Update Automation

docsautomatormcp_update_automation_esignature

Update Automation Esignature

Build your Agent

Same auth pattern across every framework.

from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="docsautomatormcp")

mcp = MultiServerMCPClient({
    "docsautomatormcp": {
        "url": "https://mcp.scalekit.com/docsautomatormcp",
        "headers": {"Authorization": "Bearer " + token}
    }
})
tools = await mcp.get_tools()

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "docsautomatormcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/docsautomatormcp
// Pass: Authorization: Bearer + token

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "docsautomatormcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/docsautomatormcp
// Pass: Authorization: Bearer + token

from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="docsautomatormcp")
# Connect to MCP at https://mcp.scalekit.com/docsautomatormcp
# Pass: Authorization: Bearer + token

Try these prompts

Paste any prompt into your agent to get started.

Generate & retrieve documents

Copy the prompt

Copied

List all my active automations and generate a PDF contract from the 'Client Onboarding' template for the new deal data I provide.

Copy the prompt

Copied

Generate a proposal document from automation ID abc123 using these values and poll until the PDF is ready, then return the download link.

Manage e-signatures

Copy the prompt

Copied

Show me all pending e-signature sessions from the last 7 days and resend the invitation to any signer who hasn't opened the document yet.

Copy the prompt

Copied

Get the full audit trail for signing session xyz789 and summarize which signers have completed their signature.

SEE HOW AUTH WORKS

User authorises once. Every agent call after uses their token with scope enforcement.

Authorize

Your user connects

DocsAutomator MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

DocsAutomator MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

DocsAutomator MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

DocsAutomator MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

No items found.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought.

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.

// shared token
 audit → bot_service_account

 // scalekit
 audit → user_abc ✓

02.

Authentication is not authorization

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Docsautomator MCP as the user or as a shared key?

Scalekit resolves a per-user credential for each call. The Docsautomator MCP audit log shows the real user identity, not a shared service account.

Where is the Docsautomator MCP token stored?

In Scalekit's AES-256 encrypted vault, isolated per tenant. Tokens are auto-refreshed before expiry and revocable from a single dashboard without code changes.

Can I limit what the agent is allowed to do in Docsautomator MCP?

Pass a toolNames filter to listScopedTools. Scalekit enforces the allowed set before every API call — the agent cannot invoke tools outside the approved list.

What happens when a user revokes Docsautomator MCP access?

The token is invalidated at the next tool call. The agent fails closed rather than falling back to a shared key. Other users are unaffected and the revocation event is logged with a timestamp.

Can an agent create or delete automations on behalf of one user without affecting another user's automations?

Yes. Scalekit issues a separate credential per user, so all write operations — creating, updating, or deleting automations — execute under the authorizing user's Docsautomator workspace. One user's agent cannot touch another user's automations, and every mutation appears in the audit trail against the correct identity.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit