# Autenti MCP MCP

> Autenti provides digital document signing with legal-grade electronic signatures. It handles compliance according to European eIDAS regulations. Connect this MCP to your AI client, and you gain full control over professional document workflows; manage processes, audit history, and track participant progress using natural conversation.

## Overview
- **Category:** document-management
- **Price:** Free
- **Tags:** digital-signature, identity-verification, compliance, eidas, document-workflow, audit-trail

## Description

This connector lets you run your entire digital signature pipeline through a natural language interface. You can stop manually checking individual contract statuses or digging through email threads trying to figure out who signed what. Instead, your AI client acts as the dedicated coordinator. It handles everything from starting new agreements with specific metadata to tracking participant progress and executing actions like sending, signing, or rejecting documents based on the current state. This capability is key for compliance teams needing real-time visibility into process status and audit trails. Connecting Autenti via Vinkius makes it available across any MCP-compatible client; you just talk to your agent, and it manages the complex signature coordination.

## Tools

### check_api_health
Verifies the connectivity status between your AI client and Autenti's API endpoint.

### add_new_contact
Adds a specified contact to your internal address book for future use in processes.

### create_new_signature_process
Initializes a brand new document signing workflow, requiring a title and associated metadata.

### execute_process_action
Applies a specific state-changing action (like Sign or Reject) to an existing signature process ID.

### get_user_account_profile
Fetches the metadata for the user account that is authenticated and connected to your AI client.

### get_process_details
Retrieves comprehensive details about a specific document signing workflow instance.

### list_available_process_actions
Checks and lists all possible actions that can be performed on a given document process ID.

### list_saved_contacts
Retrieves all contacts stored in your dedicated address book within Autenti.

### list_process_files
Lists all files associated with a given document signing process ID.

### list_process_participants
Shows who the current signers and observers are for a specific agreement workflow.

### list_signature_processes
Provides a list of every document signing process currently managed by the system.

### list_configured_webhooks
Retrieves the full list of active webhooks configured for your account for event monitoring.

## Prompt Examples

**Prompt:** 
```
List all my active document signature processes.
```

**Response:** 
```
I've retrieved your active processes. You currently have 3 documents in progress, including 'Service Agreement' (Status: SENT) and 'NDA'. Would you like the detailed participant metadata for any of these?
```

**Prompt:** 
```
What actions can I take on process 'proc_123'?
```

**Response:** 
```
For process proc_123, you can currently perform the following high-fidelity actions: 'SIGN_DOCUMENT', 'REJECT', or 'CANCEL'. Shall I proceed with the signature for you?
```

**Prompt:** 
```
Add 'John Doe' (john@example.com) to my Autenti contacts.
```

**Response:** 
```
Contact created! John Doe has been successfully added to your Autenti address book (ID: cont_456). He is now available for process association. Shall I start a new signature workflow for him?
```

## Capabilities

### Start document signing processes
Initiates a new digital agreement workflow by providing necessary titles and metadata.

### Get process status details
Retrieves the current state, high-fidelity metadata, and historical audit data for any specific signature process.

### Execute workflow actions
Directly performs required document actions—like sending or rejecting—after identifying valid options for the agreement's current status.

### Manage participants and contacts
Adds new signers to your address book, lists existing contacts, and views who is currently assigned to a process.

### Monitor webhooks and processes
Accesses the full directory of active webhooks or lists all ongoing document signature workflows for monitoring purposes.

### Check API connectivity
Runs a simple check to verify that Autenti's connection is functioning correctly with your agent.

## Use Cases

### Onboarding new vendors
A Procurement Manager needs to sign a Service Agreement with five new vendors. They use `list_saved_contacts` to pull the contacts, then call `create_new_signature_process` for each vendor's specific agreement type, and finally execute the 'SEND' action via `execute_process_action`. This replaces 15 manual emails.

### Compliance audit preparation
The Compliance Officer needs to prove all NDAs signed last quarter are active. They run `list_signature_processes` for the relevant date range, then use `get_process_details` on each ID to pull the complete participant list and status record for an auditor.

### Fixing a stalled contract
A Legal team member notices a key signer hasn't responded. They check `list_process_participants`, see who is missing, then use `add_new_contact` to get the updated contact info and re-send the document using `execute_process_action`.

### Verifying system status
The Ops Engineer wants to know if the connector is working before a major sign-off. They simply call `check_api_health`. If that succeeds, they're cleared to proceed with complex workflow orchestration.

## Benefits

- No more status checks. You can list all ongoing documents using `list_signature_processes`—get a quick overview of every agreement without opening multiple tabs.
- Full control over the document state. Instead of guessing what's next, first run `list_available_process_actions`. Then, use `execute_process_action` to move the workflow forward precisely when needed.
- Perfect coordination is guaranteed. You can manage participant directories and add signers using `add_new_contact` or check existing participants with `list_process_participants`; it's all in one place.
- Audit trails are instant. The agent pulls high-fidelity metadata via `get_process_details`, giving you immediate, reliable compliance data every time.
- Operational readiness is clear. Use `check_api_health` to ensure the connection works before running anything mission-critical; it's a quick sanity check.
- Visibility into events. You can review all active webhooks using `list_configured_webhooks`, ensuring your system gets real-time alerts for incoming document events.

## How It Works

The bottom line is: Your AI client talks to Autenti; Autenti handles the complex compliance and document state changes.

1. First, subscribe to this MCP and retrieve the necessary OAuth Access Token from the Autenti Developer Portal. You need these credentials.
2. Next, instruct your AI client to list all existing signature processes using `list_signature_processes` or check for available actions on a specific process ID via `list_available_process_actions`.
3. Finally, tell your agent what you want to achieve—for example, 'Send the agreement to John Doe'—and it executes the action using tools like `execute_process_action`.

## Frequently Asked Questions

**How do I find my Autenti Access Token?**
Log in to the [**Autenti Developer Portal**](https://developers.autenti.com/), navigate to your application settings, and generate an OAuth 2.0 Access Token.

**Can I discover valid actions via AI?**
Yes! The `list_available_process_actions` tool retrieves a dynamic list of valid operations (like SEND or SIGN) based on the document's high-fidelity status.

**How do I add a new contact programmatically?**
Use the `add_new_contact` tool to register a name and email in your Autenti address book for future high-fidelity signature requests.

**How do I use `get_process_details` to track a document's status over time?**
The tool retrieves the current, high-fidelity metadata for any specific signature process. It’s useful for checking historical audit data or verifying if a contract moved from 'SENT' to 'SIGNED.' This lets your agent report exactly what happened and when it changed state.

**If I need to know who is involved, how do I use `list_process_participants`?**
This tool pulls a list of all signers and observers associated with a document process. It helps you manage collaboration by confirming if the right people are on the record or if someone needs to be added. You get clear oversight of the entire participant group.

**What should I do if my AI agent reports connection issues, and how does `check_api_health` help?**
Running `check_api_health` verifies your API connectivity instantly. If this tool confirms the connection is active, you know the problem isn't with the link itself. This helps narrow down troubleshooting to data or workflow logic issues.

**How do I verify that real-time document events are working correctly using `list_configured_webhooks`?**
This tool shows all active webhook endpoints connected to your account. You use this list to confirm the delivery mechanism is set up and operational. If a critical event isn't being received, checking these hooks confirms if the notification pipeline is broken.

**What information does `create_new_signature_process` require before I can start an agreement?**
Starting a process requires both a title and associated metadata. Providing this upfront ensures the system correctly categorizes the document from day one. It's crucial input that dictates how your agent manages the workflow lifecycle.