Create Accountor Login
Docs

Templates

Part of the MountDev Ops Contracts documentation. Updated November 19, 2026

MountDev Ops Contracts documentation | Updated November 19, 2026

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Every update passes all 8,865 automated checks before it ships, and every screen change is walked through before release.

What a Template Holds

Templates are records in the Templates module. Add and change them like any record, under Templates in the Contracts menu.

  • Name: what you choose when you start a contract.
  • Wording: the contract itself. Write a field as {{Field Name}}, and it is filled in when you start a contract. Start a line with # to make it a heading. Blank lines separate paragraphs.
  • Fields: one per line. Write Fee to ask for a value, or Fee: $249 to give it a starting value. Any {{Field}} in the wording that is not listed here is asked for too.
  • Signer roles: who signs, in order, separated by commas, such as Client, Rivera Landscaping. Starting a contract lays out one signer for each role, with the contact as the first.
  • Term in months: how long a contract lasts. A contract started from it ends one term after its start date unless you give an end date.
  • Renewal: Renews automatically, Renew by hand, or Does not renew (Renewals and End Dates).
  • Days of notice before renewal or end: how early your team hears about a renewal or end date. Contracts Settings has the default.
  • Status: Active, Draft, or Retired. Only an Active template is offered when you start a contract, so a Draft is never used by accident. Retired stops offering one. Contracts already started from a template are not affected, because each holds its own wording.

Fields Filled in for You

These fields fill themselves from the contract: {{Company}}, {{Contact}}, {{Contact Email}}, {{Title}}, {{Date}} (the day it was started), {{Start Date}}, {{End Date}}, and {{Our Company}} (your company's name).

Seeing a Template's Fields

Action contracts.template.get returns a template's fields with their starting values, the fields filled in for you, its signer roles, term, renewal, and wording. The Start a Contract window uses it to show the right inputs.

Templates Your AI Agent Saves

Your AI agent can write a contract template for you, but it can never put one to use. The wording is legal text, so what an agent writes is a draft for a person, and your company's lawyer, to read.

  • Save a Template (action contracts.template.save, MCP tool contracts_template_save) saves a template's name, wording, fields, signer roles, term, renewal, and notice days. It follows the same rules as the Templates screen. It never starts or sends a contract.
  • Always a Draft. A template saved this way is a Draft. It is not offered when a contract starts, not offered in Contracts Settings for accepted proposals, and not offered to an automation, until a person sets its Status to Active on the Templates screen.
  • An Active template is never changed in place. If your agent is asked to change one, it saves a new Draft copy named with "(Draft)" after the name, and says so. When you set the copy Active, you may retire the one it replaces. Contracts already started never change.
  • List Templates (action contracts.template.list, MCP tool contracts_template_list) returns each template's name, status, field names, signer roles, term, and renewal, a page at a time, without the wording. To read the wording of one template, use contracts.template.get with its id.

Giving an agent these tools is your choice in Settings, Connections. They need the permissions contracts.template_save and contracts.template_list.

Ask Us Anything

We’d love to hear from you!