Skip to content
English
Log In to Customer Portal
Log In to Workspace
  • There are no suggestions because the search field is empty.

MCP Server

MCP is designed for technical and power users who already use their own AI tools. It is enabled by issuing an API vendor token, which means any MCP-compatible client can connect directly to a workspace and work with live data such as deals, properties, contacts, companies, and custom objects. 

 

The MCP server exposes five tools to the connected AI client:

Tool Function Notes
find_fields Looks up exact field names, types, and valid values before
searching/writing.		 Prevents guessing; reveals dropdown
options like valid deal stages.
list_objects Searches/filters/sorts a list of records. Supports free-text search, filters, sorting, pagination.
get_object Loads one full record by ID. Returns every field, including custom fields.
create_object  Creates a new record. Only runs on an explicit user request.
update_object Updates specific fields on an existing record. Partial update — only named fields change.

💡Things to Consider

MCP covers Deals (Projects), Pipelines, Properties, Companies, Contacts, and Custom Objects. 

Requirements:

MCP URL: https://app.termsheet.com/mcp/v1

API Key: Configure API Key in Settings > API

Common Troubleshooting

Wrong field name used — the AI is instructed to always look up field names before writing. This usually means it needs to re-check the field catalog, not that MCP is broken.

Percent fields: Stored on a 0–100 scale, not 0–1 (50% is 50 , not 0.5 ).

Redacted data: A field value of "REDACTED" is intentional — it means the connected user doesn't have permission to see that data.

Deleted records: Excluded from normal searches unless the AI explicitly asks for  soft-deleted records.

This is a read and write integration: create_object / update_object will change
workspace data, but only on an explicit request.

⚙️Steps

  1. Configure an API Key or use an existing API Key
  2. Point the AI client to the MCP URL
  3. Use the following request headers
    Authorization: <API Key>
    Content - Type: application/json
    Accept: application/json

     Note: don't use Bearer prefix, only the raw api key