How to integrate Firmao MCP with Claude Code

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Firmao logo
Claude Code logo
divider

Introduction

Manage your Firmao directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Firmao with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • 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.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Firmao to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

Supported Tools & Triggers

Tools
Create InvoiceCreates a new sales or purchase invoice in Firmao CRM.
Delete Company SettingDeletes a company setting by its unique identifier.
Delete ContactSoft-deletes a contact in Firmao CRM by marking it as deleted (sets deleted=true).
Delete InvoiceSoft-deletes a Firmao invoice by marking it as deleted.
Delete OfferSoft-delete an offer in Firmao by marking it as deleted.
Get InvoiceRetrieve detailed information about a specific invoice by its ID.
Get OfferRetrieve detailed information about a specific offer from Firmao CRM by its unique ID.
Get TaskRetrieves detailed information about a specific task by its unique ID.
List Company SettingsLists all company settings from Firmao.
List InvoicesTool to list invoices.
List TasksRetrieves a paginated list of tasks from Firmao.
Update Contact in FirmaoUpdates an existing contact in Firmao CRM by its ID.
Update OfferUpdates an existing offer/quote in Firmao by ID.
Update TaskTool to update an existing task.

What is the Firmao MCP server, and what's possible with it?

The Firmao MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Firmao account. It provides structured and secure access to your business data, so your agent can perform actions like retrieving invoices, managing offers, handling tasks, and updating company settings on your behalf.

  • Invoice management and automation: Let your agent create new invoices, retrieve detailed invoice data, list all invoices, or delete invoices as needed—all without manual entry.
  • Offer tracking and updates: Effortlessly get the details of any offer, or have your agent delete offers that are no longer relevant to your business pipeline.
  • Task and contact handling: Fetch specific task details or manage your contact list, including the ability to remove outdated or incorrect contacts with ease.
  • Company configuration oversight: List and review your company’s settings or delete obsolete company configurations—helping you keep your business data clean and up to date.

Connecting Firmao via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Firmao) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Firmao account
  • Basic knowledge of Python or TypeScript

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["firmao"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http firmao-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Create a script to generate a Composio MCP URL for Firmao. This URL will be used to connect Claude Code to Firmao.

What's happening:
  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Firmao
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output

Add Firmao MCP to Claude Code

bash
claude mcp add --transport http firmao-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (firmao-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

Verify the installation

bash
claude mcp list

Check that your Firmao MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your firmao-composio entry in the list
  • This confirms that Claude Code can now access Firmao tools

If everything is wired up, you should see your firmao-composio entry listed:

Claude Code MCP list showing the toolkit MCP server

Authenticate Firmao

The first time you try to use Firmao tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Firmao
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Firmao authorization flow
  • Return to the terminal and start using Firmao through Claude Code

Once authenticated, you can ask Claude Code to perform Firmao operations in natural language. For example:

  • "List all invoices created this month"
  • "Get details for invoice ID 12345"
  • "Delete a contact named John Doe"

Complete Code

Here's the complete code to get you started with Firmao and Claude Code:

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["firmao"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http firmao-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Conclusion

You've successfully integrated Firmao with Claude Code using Composio's MCP server. Now you can interact with Firmao directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Firmao operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Firmao operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

How to build Firmao MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Firmao MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Firmao MCP with Claude Agent SDK

Claude Cowork logo

Claude Cowork

Use Firmao MCP with Claude Cowork

Codex logo

Codex

Use Firmao MCP with Codex

OpenClaw logo

OpenClaw

Use Firmao MCP with OpenClaw

Hermes logo

Hermes

Use Firmao MCP with Hermes

CLI logo

CLI

Use Firmao MCP with CLI

Google ADK logo

Google ADK

Use Firmao MCP with Google ADK

LangChain logo

LangChain

Use Firmao MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Firmao MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Firmao MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Firmao MCP with LlamaIndex

CrewAI logo

CrewAI

Use Firmao MCP with CrewAI

FAQ

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

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

Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude 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 Firmao tools.

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

Yes, absolutely. You can configure which Firmao 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 Firmao 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.

Get started for freeGet a demo↗