← zovo.one

INDIVIDUAL MCP TOOL

agreement_get

Read one service agreement in full by SA number or client name: parties, scope, deliverables, rate and payment terms, dates, termination, liability cap, jurisdiction, the clauses it carries, its status and its status history.

zovo.onenone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.zovo.one/mcp/service-contract

No auth detected

Connect to this endpoint to inspect the live schema for agreement_get and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

  • A tool name or description suggests a financial action.

Parent server

zovo.one

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.mcp-service-agreement]
url = "https://mcp.zovo.one/mcp/service-contract"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "mcp-service-agreement": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/service-contract"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: mcp-service-agreement
Remote MCP URL: https://mcp.zovo.one/mcp/service-contract

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "mcp-service-agreement": {
      "url": "https://mcp.zovo.one/mcp/service-contract"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "mcp-service-agreement": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/service-contract"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "mcp-service-agreement",
  "transport": "streamable-http",
  "url": "https://mcp.zovo.one/mcp/service-contract"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • agreement_create — Write a service agreement between a freelancer and a client before the work starts: the parties, the scope of services, the deliverables, the rate and payment terms, start and end dates, a termination notice period, a liability cap and the governing jurisdiction.
  • agreement_list — List service agreements newest first: parties, status, rate, dates and the clauses each carries.
  • agreement_update_status — Move one agreement exactly one step: draft, sent, signed, expired, stamping the date and an optional note into its history.
  • clause_library — List the built-in clause library: intellectual property assignment, mutual confidentiality, late payment interest, kill fee and revision rounds.
  • agreement_render — Render a service agreement ready to send and sign: the parties, the services, the deliverables, the payment terms, the term, termination, liability, jurisdiction, any library clauses it carries, and a signature block for both parties.
  • agreement_checklist — The before-you-send-it checklist for one agreement: every missing field is listed, and terms whose absence cuts one way are flagged neutrally -- as written, what the gap means for both parties -- such as no termination clause or an uncapped liability.
  • license_status — Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL.
  • license_activate — Turn Pro on for this connection with key, an MCPL1.