Skip to main content
Glama
TheOctMind

Super Fireberry MCP

by TheOctMind
README.md
# Super Fireberry MCP

<p align="center">
  <img src="https://img.shields.io/badge/Fireberry-CRM-orange?style=flat-square&logo=fireberry" alt="Fireberry Logo" />
  <img src="https://img.shields.io/badge/Model_Context_Protocol-SDK-blue?style=flat-square" alt="MCP Logo" />
</p>

<p align="center">
  <a href="https://github.com/TheOctMind/super-fireberry-mcp/actions"><img src="https://img.shields.io/github/actions/workflow/status/TheOctMind/super-fireberry-mcp/build.yml?branch=master&style=flat-square" alt="Build Status" /></a>
  <a href="https://opensource.org/licenses/MIT"><img src="https://img.shields.io/badge/License-MIT-green.svg?style=flat-square" alt="License" /></a>
  <a href="https://github.com/prettier/prettier"><img src="https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square" alt="Prettier" /></a>
  <a href="https://www.typescriptlang.org/"><img src="https://img.shields.io/badge/TypeScript-5.0+-blue?style=flat-square&logo=typescript" alt="TypeScript" /></a>
</p>

---

## Overview

Super Fireberry MCP is a production-grade implementation of the Model Context Protocol (MCP) specifically engineered for Fireberry CRM. It provides a high-fidelity interface for Large Language Models (LLMs) to interact with CRM data using natural language.

This server acts as an intelligent middleware, abstracting the complexities of the Fireberry REST API into a set of powerful, self-documenting tools.

## Architecture

The project is built on a modular service-oriented architecture, ensuring high performance and type safety.

```mermaid
graph TD
    A[LLM / Claude] -->|MCP Protocol| B[Super Fireberry Server]
    B -->|Normalization Layer| C[API Service]
    C -->|Authenticated REST| D[Fireberry CRM API]
    D -->|JSON Response| C
    C -->|Typed Objects| B
    B -->|Structured Output| A
```

### Key Components
- **Normalization Service**: Maps human-readable entity names to internal system codes.
- **Query Engine**: Translates natural language intent into structured Fireberry Query API payloads.
- **Batch Handler**: Manages high-volume data operations with efficient error recovery.

## Features

- **Full Metadata Reflection**: Zero-config support for custom objects and fields.
- **Power Query**: Advanced filtering (logical AND/OR), sorting, and deep pagination.
- **Financial Integration**: Native support for Invoices, Receipts, and Transaction Items.
- **Batch Processing**: High-throughput creation and updates for enterprise data loads.
- **Relationship Intelligence**: Navigate complex record hierarchies effortlessly.

## Toolset

| Tool | Capability | Typical Use Case |
| :--- | :--- | :--- |
| `get_objects` | System Discovery | "What modules are available?" |
| `get_fields` | Schema Inspection | "What are the fields for 'Projects'?" |
| `query` | Advanced Search | "Find all leads from LinkedIn with status 'New'." |
| `manage_record` | Full CRUD | "Update the status of Account #105 to 'Active'." |
| `get_related_records`| Hierarchy Traversal | "Get all tasks linked to this contact." |

## Installation & Setup

### Prerequisites
- Node.js v18.0.0 or higher
- A valid Fireberry API Access Token

### Local Setup
```bash
git clone https://github.com/TheOctMind/super-fireberry-mcp.git
cd super-fireberry-mcp
npm install
npm run build
```

## Integration

### Claude Desktop Configuration
Add the following entry to your `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "super-fireberry": {
      "command": "node",
      "args": ["/absolute/path/to/super-fireberry-mcp/build/index.js"],
      "env": {
        "FIREBERRY_TOKEN_ID": "YOUR_API_TOKEN"
      }
    }
  }
}
```

## Roadmap

- **v1.1**: Direct file attachment streaming.
- **v1.2**: Webhook integration for real-time notifications.
- **v2.0**: Native support for Fireberry Workflow execution.

## Contributing

We welcome contributions! Please see our [Contributing Guidelines](CONTRIBUTING.md) for more details.

## License

This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.

---
<p align="center">
  Built for the Fireberry Ecosystem
</p>

TDQS

A3.7/5.0

Scored across 5 tools

Disambiguation5/5

Each tool addresses a clearly distinct layer: object metadata, field metadata, record search, record mutations, and relationship traversal. Even though query and get_related_records both return records, their purposes are separated by general filtered search versus direct linked-record navigation.

Naming Consistency3/5

The get_objects, get_fields, and get_related_records tools follow a consistent get_ prefix, but query is a bare noun/verb and manage_record uses a generic 'manage' verb. The naming is readable but mixes conventions rather than following a uniform verb_noun pattern.

Tool Count5/5

Five tools is a well-scoped count for a CRM MCP server. Each tool covers a major capability—discovery, metadata, search, mutations, and relationships—without unnecessary fragmentation or overwhelming breadth.

Completeness4/5

The tool set covers metadata discovery, record creation/updating/deletion, complex search, and relationship traversal, which covers core CRM workflows. Minor gaps exist, such as no explicit single-record fetch and no relationship mutation tools, but query and manage_record can likely work around these.

Maintenance

ActivityInactive
ResponsivenessNo issues