Super Fireberry MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIREBERRY_TOKEN_ID | Yes | Your Fireberry API Access Token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_objectsA | Discover all available CRM modules and custom objects. Use this first to understand the system structure. |
| get_fieldsA | Retrieve detailed field definitions for any object. Essential before creating or updating records to know which fields exist. |
| queryC | Execute complex search queries with logical filters. Supports pageNumber, pageSize, and filter strings (e.g., 'accountname contains "test"'). |
| manage_recordA | Create, Update, or Delete CRM records. For 'update', recordId is mandatory. For 'create', include the data object with field values. |
| get_related_recordsA | Fetch records linked to a specific entity. Useful for traversing relationships like Contacts under an Account. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
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.
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.