Okdoc

com.okdocaiPublished by okdocai.comOfficial publisherv1.0.0Updated Oct 24, 2026

E-signature & document automation: create, send, track and sign documents with payments. 38 tools.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Remote Okdoc MCP server that lets an assistant create, send, track and sign documents with e-signature and payments.

What you can do
  • Create documents for e-signature workflows
  • Send documents to recipients and track their status
  • Sign documents
  • Handle payments tied to document workflows
  • The registry lists 38 tools in total, but no individual tool names or descriptions are provided, so exact capabilities beyond the above are unconfirmed.
When to use it
Useful when you want an assistant to drive e-signature and document automation end to end — preparing documents, sending them for signature, following their progress, and handling related payments — without leaving the chat.
Requirements
A remote MCP endpoint at okdocai.com over streamable HTTP. OAuth authentication is required, so an Okdoc account and an OAuth-capable client are needed. No environment variables or headers are declared.
Before you install
The server can send documents and handle payments, so actions may reach third parties and involve spending money. Signing is legally significant. OAuth grants access to your Okdoc account; review the scopes requested before connecting.

Installation

In SourceWeft

  1. Open Okdoc in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.okdocai%2Fokdoc/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "okdoc": {
      "type": "http",
      "url": "https://okdocai.com/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.