# FutureSense [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/Sams3595/futuresense-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/futuresense

## Description
Invoicing, CRM, accounting, payroll, booking and AI content tools for FutureSense apps.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "futuresense": {
    "command": "npx",
    "args": ["-y","futuresense-mcp"],
    "env": {
      "FUTURESENSE_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `FUTURESENSE_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the FutureSense MCP server does

The FutureSense MCP server gives AI agents access to the FutureSense AI business platform through MCP tools. The README lists 556 tools across 10 application areas, allowing an agent to perform operations in business systems from one server and one API key.

Supported areas include invoicing, payroll, accounting, CRM, booking, content creation, website building, quotations, email, and reports. The available operations range from creating invoices and managing products to running pay runs, maintaining contacts, scheduling appointments, producing content, managing pages, sending transactional email, and generating financial or operational summaries.

The server is suited to workflows that cross application boundaries. For example, an agent can work with quotes and invoices, manage customer or deal records, handle payroll data, or retrieve revenue and expense information through the same FutureSense connection.

## How it works

The package runs as an MCP server and exposes FutureSense platform operations as callable tools. Clients start it with `npx`, while the API credential is passed through the `FUTURESENSE_API_KEY` environment variable. The README describes the connection as using a single API key for the platform’s app domains.

The documented configuration uses a server entry named `futuresense`, the `npx -y futuresense-mcp` command, and an environment block containing the API key. It is intended for Claude, Cursor, ChatGPT, Gemini, and other MCP-compatible clients.

## Setup and configuration

Install the package with:

```bash
npm install futuresense-mcp
```

A client configuration can start the server without a separate executable path:

```json
{
  "mcpServers": {
    "futuresense": {
      "command": "npx",
      "args": ["-y", "futuresense-mcp"],
      "env": {
        "FUTURESENSE_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}
```

Obtain the API key from the FutureSense hub at `hub.futuresenseai.com`. The provided setup is a local stdio-style configuration; the README does not document additional configuration variables or deployment modes.

## Tools and capabilities

The FutureSense MCP server groups its tools into these domains:

- Invoicing: 103 tools for invoices, products, expenses, bank reconciliation, taxes, credit notes, deposits, and receipts.
- Payroll: 68 tools for employees, pay runs, deductions, and payslips.
- Accounting: 72 tools for accounts, journals, profit and loss reports, balance sheets, and tax filing.
- CRM: 58 tools for contacts, email campaigns, pipelines, and deals.
- Booking: 47 tools for appointments, reminders, and payments.
- Content creation: 44 tools for content, assets, and publishing workflows.
- Website builder: 39 tools for pages, layouts, and components.
- Quotations: 35 tools for quotes, approvals, and conversion to invoices.
- Email: 52 tools for transactional messages, templates, and open tracking.
- Reports: 38 tools for KPI snapshots, revenue, and expense summaries.

## Limitations and notes

Access depends on a valid FutureSense API key, and the README does not specify the permissions model, rate limits, error behavior, or individual tool schemas. The listed tool count and app coverage come from the project documentation and may change as the npm package is updated. Confirm the current package and platform behavior before relying on particular operations in production. The project is released under the MIT license.

_Full upstream README: https://allmcps.com/mcp/futuresense/readme_