MCP Server for eSignatures

Instructions

Implementation Reference

• src/mcp_server_esignatures/server.py:118-120 (handler)

  Handler for create_template tool: makes a POST request to /api/templates with the arguments and returns the response.

  if name == "create_template":
      response = await httpxClient.post(f"/api/templates?token={secret_token}", json=arguments)
      return [types.TextContent(type="text", text=f"Response code: {response.status_code}, response: {response.json()}")]

• src/mcp_server_esignatures/input_schema_templates.py:3-15 (schema)

  Pydantic/JSON schema defining the input parameters for the create_template tool.

  INPUT_SCHEMA_CREATE_TEMPLATE = {
      "type": "object",
      "properties": {
          "title": {"type": "string", "description": "Title for the new template; used for contracts based on this template."},
          "labels": {"type": "array", "description": "Assign labels for organizing templates and contracts; labels are inherited by contracts.", "items": {"type": "string"}},
          "document_elements": {
              "type": "array",
              "description": "Customize template content with headers, text, images. Owners can manually replace {{placeholder fields}} in the eSignatures contract editor, and signers can fill in Signer fields when signing the document. Use placeholders for signer names if needed, instead of Signer fields. Contract title auto-inserts as the first line.",
              "items": INPUT_SCHEMA_DOCUMENT_ELEMENTS_ITEMS
          }
      },
      "required": ["title", "document_elements"]
  }

• src/mcp_server_esignatures/server.py:55-59 (registration)

  Registration of the create_template tool in the list_tools handler, including name, description, and input schema reference.

  types.Tool(
      name="create_template",
      description="Creates a reusable contract template for contracts to be based on.",
      inputSchema=INPUT_SCHEMA_CREATE_TEMPLATE
  ),