Fireberry
Fireberry is a CRM platform that offers integrations with various tools and applications to streamline business processes.
Verdict
Common use cases
- Log sales calls directly from chat
- Update deal stages during pipeline reviews
- Pull customer history before support calls
- Check valid picklist options before creating records
- Query overdue tasks across all modules
Integration
- Vendor
- Fireberry
- Category
- crm
- Auth
- API_KEY
- Tools
- 3
- Composio slug
fireberry
Tools
- Create a new Fireberry record
Tool to create a new record in a specified fireberry table. use when you have the table name and record data ready for insertion.
- Fireberry: Query Records
Tool to query records with filtering, sorting, and pagination. use when you need to retrieve specific fireberry records by module.
- Get Picklist Values
Tool to retrieve all possible picklist (dropdown) values for a specific field. use when you need to load all available options for a picklist field in a record type.
Setup
Setup guide
- 1Open your Switchy workspace and navigate to Settings > Integrations. Click Add Integration and select Fireberry from the CRM category. You'll be prompted to enter your Fireberry API key — generate one by logging into Fireberry, going to Settings > API Access, and creating a new key with read and write permissions for the modules you want to access. Paste the key into Switchy and click Connect. Switchy will verify the key and confirm which modules are accessible. To test the connection, open any Space and type '@Fireberry query records in Contacts module' — if the MCP returns a list of contacts, you're ready. Use '@Fireberry' at the start of any message to invoke its tools inside a Space.
What teammates see: by default, memories from Fireberry are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Log New Contact
@Fireberry create a new contact record in the Contacts table with the name 'Alex Chen', email 'alex@example.com', and phone '+1-555-0199'.Open in a Space →
Find Open Deals
@Fireberry query records in the Deals module where status is 'Open', sorted by expected close date ascending.Open in a Space →
Check Lead Sources
@Fireberry get all picklist values for the 'Lead Source' field in the Leads module so I can pick the right option.Open in a Space →
Update Account Owner
@Fireberry create a task record in the Tasks table with subject 'Reassign Account Owner', due date tomorrow, and assigned to user ID 'U12345'.Open in a Space →
Pull Recent Activity
@Fireberry query records in the Activities module where contact ID is 'C67890', sorted by activity date descending, limit 10 results.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@fireberry show me all leads created in the last 7 days, sorted by estimated deal value
Based on the query, Fireberry returned 12 leads from the past week. The top three by estimated value are: Acme Corp ($45K, created 2 days ago, status: Qualified), TechStart Inc ($38K, created 5 days ago, status: New), and Global Solutions ($32K, created yesterday, status: In Discussion). All leads are currently assigned to the sales team with follow-up tasks scheduled. This is an illustrative example showing how the MCP structures filtered query results.
This example uses the Query Records tool with date filtering and sorting parameters. Note that field names and available filters depend on your Fireberry instance configuration. The MCP requires read permissions on the Leads module, and results are paginated if your query returns more than the default limit.
@fireberry create a new contact record for Sarah Chen at DataFlow Systems, email sarah.chen@dataflow.io, phone +1-555-0199
Successfully created contact record in Fireberry. The new contact 'Sarah Chen' has been added to the Contacts module with ID #C-2847. Email and phone fields are populated as specified. The record is set to default status 'Active' and assigned to your user account. Company association with 'DataFlow Systems' was automatically linked based on the company name match in your CRM. This illustrative example shows the confirmation structure after record creation.
This example demonstrates the Create Record tool, which requires write permissions on the Contacts module. The MCP validates required fields before submission, but you'll need to check your Fireberry instance for mandatory custom fields. Side-effect: this creates a permanent record that counts toward your Fireberry storage limits.
@fireberry what are the valid status options for opportunity records, then summarize which statuses indicate we should follow up this week
Fireberry picklist values for Opportunity Status: New, Qualified, Proposal Sent, Negotiation, Closed Won, Closed Lost, On Hold. Based on these options, you should prioritize follow-ups for opportunities in 'Proposal Sent' and 'Negotiation' statuses this week—these represent active deals requiring immediate attention. 'Qualified' opportunities are also worth reviewing to move them forward. 'On Hold' may need re-engagement depending on hold reasons. This illustrative example shows how picklist data combines with AI reasoning.
This example pairs the Get Picklist Values tool with AI synthesis to provide actionable guidance. Picklist options are instance-specific and may include custom values your team has configured. The AI's interpretation of 'follow up this week' is contextual—adjust based on your actual sales cycle and team priorities.
Use-case deep-dives
When Fireberry MCP saves reps from tab-switching mid-call
A 6-person sales team runs discovery calls in Zoom and logs notes in Fireberry. Without the MCP, reps alt-tab to the CRM mid-call or reconstruct details afterward from memory. With Switchy's Fireberry integration, the AI assistant creates contact records and logs call summaries in real time while the rep stays in the conversation. The query tool pulls existing account context before the call starts, and the picklist tool ensures deal stages and lead sources match your CRM's dropdown values exactly. This works best for teams closing 10-30 deals per month where call quality matters more than CRM speed. If your reps close 100+ deals monthly, they likely need dedicated CRM automation beyond what an AI workspace provides. For small teams where every conversation counts, Fireberry MCP turns Switchy into a CRM copilot that doesn't interrupt the human work.
How Fireberry MCP routes support cases without Zapier
A 4-person support team uses Fireberry to track customer issues and escalations. Tickets arrive via email, Slack, and a help widget, but routing decisions require context the CRM already holds: account tier, open case count, last contact date. The Fireberry MCP lets Switchy query customer records mid-triage, check if an account has three open P1 cases, and create a new escalation record with the correct priority picklist value in one step. This replaces a Zapier chain that cost $50/month and broke whenever Fireberry's field names changed. The trade-off: if your support volume exceeds 200 tickets per week, you need a dedicated helpdesk tool with SLA automation, not a CRM query layer. For small teams handling 30-80 tickets weekly, Fireberry MCP gives your AI workspace enough CRM reach to make smart routing calls without leaving the conversation.
When Fireberry MCP pulls deal data for exec reviews
A 3-person leadership team reviews pipeline health every quarter. The VP of Sales needs a snapshot of deals by stage, rep, and close date, but Fireberry's native reporting requires clicking through five screens and exporting CSVs. With the Fireberry MCP in Switchy, the exec asks the AI to query all deals closing this quarter, filter by stage, and summarize rep performance in a shared workspace thread. The query tool handles filtering and sorting; the create tool logs follow-up actions directly into Fireberry as new tasks. This works when your pipeline has 20-100 active deals and you review monthly or quarterly. If you're managing 500+ deals or need daily dashboards, invest in a BI tool that syncs Fireberry data overnight. For small teams where pipeline reviews happen in conversation, not dashboards, Fireberry MCP turns Switchy into a live CRM query layer that answers exec questions in seconds.
Frequently asked
What does the Fireberry MCP do in Switchy?
It lets your team create, query, and update CRM records in Fireberry directly from Switchy chat. You can filter contacts by status, add new deals with the correct picklist values, or pull account data without switching tabs. The MCP handles table lookups and field validation so you don't need to remember Fireberry's schema.
Do I need admin access to connect Fireberry?
You need a Fireberry API key, which typically requires admin or developer permissions in your Fireberry account. Standard users can't generate API keys. Once connected, the MCP inherits whatever data access that key has — if the key can see all modules, Switchy can too.
Can the Fireberry MCP update existing records or only create new ones?
The current toolset focuses on creating new records and querying existing ones. If you need to update a record, you'll query it first to get the ID, then use Fireberry's web UI or API directly. The MCP doesn't expose a dedicated update tool yet.
How is this different from just using Fireberry's web app?
You stay in Switchy chat instead of context-switching to Fireberry's UI. The MCP is faster for bulk lookups or when you're already drafting a message and need to check a contact's status. For complex workflows or custom views, Fireberry's native interface still wins.
Who on the team should connect the Fireberry integration?
Whoever owns your Fireberry API keys — usually a CRM admin or ops lead. They connect it once in Switchy, and the whole workspace can use it. Individual users don't need separate Fireberry logins. Just make sure the API key has access to the modules your team actually queries.