Quickstart

This guide walks through connecting to the Lofty MCP server and calling your first operation. By the end you’ll have made a full search_apis → describe_api → invoke_api round trip and retrieved real lead data.

Get a credential

You need an API key or an OAuth 2.0 access token — the same credentials used for the direct REST API. If you don’t have one yet, follow the API Quickstart to get one.

Over MCP, always send your credential as Authorization: Bearer <token> — even an API key, which normally uses the token prefix on the direct REST API. See Authentication for why.

Connect your MCP client

Point any Streamable HTTP MCP client at:

https://mcp.lofty.com/mcp

claude mcp add --transport http lofty https://mcp.lofty.com/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

{
  "mcpServers": {
    "lofty": {
      "type": "http",
      "url": "https://mcp.lofty.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

curl https://mcp.lofty.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0", "id": 1, "method": "initialize",
    "params": {"protocolVersion": "2025-06-18", "capabilities": {}, "clientInfo": {"name": "quickstart", "version": "0.1"}}
  }'

Any client that speaks Streamable HTTP works the same way — consult your client’s docs for its equivalent of “add a remote MCP server with a custom header.” A successful initialize call includes serverInfo and an instructions field describing the four tools and how to use them together.

Search for an operation

Describe what you want to do in plain words with search_apis rather than guessing an operationId — ids are stable but not derivable from the resource name (deleting a lead, for example, is lead_trash, not lead_delete).

curl https://mcp.lofty.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d '{
    "jsonrpc": "2.0", "id": 2, "method": "tools/call",
    "params": {"name": "search_apis", "arguments": {"query": "get a lead by id"}}
  }'

The response includes lead_get among the candidates, each with its operationId, HTTP method, path, and a one-line summary.

Describe the operation

Call describe_api with the operationId to get its full parameter schema before calling it.

curl https://mcp.lofty.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d '{
    "jsonrpc": "2.0", "id": 3, "method": "tools/call",
    "params": {"name": "describe_api", "arguments": {"operationId": "lead_get"}}
  }'

The response’s inputSchema shows lead_get takes a required leadId (integer) and an optional withTrash (boolean).

Invoke it

Call invoke_api with the arguments describe_api described.

curl https://mcp.lofty.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d '{
    "jsonrpc": "2.0", "id": 4, "method": "tools/call",
    "params": {"name": "invoke_api", "arguments": {"operationId": "lead_get", "arguments": {"leadId": 100001}}}
  }'

A successful call returns the same JSON body the direct REST API would — wrapped under content[0].text (a string, for any MCP client) and mirrored in structuredContent (already-parsed JSON, for clients that support it).

Lead, task, and other entity IDs are 64-bit integers. If you’re consuming structuredContent from JavaScript or TypeScript, read the JS/TS Integration Guide first — JSON.parse() silently corrupts IDs above 2^53 - 1.

Get Started

Authentication

Core Concepts

Guides

Lofty CLI

MCP Server

Next steps

Tools Reference

Troubleshooting

​Next steps

Tools Reference

Troubleshooting

Next steps