How to integrate Oksign MCP with Hermes

Oksign logo
Hermes logo
divider

Introduction

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows.

This guide explains the easiest and most robust way to connect your Oksign account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.

Also integrate Oksign with

What is Composio Connect?

Composio Connect is a consumer offering that lets anyone plug 1,000+ applications directly into their agent harness — including Hermes. It can:

  • Search and load tools from relevant toolkits on-demand, reducing context usage.
  • Chain multiple tools to accomplish complex workflows via a remote workbench, without excessive back-and-forth with the LLM.
  • Manage app authentication end-to-end with zero manual overhead.

Integrating Oksign with Hermes

Using Composio Connect CLI

1. Install the Composio CLI

Run the install script directly, or paste https://composio.dev/hermes into your Hermes chat box to have it installed for you.

bash
curl -fsSL https://composio.dev/install | bash
Hermes authenticating with Composio

2. Authenticate

Once the CLI is installed, ask Hermes to authenticate with Composio.

3. Connect to Oksign

Ask your agent to connect to Oksign, or simply request any Oksign-related task. Hermes will prompt you to authenticate and authorize access.

4. Done. You're all set with a new Oksign connection.


Using Composio Connect MCP

1. Get your MCP URL and API Key

Go to dashboard.composio.dev and copy your Connect MCP URL and API key.

Copy MCP URL and API key from Composio dashboard

2. Open the Hermes config file

bash
nano ~/.hermes/config.yaml

3. Add the Composio Connect MCP server

bash
mcp_servers:
  composio:
    url: "https://connect.composio.dev/mcp"
    headers:
      x-consumer-api-key: "YOUR_COMPOSIO_API_KEY"
    connect_timeout: 60
    timeout: 180

Save with Ctrl + O, Enter, then exit with Ctrl + X.

4. Restart your Hermes agent

Once restarted, ask your agent to connect to Oksign or request any Oksign-related task. It will prompt you to authenticate and authorize access.

5. Done!

What is the Oksign MCP server, and what's possible with it?

The Oksign MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Oksign account. It provides structured and secure access so your agent can perform Oksign operations on your behalf.

Supported Tools & Triggers

Tools
Remove BriefcaseTool to remove a previously created briefcase from OKSign platform.
Retrieve Briefcase InformationTool to retrieve a previously uploaded briefcase tokeninfo for consultation.
Remove ContactsTool to remove specified contacts from the account's contact list.
Retrieve ContactsTool to retrieve the list of contacts stored in the account.
Upload ContactsTool to insert or update contact information in the account's contact list.
Retrieve Account CreditsTool to retrieve account credit balance and storage information.
Check Document ExistsTool to check if a signed or unsigned document still exists on the OKSign platform.
Remove DocumentTool to remove a signed or unsigned document from the OKSign platform.
Upload DocumentTool to upload a PDF or Word document to OKSign platform for completion and/or signing.
Create Editor Express SessionTool to invoke the OKSign Editor Express for modifying documents and form descriptors.
Upload Form DescriptorTool to upload form descriptor defining signature fields and other field types to a document.
Get Active DocumentsTool to retrieve all active document IDs and properties from OKsign account.
Retrieve Linked Document ListTool to retrieve the list of linked signed or source document IDs related to a specific document.
Upload NotificationsTool to upload notifications defining email(s) and/or SMS(es) to be sent to signer(s) with signing links.
Update Organization Token InfoTool to update organizational token information and settings for the account.
Remove SignExpress TokenTool to remove a previously uploaded SignExpress tokeninfo JSONObject from the OKSign platform.
Retrieve UsersTool to retrieve the list of users associated with the OkSign account.

Way Forward

With Oksign connected, Hermes can now act on your behalf whenever it detects a relevant task or you ask it to.

From here, you can extend Hermes further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup. Each new integration compounds what Hermes can do for you.
  • Build workflows across tools: Once multiple apps are connected, Hermes can chain actions together — turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Let it learn your patterns: The more you use Hermes, the better it gets at anticipating how you'd handle recurring tasks. Give it feedback on drafts and decisions, and it will adapt.

If you run into trouble or want to share what you've built, join the community or check out the Docs for deeper configuration options.

How to build Oksign MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Oksign MCP?

With a standalone Oksign MCP server, the agents and LLMs can only access a fixed set of Oksign tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Oksign and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Hermes?

Yes, you can. Hermes fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Oksign tools.

Can I manage the permissions and scopes for Oksign while using Tool Router?

Yes, absolutely. You can configure which Oksign scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Oksign data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.