← All integrations

ForceManager MCP server

294 operations0 webhooks

Manage Sage Sales Management v4 CRM records, sales resources, activities, products, orders, users, and reference data.

Try ForceManager with your agent

Connect ForceManager, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in ForceManager on my account, then run one read-only example and show me the result.

Runs once, when you ask

ForceManager tools and triggers

Tools are what your agent can do in ForceManager through Corsair's MCP server. Triggers are the ForceManager events a routine can start from.

Orders Entity

  • Create Order HeaderWrite

    Create Order Header (POST /salesorders)

    ordersEntity.createOrderHeader

  • Create Order LineWrite

    Create Order Line (POST /salesOrdersLines)

    ordersEntity.createOrderLine

  • Delete Order HeaderDestructive

    Delete Order Header (DELETE /salesorders/{ID})

    ordersEntity.deleteOrderHeader

  • Delete Order LineDestructive

    Delete Order Line (DELETE /salesordersLines/{ID})

    ordersEntity.deleteOrderLine

  • Get Order HeaderRead-only

    Get Order Header (GET /salesorders/{ID})

    ordersEntity.getOrderHeader

  • Get Order LineRead-only

    Get Order Line (GET /salesordersLines/{ID})

    ordersEntity.getOrderLine

  • List Order HeadersRead-only

    List Order Headers (GET /salesorders)

    ordersEntity.listOrderHeaders

  • List Order LinesRead-only

    List Order Lines (GET /salesordersLines)

    ordersEntity.listOrderLines

  • Order Headers SchemaRead-only

    Order Headers schema (GET /salesorders/schema)

    ordersEntity.orderHeadersSchema

  • Order Lines SchemaRead-only

    Order Lines schema (GET /salesordersLines/schema)

    ordersEntity.orderLinesSchema

  • Update Order HeaderWrite

    Update Order Header (PUT /salesorders/{ID})

    ordersEntity.updateOrderHeader

  • Update Order LineWrite

    Update Order Line (PUT /salesordersLines/{ID})

    ordersEntity.updateOrderLine

Connect ForceManager to Claude, ChatGPT or Cursor

  1. 1

    Connect ForceManager in Corsair

    Add your ForceManager API key once in Corsair. Corsair stores the credential encrypted and makes the ForceManager API calls for your agent, so it never goes into a prompt or a config file. Connect ForceManager

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs ForceManager. On a ChatGPT personal plan, connect ForceManager here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, ForceManager's read and write operations run right away and its 51 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/forcemanager, add the ForceManager plugin, and connect with an API key. Then call methods like corsair.forcemanager.api.accountAddresses.accountAddressesSchema() from your app. Corsair keeps each tenant isolated.

Yes. ForceManager requires an API key from your ForceManager account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit ForceManager, GitHub, Notion, Stripe, and the rest. Trigger ForceManager from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for manage Sage Sales Management v4 CRM records, sales resources, activities, products, orders, users, and reference data. Common builds include sync jobs, admin tooling, and agents that call ForceManager APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per ForceManager API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/forcemanager in the open repo. When ForceManager ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your ForceManager data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store ForceManager data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put ForceManager on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 51 destructive ForceManager operations. You can change a link's mode at hub.corsair.dev/me.