How to connect Clientary MCP with VS Code

Trusted by teams at
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Clientary logo
VS Code logo
divider

How to connect Clientary MCP with VS Code

VS Code is the most popular code editor out there. With its recent AI makeover, it can do more than just help you write code. You can connect your applications to it and let LLMs automate many of the mundane tasks in your workflow.

In this guide, I will explain how to connect Clientary with VS Code in the most secure and robust way possible via Composio.

Also integrate Clientary with

Why use Composio?

Composio provides:

  • Access to 1,000+ managed apps from a single MCP endpoint. This makes it convenient for agents to run cross-app workflows.
  • Programmatic tool calling. Allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool response handling outside the LLM context. This minimizes context bloat from large tool responses.
  • Dynamic just-in-time access to thousands of tools across hundreds of apps. Composio loads the tools your agent needs, so LLMs are not overwhelmed by tools they do not need.

Integrate Clientary MCP with VS Code

1. Install with one click

Click the button below to add Composio to VS Code. You will be prompted to authorize. This requires VS Code 1.99+ with GitHub Copilot.

+Install in VS Code

2. Or add manually

Open or create .vscode/mcp.json in your project root and add the following configuration:

bash
{
  "servers": {
    "composio": {
      "type": "http",
      "url": "https://connect.composio.dev/mcp"
    }
  }
}

3. Authorize

Click the install button to authorize VS Code to connect to Composio. VS Code will detect OAuth and prompt you to sign in.

VS Code MCP server install screen for Composio

A browser window will open to authorize.

Composio authorization browser window

4. Authenticate Clientary and start working

Back in VS Code chat, ask the agent to connect to Clientary or give it any Clientary-related task.

For example, ask it to:

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

It will prompt you to authenticate and authorize access to Clientary.

That is it. Composio tools are now available in VS Code, and your Clientary account is ready to use.

Supported Tools & Triggers

Tools
Create ClientTool to create a new client record in Clientary.
Create ContactTool to create a new contact within a specified client.
Create ExpenseTool to create a new expense record in Clientary to track expenditures within your account.
Create LeadTool to create a new lead record in Clientary.
Create ProjectTool to create a new project in Clientary with name and rate.
Create TaskTool to create a new task in Clientary.
Delete ClientTool to remove a client and all associated projects, invoices, estimates, and contacts.
Delete LeadTool to permanently delete a lead and all associated Estimates and Contacts.
Delete PaymentTool to remove an existing payment from an invoice.
Delete Payment ProfileTool to remove a specific payment profile from a client's account.
Delete Recurring ScheduleTool to remove a recurring schedule by its identifier.
Get ClientTool to fetch details for a specific client using its ID.
Get ContactTool to retrieve a single contact by its ID.
Get EstimateTool to retrieve details for a single estimate by ID.
Get ExpenseTool to retrieve details for a single expense record in Clientary.
Get Hour EntryTool to obtain details about a specific time entry in Clientary.
Get InvoiceTool to retrieve detailed information for a specific invoice by ID.
Get LeadTool to retrieve a single lead by its ID.
Get ProjectTool to retrieve a single project by its identifier.
Get StaffTool to retrieve a single staff member by their ID.
Get TaskTool to retrieve a specific task by its ID.
List Client ContactsTool to retrieve all contacts for a specific client with pagination support.
List Client ExpensesTool to retrieve all expenses for a specific client within an optional date range.
List Client InvoicesTool to retrieve all invoices for a specific client with pagination support (30 results per page).
List Client ProjectsTool to retrieve all projects associated with a specific client with pagination support (10 results per page).
List ClientsTool to retrieve all clients with pagination support (10 results per page).
List ExpensesTool to retrieve expenses by date range (defaults to current fiscal year).
List LeadsTool to retrieve all leads with pagination support.
List PaymentsTool to retrieve all payments with pagination support (30 results per page).
List Project EstimatesTool to retrieve estimates scoped to a particular project with pagination support (30 results per page).
List Project ExpensesTool to retrieve all expenses for a specific project within an optional date range.
List Project HoursTool to retrieve all time tracking entries logged against a specific project.
List Project InvoicesTool to retrieve all invoices linked to a specific project with pagination support (30 results per page).
List ProjectsTool to retrieve all projects with pagination support (10 results per page).
List StaffTool to retrieve all staff members for an account.
List TasksTool to retrieve all tasks with pagination support (50 results per page).
Send Invoice MessageTool to send an invoice message to recipients via email.
Update ClientTool to update an existing client record in Clientary with partial or complete field modifications.
Update ExpenseTool to update an existing expense record in Clientary with partial or complete field modifications.
Update Hour EntryTool to modify an existing time entry in Clientary with partial or complete field updates.
Update ProjectTool to update an existing project in Clientary with partial or complete field modifications.
Update TaskTool to update an existing task in Clientary with partial or complete field modifications.

Way Forward

Now that Clientary is connected, extend your setup by connecting the other apps you already use every day, so your agent can run true cross-app workflows end to end.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.
  • Connect HubSpot or Salesforce to log customer context, update records, and draft follow-ups.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single MCP endpoint, your agent can coordinate multiple tools safely and reliably in one conversation.

How to build Clientary MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Clientary MCP?

With a standalone Clientary MCP server, the agents and LLMs can only access a fixed set of Clientary tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Clientary and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with VS Code?

Yes, you can. VS Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Clientary tools.

Can I manage the permissions and scopes for Clientary while using Tool Router?

Yes, absolutely. You can configure which Clientary scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Clientary data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.