How to integrate Clientary MCP with Grok Build

Connect Grok Build to Clientary MCP. Create new invoice for a client, list all active projects this month, and more from your terminal, with authentication handled for you.

Clientary logoClientary
Api Key

Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time.

42 Tools

How to integrate Clientary MCP with Grok Build

Grok Build is xAI's terminal coding agent. It runs on Grok 4.5, plans its work before it acts, and can run multiple sub-agents in parallel. It also reads Claude Code's MCP configuration, so any server you already have in a .mcp.json is picked up with no changes.

In this guide, I will show you how to connect your Clientary account to Grok Build through Composio, so it can create new invoice for a client, list all active projects this month, send payment reminder to overdue clients, and more without leaving the terminal. Composio holds the OAuth tokens for you, and Grok Build only calls the tools you approve.

Also integrate Clientary with

Why use Composio over a standalone MCP server?

  • Read and write access. Composio's Clientary integration lets Grok Build take real actions like creating drafts, sending updates, and labeling records, not just reading data.
  • 1,000+ SaaS toolkits out of the box. One endpoint gives you a full catalog of pre-built connectors, from Gmail and Slack to Notion, Linear, and Salesforce.
  • One MCP server for every app. Wire up a single Composio server instead of maintaining a separate MCP entry for each app.
  • Smart, context-aware tool loading. Grok Build caps how many tools it holds in a single request. Composio loads only the tools a task needs, so you do not spend that budget on tools you are not using.
  • Cross-app automation. Chain actions across apps in one run. Pull a thread, summarize it in Notion, and post the highlights to Slack from a single prompt.

Prerequisites

  • Grok Build installed and signed in. Install with curl -fsSL https://x.ai/cli/install.sh | bash on macOS or Linux, or irm https://x.ai/cli/install.ps1 | iex on Windows PowerShell. On first launch Grok opens a browser to authenticate; for headless or CI use, set an XAI_API_KEY environment variable instead (create the key at console.x.ai).
  • Access to the Clientary account you want to connect.
  • The Composio MCP endpoint. Composio's server is remote and hosted, so there is nothing to run locally and no tunnel to set up.

Step-by-step: Connect Clientary to Grok Build

1. Install and verify Grok Build

Install the CLI, then restart your shell so the grok binary lands on your PATH:

bash
curl -fsSL https://x.ai/cli/install.sh | bash
which grok

On Windows, install with PowerShell instead: irm https://x.ai/cli/install.ps1 | iex. If which grok returns a path, you are set. Grok Build runs on Grok 4.5 by default; you can switch models inside the session with /model <name>.

2. Add the Composio server

Add Composio as a remote HTTP MCP server with the grok mcp add command:

bash
grok mcp add --transport http composio https://connect.composio.dev/mcp

You can also add and manage servers from inside a session. Run /mcps to open the extensions modal on the MCP tab, then add a new server and paste the Composio URL. Added this way, Grok auto-detects the name from the URL and lists the server as connect:

bash
https://connect.composio.dev/mcp
Grok Build /mcps extensions modal listing MCP servers Grok Build adding the Composio MCP server with its URL

Grok also reads Claude Code-style config, so an entry in ~/.grok/config.toml or a project .mcp.json works the same way.

3. Authenticate

Composio uses OAuth. In the /mcps modal, select the Composio server and press i to authenticate (Grok also triggers this browser flow automatically the first time it uses a Composio tool). Click Allow to authorize access. Grok stores the tokens under ~/.grok/mcp_credentials.json, and /mcps shows Composio as connected.

Grok Build prompting to authenticate the Composio MCP server Composio authorization screen with the Allow button for Grok Build

4. Start building

Ask Grok to work with your Clientary account through Composio. On the first Clientary action, Composio prompts you to connect the account through OAuth. Approve the scopes once, and Composio handles token refresh from there.

What you can do after connecting Clientary

  • Create new invoice for a client
  • List all active projects this month
  • Send payment reminder to overdue clients

Security + privacy notes (important)

  • Use least-privilege access. Grant only the Clientary scopes you actually need.
  • Review OAuth scopes before approving. Check that the requested scopes match what you expect Composio and Grok Build to do.
  • Keep write actions human-reviewed. Grok Build proposes a plan before it acts. Leave that approval step on for actions like sending messages or editing records.
  • Keep secrets out of version control. Your XAI_API_KEY and any tokens should never be committed. Use environment variables or a secrets manager.
