Flotiq

@Flotiq search for all blog posts published in the last 30 days that mention 'product launch' and return their titles, authors, and publish dates

Found 12 blog posts matching your criteria. The most recent is 'Q1 Product Launch Recap' by Sarah Chen (published March 15), followed by 'Behind the Scenes: Launch Day Prep' by Marcus Liu (March 8), and 'Customer Reactions to Our Latest Release' by Sarah Chen (March 3). The full list includes posts from the marketing, product, and customer success teams. Each result includes the post slug, featured image reference, and tag associations for further filtering.

This example uses Flotiq's full-text search across a custom 'blogPost' content type. The MCP returns structured data from your Flotiq schema—field names and relationships depend on how you've defined that content type. Search respects the API key's read permissions; private content types won't appear in results.

@Flotiq create a new product entry with name 'Wireless Charger Pro', SKU 'WCP-2024', price 49.99, and category 'accessories'

Created product object WCP-2024 in Flotiq. The new entry includes: name set to 'Wireless Charger Pro', SKU 'WCP-2024', price $49.99, category linked to your 'accessories' content type, and auto-generated fields (creation timestamp, internal ID). The object is now live and queryable via your Flotiq API. Note that this assumes a 'product' content type exists in your schema with fields matching these names—if field definitions differ, you'll receive a validation error listing required or mismatched fields.

This write operation requires your Flotiq content type schema to include the specified fields (name, SKU, price, category). Validation happens server-side; the MCP will surface any schema mismatches before committing. The API key must have write permissions on the target content type. Side-effect: the new object is immediately visible to all API consumers.

@Flotiq list all 'teamMember' objects, expand their 'department' relationships, then draft a company directory grouped by department with each person's role and contact email

Retrieved 47 team members across 6 departments. Engineering (18 members) includes roles from Junior Developer to VP Engineering; Marketing (12 members) spans Content Writer to CMO; Sales (9 members) includes SDRs and Account Executives. Each record includes the person's full name, title, work email, and department metadata (department name, head count, office location). A formatted directory might group these as: **Engineering** – Alice Johnson (VP Engineering, alice@company.com), Bob Smith (Senior Developer, bob@company.com)… and so on for each department. The relationship expansion pulls department details without additional queries.

This synthesis example combines Flotiq's list and relationship-expansion features with the AI's formatting logic. The 'expand' parameter fetches linked content type data in one call, avoiding N+1 queries. Output structure depends entirely on your Flotiq schema—'teamMember' and 'department' are illustrative content type names. Rate limits apply to list operations returning large result sets.

When Flotiq wins for headless product data at small scale

A 3-person Shopify store team managing 200 SKUs across multiple channels needs a single source of truth for product descriptions, specs, and imagery. Flotiq's batch upsert tool lets you push catalog updates from a spreadsheet or PIM into structured content types, then pull that data into Shopify, your marketing site, and email campaigns via the search and list endpoints. The API-key auth means any team member can run the sync from a Switchy chat without OAuth friction. This works cleanly up to about 5,000 objects; beyond that, you'll want a dedicated integration layer because the 100-object batch limit starts to feel slow. If your catalog changes daily and you need sub-second sync, look elsewhere. But for weekly catalog refreshes and multi-channel consistency, Flotiq gives you structured content without a CMS learning curve.

Flotiq as a lightweight docs backend for support teams

A 6-person support team writes help articles in Notion but needs them searchable on the public site and inside the app. Flotiq's content type system lets you define an 'article' schema with title, body, category, and tags, then use the create and update tools to push finished drafts from Switchy into production. The full-text search tool powers the in-app help widget, and the list endpoint feeds the marketing site's help index. The 60-day soft-delete window gives you a safety net if someone accidentally removes a critical article. This setup breaks down if you need versioning or approval workflows—Flotiq doesn't track content history natively. But for a small team publishing 10-20 articles a month with straightforward taxonomy, it's faster than Contentful and cheaper than a headless CMS with enterprise features you won't use.

When Flotiq handles multi-source event data for small conferences

A 4-person conference team collects registrations from Eventbrite, Luma, and a custom form, then needs a unified view for badge printing and session planning. Flotiq's batch upsert tool normalizes attendee records into a single content type, and the search endpoint lets you filter by ticket tier, dietary restrictions, or session interest during standup. The get and list tools pull subsets for vendor handoffs without exposing the full dataset. This works for conferences under 1,000 attendees where real-time sync isn't critical—batch imports run every few hours, not every minute. If you need live seat counts or complex multi-step registration flows, you'll outgrow this quickly. But for annual or quarterly events where you're wrangling CSVs from three platforms into one planning doc, Flotiq gives you structured storage and query without building a custom database.