# How to connect Docusign eSignature to Hermes Agent

> Set up DocuSign eSignature for Hermes Agent with Agent200, then check which tools are available to your agent.

- Page: https://www.agent200.com/connectors/docusign-esignature/framework/hermes-agent/
- Connector: [Docusign eSignature](https://www.agent200.com/connectors/docusign-esignature.md)
- Framework: Hermes Agent
- Updated: 2026-11-18

## Instructions for AI agents

Goal: connect Docusign eSignature to Hermes Agent with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/docusign-esignature/framework/hermes-agent/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Hermes Agent's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure Docusign eSignature is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Hermes Agent: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Hermes Agent's exact menus or commands.
4. The first Docusign eSignature request returns an authorization link if the user has not connected Docusign eSignature yet: show it to them and continue once they have approved access on Docusign eSignature's own page.
5. Check it works with this request: "Ask Hermes Agent to list the Agent200 tools available for DocuSign eSignature, including which are read-only."
   What should come back:
   - A list of the DocuSign eSignature tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Docusign eSignature, then retry.

## Overview

This guide connects Docusign eSignature to Hermes Agent through Agent200's MCP server. When you finish, Hermes Agent can search, read and act in Docusign eSignature with the tools Agent200 provides, whenever a request needs them.

You add one MCP server to Hermes Agent with your Agent200 API key. Your Docusign eSignature account is connected through managed OAuth: you approve access once on Docusign eSignature's own page, and Agent200 keeps the connection working.

- **Connector:** [Docusign eSignature](https://www.agent200.com/connectors/docusign-esignature/)
- **Works with:** Hermes Agent · Agent app, through MCP
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [6 tools](https://www.agent200.com/connectors/docusign-esignature/framework/hermes-agent/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **Docusign eSignature enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a Docusign eSignature account.** They approve access once, on Docusign eSignature's own page.
- **Hermes Agent, with custom MCP servers allowed.** Hermes Agent is open source and self-hosted: anyone running it can add MCP servers in its config file.

## Connect Docusign eSignature to Hermes Agent

### Step 1: Create your Agent200 API key

Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Hermes Agent in the next step, as "Authorization: Bearer <your key>". One key covers Docusign eSignature and every other connector enabled for your project. Keep it out of chats and source control.

Create an API key: https://agent200.com/platform/apikeys/

### Step 2: Store your key in ~/.hermes/.env

Keep the key out of `config.yaml`: Hermes reads it from `~/.hermes/.env`.

File `~/.hermes/.env`:

```bash
AGENT200_API_KEY=your-agent200-api-key
```

### Step 3: Add the server to ~/.hermes/config.yaml

Add an entry under `mcp_servers` with the URL and the Authorization header. Do not set `transport: sse`: Agent200 serves streamable HTTP.

File `~/.hermes/config.yaml`:

```text
mcp_servers:
  agent200:
    url: "https://api.agent200.com/mcp/"
    headers:
      Authorization: "Bearer ${AGENT200_API_KEY}"
```

### Step 4: Reload and test

In a running session, run `/reload-mcp`, or restart Hermes. Then check what the server returned from a terminal.

File `Terminal`:

```bash
# In a running Hermes session: /reload-mcp
hermes mcp test agent200
hermes mcp list
```

### Step 5: Connect your Docusign eSignature account

The first time you ask Hermes Agent for something in Docusign eSignature, Agent200 returns an authorization link. Open it and approve access on Docusign eSignature's own page. Agent200 stores the connection and keeps it working; your password never reaches Hermes Agent or Agent200.

## Test your connection

Ask: "Ask Hermes Agent to list the Agent200 tools available for DocuSign eSignature, including which are read-only."

What should come back:

- A list of the DocuSign eSignature tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.

If no tools appear, check your Agent200 project access for DocuSign eSignature and make sure its tools are enabled. Tool availability depends on your project setup.

## Docusign eSignature tools Hermes Agent can call

- **List envelopes** (`docusign_list_envelopes`, read): List envelopes sent or changed since a date.
- **Get an envelope** (`docusign_get_envelope`, read): Get an envelope's status and its recipients.
- **List templates** (`docusign_list_templates`, read): List the templates in the user's account.
- **Send an envelope** (`docusign_create_envelope`, write): Send an envelope from a template to the named signers.
- **Download a document** (`docusign_get_document`, read): Download a document from an envelope.
- **Void an envelope** (`docusign_void_envelope`, write): Void an envelope that is still out for signature.

## How it works

1. **You ask Hermes Agent.** In your own words, for something in Docusign eSignature.
2. **Hermes Agent picks a tool.** It sees the Docusign eSignature tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** With your own Docusign eSignature connection, within the tools and scopes your project allows.
4. **Hermes Agent answers.** It gets the result back from the MCP server and uses it in its reply or its next step.

**Each user's own connection.** Connections belong to individual end users. A request for one user never reaches another user's Docusign eSignature account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and Docusign eSignature enforces what its API grants.

## Troubleshooting

### The connection fails and names a missing variable

Add `AGENT200_API_KEY` to `~/.hermes/.env` and run `/reload-mcp`.

### The server answers 401 or 403

Check the key in `~/.hermes/.env` and that the header reads exactly `Bearer ${AGENT200_API_KEY}`.

### The initialize request fails with 400 or 405

That points to an SSE setting. Remove any `transport: sse` line from the entry and check the URL is exactly the Agent200 MCP server address.

### The Docusign eSignature tools do not appear

Run `hermes mcp test agent200`, check the entry is not disabled and no tools filter hides them, then `/reload-mcp`. Hermes names them `mcp_agent200_...`.

### Hermes Agent shows a Docusign eSignature authorization link

You have not connected Docusign eSignature yet, or the connection needs to be approved again. Open the link, approve access on Docusign eSignature's own page, then ask Hermes Agent again.

### A tool call is refused or returns less than expected

Agent200 runs only what your project allows. Check that Docusign eSignature and the tools you need are enabled in the dashboard's Connectors settings, and that you granted Docusign eSignature the access the task needs.

### The API key was pasted into a chat or committed

Create a new key on the [API keys page](https://agent200.com/platform/apikeys/), replace it in Hermes Agent's MCP settings, and stop using the old one. Paste the key only into Hermes Agent's settings, never into a chat.

## Use Docusign eSignature with another framework

- [Docusign eSignature + Claude](https://www.agent200.com/connectors/docusign-esignature/framework/claude.md)
- [Docusign eSignature + ChatGPT](https://www.agent200.com/connectors/docusign-esignature/framework/chatgpt.md)
- [Docusign eSignature + Claude Code](https://www.agent200.com/connectors/docusign-esignature/framework/claude-code.md)
- [Docusign eSignature + Muse](https://www.agent200.com/connectors/docusign-esignature/framework/muse.md)
- [Docusign eSignature + Grok Bot](https://www.agent200.com/connectors/docusign-esignature/framework/grok-bot.md)
- [Docusign eSignature + OpenAI Dots](https://www.agent200.com/connectors/docusign-esignature/framework/openai-dots.md)
- [Docusign eSignature + Claude Duet](https://www.agent200.com/connectors/docusign-esignature/framework/claude-duet.md)
- [Docusign eSignature + OpenClaw](https://www.agent200.com/connectors/docusign-esignature/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