TOOLS

Supported Tools

Every Clientary action and event your agent gets out of the box.

Create Client

Tool to create a new client record in Clientary.

Create Contact

Tool to create a new contact within a specified client.

Create Expense

Tool to create a new expense record in Clientary to track expenditures within your account.

Create Lead

Tool to create a new lead record in Clientary.

Create Project

Tool to create a new project in Clientary with name and rate.

Create Task

Tool to create a new task in Clientary.

Delete Client

Tool to remove a client and all associated projects, invoices, estimates, and contacts.

Delete Lead

Tool to permanently delete a lead and all associated Estimates and Contacts.

Delete Payment

Tool to remove an existing payment from an invoice.

Delete Payment Profile

Tool to remove a specific payment profile from a client's account.

Delete Recurring Schedule

Tool to remove a recurring schedule by its identifier.

Get Client

Tool to fetch details for a specific client using its ID.

Get Contact

Tool to retrieve a single contact by its ID.

Get Estimate

Tool to retrieve details for a single estimate by ID.

Get Expense

Tool to retrieve details for a single expense record in Clientary.

Get Hour Entry

Tool to obtain details about a specific time entry in Clientary.

Get Invoice

Tool to retrieve detailed information for a specific invoice by ID.

Get Lead

Tool to retrieve a single lead by its ID.

Get Project

Tool to retrieve a single project by its identifier.

Get Staff

Tool to retrieve a single staff member by their ID.

Get Task

Tool to retrieve a specific task by its ID.

List Client Contacts

Tool to retrieve all contacts for a specific client with pagination support.

List Client Expenses

Tool to retrieve all expenses for a specific client within an optional date range.

List Client Invoices

Tool to retrieve all invoices for a specific client with pagination support (30 results per page).

List Client Projects

Tool to retrieve all projects associated with a specific client with pagination support (10 results per page).

List Clients

Tool to retrieve all clients with pagination support (10 results per page).

List Expenses

Tool to retrieve expenses by date range (defaults to current fiscal year).

List Leads

Tool to retrieve all leads with pagination support.

List Payments

Tool to retrieve all payments with pagination support (30 results per page).

List Project Estimates

Tool to retrieve estimates scoped to a particular project with pagination support (30 results per page).

List Project Expenses

Tool to retrieve all expenses for a specific project within an optional date range.

List Project Hours

Tool to retrieve all time tracking entries logged against a specific project.

List Project Invoices

Tool to retrieve all invoices linked to a specific project with pagination support (30 results per page).

List Projects

Tool to retrieve all projects with pagination support (10 results per page).

List Staff

Tool to retrieve all staff members for an account.

List Tasks

Tool to retrieve all tasks with pagination support (50 results per page).

Send Invoice Message

Tool to send an invoice message to recipients via email.

Update Client

Tool to update an existing client record in Clientary with partial or complete field modifications.

Update Expense

Tool to update an existing expense record in Clientary with partial or complete field modifications.

Update Hour Entry

Tool to modify an existing time entry in Clientary with partial or complete field updates.

Update Project

Tool to update an existing project in Clientary with partial or complete field modifications.

Update Task

Tool to update an existing task in Clientary with partial or complete field modifications.

FAQ

Frequently asked questions

A standalone Clientary MCP server gives Grok Build a fixed set of Clientary tools tied to that one server. The Composio Tool Router lets Grok Build load tools from Clientary and many other apps on demand, based on the task, all through a single endpoint.

Yes. Grok Build ships with native MCP support. Add a server with the grok mcp add command, from the in-session /mcps modal, or by editing ~/.grok/config.toml. It also reads Claude Code-style .mcp.json files, so Grok Build discovers the tools automatically.

Yes. Grok Build has zero-migration compatibility with Claude Code's configuration, so the same Composio server entry works in both without edits.

Tokens, keys, and configuration are encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant, so your Clientary data and credentials are handled to that standard.

Start with Clientary.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Clientary tool your agent needs.Free to start.

Start building