# How to integrate Forcemanager MCP with Mastra AI ```json { "title": "How to integrate Forcemanager MCP with Mastra AI", "toolkit": "Forcemanager", "toolkit_slug": "forcemanager", "framework": "Mastra AI", "framework_slug": "mastra-ai", "url": "https://composio.dev/toolkits/forcemanager/framework/mastra-ai", "markdown_url": "https://composio.dev/toolkits/forcemanager/framework/mastra-ai.md", "updated_at": "2026-05-12T10:12:04.404Z" } ``` ## Introduction This guide walks you through connecting Forcemanager to Mastra AI using the Composio tool router. By the end, you'll have a working Forcemanager agent that can delete a contact by their id, get details for a specific sales order, retrieve company info using company id through natural language commands. This guide will help you understand how to give your Mastra AI agent real control over a Forcemanager account through Composio's Forcemanager MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Forcemanager with - [OpenAI Agents SDK](https://composio.dev/toolkits/forcemanager/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/forcemanager/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/forcemanager/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/forcemanager/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/forcemanager/framework/codex) - [OpenClaw](https://composio.dev/toolkits/forcemanager/framework/openclaw) - [Hermes](https://composio.dev/toolkits/forcemanager/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/forcemanager/framework/cli) - [Google ADK](https://composio.dev/toolkits/forcemanager/framework/google-adk) - [LangChain](https://composio.dev/toolkits/forcemanager/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/forcemanager/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/forcemanager/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/forcemanager/framework/crew-ai) ## TL;DR Here's what you'll learn: - Set up your environment so Mastra, OpenAI, and Composio work together - Create a Tool Router session in Composio that exposes Forcemanager tools - Connect Mastra's MCP client to the Composio generated MCP URL - Fetch Forcemanager tool definitions and attach them as a toolset - Build a Mastra agent that can reason, call tools, and return structured results - Run an interactive CLI where you can chat with your Forcemanager agent ## What is Mastra AI? Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP. Key features include: - MCP Client: Built-in support for Model Context Protocol servers - Toolsets: Organize tools into logical groups - Step Callbacks: Monitor and debug agent execution - OpenAI Integration: Works with OpenAI models via @ai-sdk/openai ## What is the Forcemanager MCP server, and what's possible with it? The Forcemanager MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Forcemanager account. It provides structured and secure access to your CRM data, so your agent can perform actions like retrieving activity details, managing companies and contacts, and organizing sales orders on your behalf. - Activity management and retrieval: Instantly fetch specific sales activities or remove outdated ones, helping you keep your team's daily records up to date. - Company and contact administration: Easily get detailed company or contact information, or delete records when they're no longer needed—all with your agent's help. - Sales order and line control: Let your agent delete sales orders or individual order lines, streamlining your sales workflow and keeping data clean. - Master data maintenance: Empower your agent to manage master-data values, ensuring your CRM stays accurate and relevant as your business evolves. - Saved view organization: Ask your agent to delete saved views you no longer use, keeping your workspace focused and clutter-free. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `FORCEMANAGER_DELETE_ACTIVITY` | Delete Activity | Delete an existing activity by ID. Tries multiple base hosts and path variants to maximize compatibility across environments and gateways. | | `FORCEMANAGER_DELETE_COMPANY` | Delete Company | Tool to delete a company by its ForceManager ID. Use when you need to remove an existing company from the system. | | `FORCEMANAGER_DELETE_CONTACT` | Delete Contact | Permanently deletes a contact from ForceManager by its unique ID. This action removes the specified contact and all associated data. The operation is irreversible. The action automatically tries multiple API endpoint combinations to ensure compatibility across different ForceManager deployments and configurations. Returns the HTTP status code and any response message from the API. A successful deletion typically returns a 200 status code. | | `FORCEMANAGER_DELETE_SALES_ORDER` | Delete Sales Order | Delete a sales order by ID using ForceManager REST API. Tries multiple base hosts and path variants to maximize compatibility across environments. Accepts successful HTTP status codes (< 300) even when the response is non-JSON, capturing response text. | | `FORCEMANAGER_DELETE_SALES_ORDER_LINE` | Delete Sales Order Line | Delete a sales order line by ID. Attempts deletion across multiple ForceManager API hosts and path variations to ensure compatibility. Returns detailed information about the deletion result, including any messages or status codes from the API. Use this when you need to remove a specific sales order line item from the system. | | `FORCEMANAGER_DELETE_VALUE` | Delete Master Data Value | Delete a master-data value (Z_ table) by ID using ForceManager REST API. Tries multiple base hosts and path variants to maximize compatibility across environments. Accepts successful HTTP status codes (< 300) even when the response is HTML instead of JSON, capturing the response text as a message. Also retries sending authentication headers as query parameters on HTTP 401 as some gateways expect them in query string. | | `FORCEMANAGER_DELETE_VIEW` | Delete View | Delete a saved view (custom filter) by its ID. Views in ForceManager are saved filter configurations that users create to quickly access filtered lists of entities (accounts, activities, opportunities, etc.). This action permanently removes a view that the authenticated user has permission to delete. **Use Cases:** - Remove outdated or unused custom filters - Clean up views after organizational changes - Programmatically manage view lifecycle **Requirements:** - Valid view ID that exists in the system - Appropriate permissions to delete the view - The view must be owned by or shared with the authenticated user **Note:** This action tries multiple ForceManager API endpoints to maximize compatibility across different deployment environments and API versions. | | `FORCEMANAGER_GET_ACTIVITY` | Get Activity | Retrieves a single activity by its ID from ForceManager CRM. Use this tool when you need to: - Fetch details of a specific activity by its ID - Check if an activity exists - Retrieve activity data including comments, dates, linked contacts/accounts, and location info The action attempts multiple ForceManager API endpoints to ensure compatibility across different API versions and deployment configurations. Returns found=False if the activity does not exist or cannot be retrieved. Authentication is handled automatically via headers from the connected account. | | `FORCEMANAGER_GET_COMPANY` | Get Company | Retrieve a single company by its ID from ForceManager. Returns company details when found, or an empty entity with found=False when the company doesn't exist or the API returns non-JSON content. The action automatically tries multiple ForceManager API endpoints for maximum compatibility. Use this to fetch company information including name, address, contact details, and custom fields. Check the 'found' field to determine if the company exists. | | `FORCEMANAGER_GET_INTERNAL_ID` | Get Internal ID | Tool to retrieve ForceManager internal IDs mapping for a given externalId and entity type. This action calls the documented endpoint /api/internalid with required authentication headers and optional pagination/version headers. It tries multiple base hosts to avoid HTML app shell responses and gracefully handles non-JSON responses and error codes by returning empty results instead of failing the execution. | | `FORCEMANAGER_GET_PRODUCT` | Get Product | Retrieve a single product by its ID from ForceManager/Sage Sales Management. This action tries multiple known ForceManager API endpoints in sequence until one succeeds. If a product is not found or the API returns non-JSON content, it returns found=False with an empty entity dict. This graceful handling allows agents to check for product existence without encountering errors. Use this when you need to fetch product details such as name, price, cost, category, or custom fields by product ID. | | `FORCEMANAGER_GET_SALES_ORDER_LINE` | Get Sales Order Line | Retrieves a single sales order line by ID from ForceManager. A sales order line represents a product item within a sales order, including quantity, pricing, and discount information. Use this when you need to fetch details about a specific line item in a sales order, such as product information, quantities, prices, or applied discounts. | | `FORCEMANAGER_GET_USER` | Get User | Retrieves a single ForceManager user by their ID, returning comprehensive user information including name, email, phone, active status, permission level, manager, branches, and more. Returns the complete user object if found, or an empty entity with found=False if the user doesn't exist, was deleted, or the API returns an error. Automatically tries multiple ForceManager API endpoints and versions to ensure compatibility. Use this when you need to: fetch user profile details, verify user existence, check user permissions/status, or retrieve user contact information. | | `FORCEMANAGER_GET_VIEW` | Get View | Tool to get a single view by ID. Returns a list with zero or one view object. | | `FORCEMANAGER_LIST_VIEWS` | List Views | Tool to list saved view filters. Use when you need to retrieve saved views for a specific entity (e.g., list views for entity 'account'). | | `FORCEMANAGER_UPDATE_ACTIVITY` | Update Activity | Tool to update an existing activity by ID. Use when you need to change fields such as comment, date/time, linked entities, or geocode. | | `FORCEMANAGER_UPDATE_COMPANY` | Update Company | Update Company | | `FORCEMANAGER_UPDATE_PRODUCT` | Update Product | Updates an existing product by ID in ForceManager. Use this tool to modify product details such as name, price, cost, description, availability status, category, family, discount limits, and custom fields. The product must already exist - this action does not create new products. At least one field besides 'id' must be provided to update. | | `FORCEMANAGER_UPDATE_SALES_ORDER` | Update Sales Order | Update Sales Order | | `FORCEMANAGER_UPDATE_SALES_ORDER_LINE` | Update Sales Order Line | Tool to update sales order line by ID. Use when modifying details of an existing sales order line. Retries with query auth on 401 for proxy-pro host. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Forcemanager MCP server is an implementation of the Model Context Protocol that connects your AI agent to Forcemanager. It provides structured and secure access so your agent can perform Forcemanager operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before starting, make sure you have: - Node.js 18 or higher - A Composio account with an active API key - An OpenAI API key - Basic familiarity with TypeScript ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. - You need credits or a connected billing setup to use the models. - Store the key somewhere safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Go to Settings and copy your API key. - This key lets your Mastra agent talk to Composio and reach Forcemanager through MCP. ### 2. Install dependencies Install the required packages. What's happening: - @composio/core is the Composio SDK for creating MCP sessions - @mastra/core provides the Agent class - @mastra/mcp is Mastra's MCP client - @ai-sdk/openai is the model wrapper for OpenAI - dotenv loads environment variables from .env ```bash npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's happening: - COMPOSIO_API_KEY authenticates your requests to Composio - COMPOSIO_USER_ID tells Composio which user this session belongs to - OPENAI_API_KEY lets the Mastra agent call OpenAI models ```bash COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here OPENAI_API_KEY=your_openai_api_key_here ``` ### 4. Import libraries and validate environment What's happening: - dotenv/config auto loads your .env so process.env.* is available - openai gives you a Mastra compatible model wrapper - Agent is the Mastra agent that will call tools and produce answers - MCPClient connects Mastra to your Composio MCP server - Composio is used to create a Tool Router session ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Agent } from "@mastra/core/agent"; import { MCPClient } from "@mastra/mcp"; import { Composio } from "@composio/core"; import * as readline from "readline"; import type { AiMessageType } from "@mastra/core/agent"; const openaiAPIKey = process.env.OPENAI_API_KEY; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey as string, }); ``` ### 5. Create a Tool Router session for Forcemanager What's happening: - create spins up a short-lived MCP HTTP endpoint for this user - The toolkits array contains "forcemanager" for Forcemanager access - session.mcp.url is the MCP URL that Mastra's MCPClient will connect to ```typescript async function main() { const session = await composio.create( composioUserID as string, { toolkits: ["forcemanager"], }, ); const composioMCPUrl = session.mcp.url; console.log("Forcemanager MCP URL:", composioMCPUrl); ``` ### 6. Configure Mastra MCP client and fetch tools What's happening: - MCPClient takes an id for this client and a list of MCP servers - The headers property includes the x-api-key for authentication - getTools fetches the tool definitions exposed by the Forcemanager toolkit ```typescript const mcpClient = new MCPClient({ id: composioUserID as string, servers: { nasdaq: { url: new URL(composioMCPUrl), requestInit: { headers: session.mcp.headers, }, }, }, timeout: 30_000, }); console.log("Fetching MCP tools from Composio..."); const composioTools = await mcpClient.getTools(); console.log("Number of tools:", Object.keys(composioTools).length); ``` ### 7. Create the Mastra agent What's happening: - Agent is the core Mastra agent - name is just an identifier for logging and debugging - instructions guide the agent to use tools instead of only answering in natural language - model uses openai("gpt-5") to configure the underlying LLM ```typescript const agent = new Agent({ name: "forcemanager-mastra-agent", instructions: "You are an AI agent with Forcemanager tools via Composio.", model: "openai/gpt-5", }); ``` ### 8. Set up interactive chat interface What's happening: - messages keeps the full conversation history in Mastra's expected format - agent.generate runs the agent with conversation history and Forcemanager toolsets - maxSteps limits how many tool calls the agent can take in a single run - onStepFinish is a hook that prints intermediate steps for debugging ```typescript let messages: AiMessageType[] = []; console.log("Chat started! Type 'exit' or 'quit' to end.\n"); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); rl.on("line", async (userInput: string) => { const trimmedInput = userInput.trim(); if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } messages.push({ id: crypto.randomUUID(), role: "user", content: trimmedInput, }); console.log("\nAgent is thinking...\n"); try { const response = await agent.generate(messages, { toolsets: { forcemanager: composioTools, }, maxSteps: 8, }); const { text } = response; if (text && text.trim().length > 0) { console.log(`Agent: ${text}\n`); messages.push({ id: crypto.randomUUID(), role: "assistant", content: text, }); } } catch (error) { console.error("\nError:", error); } rl.prompt(); }); rl.on("close", async () => { console.log("\nSession ended."); await mcpClient.disconnect(); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Complete Code ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Agent } from "@mastra/core/agent"; import { MCPClient } from "@mastra/mcp"; import { Composio } from "@composio/core"; import * as readline from "readline"; import type { AiMessageType } from "@mastra/core/agent"; const openaiAPIKey = process.env.OPENAI_API_KEY; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey as string }); async function main() { const session = await composio.create(composioUserID as string, { toolkits: ["forcemanager"], }); const composioMCPUrl = session.mcp.url; const mcpClient = new MCPClient({ id: composioUserID as string, servers: { forcemanager: { url: new URL(composioMCPUrl), requestInit: { headers: session.mcp.headers, }, }, }, timeout: 30_000, }); const composioTools = await mcpClient.getTools(); const agent = new Agent({ name: "forcemanager-mastra-agent", instructions: "You are an AI agent with Forcemanager tools via Composio.", model: "openai/gpt-5", }); let messages: AiMessageType[] = []; const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); rl.on("line", async (input: string) => { const trimmed = input.trim(); if (["exit", "quit"].includes(trimmed.toLowerCase())) { rl.close(); return; } messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed }); const { text } = await agent.generate(messages, { toolsets: { forcemanager: composioTools }, maxSteps: 8, }); if (text) { console.log(`Agent: ${text}\n`); messages.push({ id: crypto.randomUUID(), role: "assistant", content: text }); } rl.prompt(); }); rl.on("close", async () => { await mcpClient.disconnect(); process.exit(0); }); } main(); ``` ## Conclusion You've built a Mastra AI agent that can interact with Forcemanager through Composio's Tool Router. You can extend this further by: - Adding other toolkits like Gmail, Slack, or GitHub - Building a web-based chat interface around this agent - Using multiple MCP endpoints to enable cross-app workflows ## How to build Forcemanager MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/forcemanager/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/forcemanager/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/forcemanager/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/forcemanager/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/forcemanager/framework/codex) - [OpenClaw](https://composio.dev/toolkits/forcemanager/framework/openclaw) - [Hermes](https://composio.dev/toolkits/forcemanager/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/forcemanager/framework/cli) - [Google ADK](https://composio.dev/toolkits/forcemanager/framework/google-adk) - [LangChain](https://composio.dev/toolkits/forcemanager/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/forcemanager/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/forcemanager/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/forcemanager/framework/crew-ai) ## Related Toolkits - [Hubspot](https://composio.dev/toolkits/hubspot) - HubSpot is an all-in-one marketing, sales, and customer service platform. It lets teams nurture leads, automate outreach, and track every customer interaction in one place. - [Pipedrive](https://composio.dev/toolkits/pipedrive) - Pipedrive is a sales management platform offering pipeline visualization, lead tracking, and workflow automation. It helps sales teams keep deals moving forward efficiently and never miss a follow-up. - [Salesforce](https://composio.dev/toolkits/salesforce) - Salesforce is a leading CRM platform that helps businesses manage sales, service, and marketing. It centralizes customer data, enabling teams to drive growth and build strong relationships. - [Apollo](https://composio.dev/toolkits/apollo) - Apollo is a CRM and lead generation platform that helps businesses discover contacts and manage sales pipelines. Use it to streamline customer outreach and track your deals from one place. - [Attio](https://composio.dev/toolkits/attio) - Attio is a customizable CRM and workspace for managing your team's relationships and workflows. It helps teams organize contacts, automate tasks, and collaborate more efficiently. - [Acculynx](https://composio.dev/toolkits/acculynx) - AccuLynx is a cloud-based roofing business management software for contractors. It streamlines project tracking, lead management, and document sharing. - [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time. - [Affinity](https://composio.dev/toolkits/affinity) - Affinity is a relationship intelligence CRM that helps private capital investors find, manage, and close more deals. It streamlines deal flow and surfaces key connections to help you win opportunities. - [Agencyzoom](https://composio.dev/toolkits/agencyzoom) - AgencyZoom is a sales and performance platform built for P&C insurance agencies. It helps agents boost sales, retain clients, and analyze producer results in one place. - [Bettercontact](https://composio.dev/toolkits/bettercontact) - Bettercontact is a smart contact enrichment tool for finding emails and phone numbers. It helps boost lead generation with automated, waterfall search across multiple sources. - [Blackbaud](https://composio.dev/toolkits/blackbaud) - Blackbaud provides cloud-based software for nonprofits, schools, and healthcare institutions. It streamlines fundraising, donor management, and mission-driven operations. - [Brilliant directories](https://composio.dev/toolkits/brilliant_directories) - Brilliant Directories is an all-in-one platform for building and managing online membership communities and business directories. It streamlines listings, member management, and engagement tools into a single, easy interface. - [Capsule crm](https://composio.dev/toolkits/capsule_crm) - Capsule CRM is a user-friendly CRM platform for managing contacts and sales pipelines. It helps businesses organize relationships and streamline their sales process efficiently. - [Centralstationcrm](https://composio.dev/toolkits/centralstationcrm) - CentralStationCRM is an easy-to-use CRM software focused on collaboration and long-term customer relationships. It helps teams manage contacts, deals, and communications all in one place. - [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time. - [Close](https://composio.dev/toolkits/close) - Close is a CRM platform built for sales teams, combining calling, email automation, and predictive dialers. It streamlines sales workflows and boosts productivity with all-in-one communication tools. - [Dropcontact](https://composio.dev/toolkits/dropcontact) - Dropcontact is a B2B email finder and data enrichment service for professionals. It delivers verified email addresses and enriches contact info with up-to-date data. - [Dynamics365](https://composio.dev/toolkits/dynamics365) - Dynamics 365 is Microsoft's platform combining CRM, ERP, and productivity apps. It streamlines sales, marketing, service, and operations in one place. - [Espocrm](https://composio.dev/toolkits/espocrm) - EspoCRM is an open-source web application for managing customer relationships. It helps businesses organize contacts, track leads, and streamline their sales process. - [Fireberry](https://composio.dev/toolkits/fireberry) - Fireberry is a CRM platform that streamlines customer and sales management. It helps businesses organize contacts, automate sales, and integrate with other business tools. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Forcemanager MCP? With a standalone Forcemanager MCP server, the agents and LLMs can only access a fixed set of Forcemanager tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Forcemanager and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Mastra AI? Yes, you can. Mastra AI 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 Forcemanager tools. ### Can I manage the permissions and scopes for Forcemanager while using Tool Router? Yes, absolutely. You can configure which Forcemanager 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 Forcemanager data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)