Flotiq MCP. Manage CMS content and media assets via your agent.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Flotiq MCP Server lets you manage your headless CMS and structured content directly from your AI client. You can create new content objects, update existing records, audit schemas, and check tenant usage limits—all via natural conversation.
It gives your agent full control over content types, media assets, and API-first data delivery.
What your AI agents can do
Create cms object
Writes a new content record into the CMS using a structured JSON payload.
Get content details
Retrieves detailed logging and content information for a specific content ID.
Get content type schema
Gets the exact structural definition for a specific content type.
Build new content records or modify existing ones by providing a JSON payload to the CMS.
Fetch detailed logging and content information for a specific content ID.
Get the exact structural definition (JSON schema) for any content type to validate data models.
List all available content types or list specific content objects within a defined space.
Run a global search query across the entire content corpus, regardless of content type.
List and inspect properties for media assets stored in your tenant environment.
Audit your current tenant quotas, including identity and content type limits.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Flotiq MCP Server: 10 Tools for Content & Media Ops
These tools allow your AI agent to manage the entire content lifecycle in Flotiq, from schema validation to global content search.
019d759bcreate cms object
Writes a new content record into the CMS using a structured JSON payload.
019d759bget content details
Retrieves detailed logging and content information for a specific content ID.
019d759bget content type schema
Gets the exact structural definition for a specific content type.
019d759bget tenant limits
Identifies your current usage quotas and limits across the CMS.
019d759blist all content types
Lists every content type available in the CMS.
019d759blist content objects
Identifies and lists all available content objects in a defined CMS space.
019d759blist media assets
Lists media assets and extracts properties related to their usage limits.
019d759bpatch cms object
Modifies an existing content object by safely substituting its attributes.
019d759bsearch global content
Runs a search query across all content records to find matches based on keywords.
019d759bwipe cms object
Permanently and irreversibly deletes a content record from the CMS.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Flotiq, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Flotiq MCP Server gives your AI client full control over your headless CMS. You can build and modify content records, check usage limits, and audit schemas—all through natural conversation. When you connect your agent, it gets full control over content types, media assets, and API-first data delivery.
To manage content, your agent can use create_cms_object to write a new record using a structured JSON payload, or patch_cms_object to modify an existing one by safely substituting its attributes. If you need to wipe a record, wipe_cms_object permanently deletes a content record.
To find specific content, your agent can run get_content_details to fetch detailed logging and content information for a content ID, or use search_global_content to run a search query across all content records based on keywords. You can also list all content types using list_all_content_types, or check all content objects in a specific space with list_content_objects.
When you're auditing the structure, get_content_type_schema gives you the exact structural definition for a content type, and you can use list_media_assets to list media assets and extract properties related to their usage limits. You can check your system quotas by running get_tenant_limits to identify current usage limits across the CMS.
If you need to manage media, list_media_assets lets you inspect properties for media assets stored in your tenant environment.
How Flotiq MCP Works
- 1 Subscribe to the Flotiq server and provide your API Key (find it in your Flotiq Dashboard > API Keys).
- 2 Tell your AI agent what you need to do—for example, 'List all blog posts' or 'Get the schema for the product type'.
- 3 The agent runs the appropriate tool, and you get the structured data payload back.
The bottom line is, your AI client talks to Flotiq via the server, and you get back structured content data.
Who Is Flotiq MCP For?
This is for developers and content ops teams who need API-first control over their CMS. If you're tired of clicking through a visual editor to test data models or update content, this lets you manage everything through code and chat. You're the person who needs to validate a schema before a feature launches.
Tests API-first content models, verifies schema mappings, and debugs data flows directly from the IDE.
Creates and updates content objects and manages media assets without opening the Flotiq web editor.
Monitors tenant limits, verifies content type definitions, and checks global content status using natural language conversation.
Searches across global content and manages media libraries without needing to navigate complex internal dashboards.
What Changes When You Connect
- Write directly to the CMS: Use
create_cms_objectto provision content records with a JSON payload. You bypass the web UI and treat the CMS like a pure API. - Validate data models instantly: Run
get_content_type_schemato get the exact JSON structure for any content type. This lets you ensure your data payload matches the target schema before writing. - Audit usage limits: Call
get_tenant_limitsto see exactly how many content objects or media assets you're using. No more surprises hitting a quota wall. - Search everywhere: Use
search_global_contentto query content across the entire site, not just the section you're currently viewing. This gives you a true global view. - Handle updates and deletes: Use
patch_cms_objectto safely change attributes on an existing record, orwipe_cms_objectif you need to permanently remove a piece of content. - Inspect media: Use
list_media_assetsto get properties and check limits for all your media uploads, keeping asset management centralized.
Real-World Use Cases
Product Team needs a schema check.
The PM needs to know if the 'product' content type accepts a 'weight' field. They run get_content_type_schema against the 'product' type. The agent returns the full JSON schema, confirming the field and its required data type, letting the PM proceed with confidence.
Developer needs to seed test data.
A developer needs 5 test blog posts for a new feature branch. They use list_content_objects to see the 'blogpost' space, then loop create_cms_object five times with dummy data. This process is repeatable and keeps the feature branch clean.
Marketer needs to find old content.
A marketer needs to find an article about 'AI work' published last year. They run search_global_content with the query. The agent returns a list of IDs and snippets, allowing the marketer to quickly locate the content regardless of which content type it belongs to.
Ops Engineer needs to check quotas.
The ops engineer notices the site is slow and suspects a quota issue. They run get_tenant_limits and get a synchronous report on their remaining identity and content type quotas, confirming the problem is not capacity.
The Tradeoffs
Trying to list everything at once
Running list_content_objects without telling the agent which content type or space to check, expecting a single massive list of millions of items.
→
Always specify the scope. First, use list_all_content_types to see what's available. Then, use list_content_objects with the specific content type ID to get a paginated list of records.
Guessing the data structure
Manually writing a JSON payload for create_cms_object based on old documentation, only to find the required field name changed.
→
Never guess. Always run get_content_type_schema first. This gives you the exact, current JSON structure needed for create_cms_object.
Accidentally deleting data
Relying on the web UI's 'delete' button, which might not log the action or might fail silently, leading to data gaps that are hard to trace.
→
Use the explicit wipe_cms_object tool. It performs an irreversible deletion and drops the live database bytes, ensuring the action is logged and accounted for.
When It Fits, When It Doesn't
Use this server if your workflow requires managing structured content via API calls. You need the ability to validate schemas (get_content_type_schema), create records (create_cms_object), and monitor capacity (get_tenant_limits) without using a GUI. Don't use this if your primary task is simple content viewing or simple text editing—use a standard CMS client instead. If you only need to read data and never write, get_content_details and search_global_content cover most needs. If you only need to see what's available, list_all_content_types is enough. You need the full stack of write/read/audit tools for this server to be necessary.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Flotiq. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manually checking content status across different tools is a headache.
Today, if you need to check if a content object is ready to publish, you have to jump between the content editor, the media asset library, and the analytics dashboard. You check the status in one place, then copy the ID, paste it into a different tool to check the schema, then open a third tab to see if the media assets are linked correctly. It's a copy-paste nightmare.
With the Flotiq MCP Server, your agent handles the whole sequence. You just ask: 'What's the status of the product page for ID 456?' The agent calls `get_content_details`, then checks `list_media_assets` and validates the schema using `get_content_type_schema`. You get the complete, validated answer in one chat response.
Flotiq MCP Server: Manage content objects and media assets.
Before, updating content meant clicking through multiple forms: one for the body copy, one for the related images, and a third to confirm the content type was still active. It was slow, and you often missed a required field.
Now, you just tell your agent, 'Update the product description for ID 123, and attach the new image from the asset library.' The agent handles the payload creation, the update via `patch_cms_object`, and the asset linking—all in a single, reliable flow.
Common Questions About Flotiq MCP
How do I use the `get_content_type_schema` tool with Flotiq? +
You provide the content type name to the agent. The tool returns the exact JSON structure, listing all required fields and their data types. This is crucial because you need this schema to successfully use create_cms_object.
Can `list_content_objects` handle millions of records? +
The tool is designed to work with bounded spaces. You must specify the content type or space ID to prevent the agent from attempting an unmanageable query. Always confirm the scope first.
Is `wipe_cms_object` safe to use? +
Use it only when you are absolutely sure you want the content gone. It permanently deletes the record and drops the database bytes; there is no undo.
What is the difference between `list_content_objects` and `search_global_content`? +
list_content_objects shows every record within a known, defined space. search_global_content runs a keyword search across the entire CMS, finding relevant content regardless of its primary type.
How do I check my quota using the `get_tenant_limits` tool? +
The get_tenant_limits tool shows your current usage against defined quotas. It returns precise arrays detailing remaining identity limits and base endpoint availability, so you know exactly where you stand.
What happens if I try to update a record that doesn't exist using `patch_cms_object`? +
The patch_cms_object tool handles non-existent nodes gracefully. It will return a specific error code and message indicating the ID is missing, allowing your agent to retry with corrected data.
Can I use `create_cms_object` for content types that are not explicitly listed? +
No, the create_cms_object tool requires a valid content type ID. You must first run list_all_content_types to get the correct type vector before attempting to provision a new object.
Does `get_content_details` provide enough information to rebuild a complex object? +
Yes, get_content_details retrieves explicit Cloud logging traces for a given Payload ID. This trace includes all necessary structural fields and relationships needed to recreate or verify the object's state.
Can my agent list all available content types in Flotiq? +
Yes. Use the 'list_all_content_types' tool. The agent executes bulk iterations to track explicitly registered types and returns the mapping configured in your Flotiq architecture.
How do I create a new content object using a JSON payload via chat? +
Use the 'create_cms_object' tool. Provide the 'content_type' and your 'payload_json'. The agent will command the backend to persist the new node utilizing your schema constraints flawlessly.
Can I search across all my global content through the agent? +
Absolutely. Use the 'search_global_content' tool. Your agent will execute immediate queries across all content by tapping raw status configurations and searching Elastic/Graph limits natively.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Moonscan (Moonbeam Network Explorer)
Access Moonbeam blockchain data via Moonscan — check GLMR balances, track transactions, and inspect smart contracts directly from any AI agent.
Dev.to (Forem)
Manage Dev.to and Forem articles — list posts, create content, and inspect user profiles directly from any AI agent.
Numeral Formatter Engine
Format raw numbers into perfect display strings: currencies ($10,000.00), bytes (2.5MB), percentages (97%), and abbreviations (1.5k).
You might also like
Dada Now Delivery
Bring Dada Now's Instant Local Delivery API to your LLM. Schedule swift deliveries, manage your stores, and calculate routing fees.
HubSpot Marketing Hub
Manage marketing emails, forms, contact lists, campaigns, and landing pages through natural conversation.
Sumo Logic
Connect your AI to Sumo Logic. Orchestrate log searches, monitor active collectors, and analyze system events efficiently.