# FlowUs MCP MCP

> FlowUs connects your AI agent directly to a centralized knowledge base. It lets you manage complex documentation, track product databases, and organize team wikis using only natural conversation. Instead of clicking through menus and tabs, your agent talks to FlowUs, instantly listing pages, pulling out content blocks, or creating new records in structured tables.

## Overview
- **Category:** productivity
- **Price:** Free
- **Tags:** wiki, database-management, page-organization, block-editor, team-collaboration, content-management

## Description

Think of it like having an entire company wiki—all the documents, project roadmaps, and databases—but instead of logging into a dozen different tools, you just talk to your AI client. This MCP turns that complex web interface into a conversation. You can ask your agent things like, 'What are all the pages related to Q3 planning?' or 'Give me a list of high-priority features from the Product Backlog.' Your agent handles the deep dive: it reads the page structure, pulls specific content blocks out of documents, and even executes queries across multi-dimensional databases. You don't touch the manual controls; your agent uses this MCP through Vinkius to keep everything organized and instantly accessible.

## Tools

### create_database_row
Adds a brand new record (row) into one of your structured databases.

### create_page
Makes a completely new, blank page within the FlowUs knowledge base.

### get_database
Retrieves the structural schema and field names for any connected database.

### get_page
Pulls all details about a specific, existing page.

### list_blocks
Reads the individual content blocks (text or media) inside a designated page.

### list_databases
Provides an inventory of every database available in your FlowUs workspace.

### list_pages
Generates a list of all pages currently held by the workspace.

### list_users
Returns a directory listing of people who have access to the workspace.

### query_database
Runs complex queries across your databases, returning only the data you need.

### update_page
Modifies content and metadata on an already existing page.

## Prompt Examples

**Prompt:** 
```
List all pages in my FlowUs workspace.
```

**Response:** 
```
I've retrieved your FlowUs pages. You have 6 active pages, including 'Project Roadmap' and 'Meeting Notes'. Which one would you like to view the content for?
```

**Prompt:** 
```
Query the 'Product Backlog' database for items with 'High' priority.
```

**Response:** 
```
I've queried the 'Product Backlog' database. I found 3 items with high priority: 'Refactor Auth Engine', 'Implement PDF Export', and 'API Documentation'. Would you like more details on any of them?
```

**Prompt:** 
```
Add a new row to the 'User Feedback' database with Name='Renato' and Feedback='Love the AI integration!'.
```

**Response:** 
```
Done! I've added your feedback to the 'User Feedback' database. The new entry for Renato has been successfully created.
```

## Capabilities

### List all pages
Gets a list of every page available in your FlowUs workspace.

### Retrieve specific content blocks
Pulls out text and media details from sections within a specific page.

### Query structured data
Finds records in your databases based on complex rules or criteria.

### Create new database entries
Adds a brand new row of information to an existing database table.

### Manage page structure
Creates, reads, or updates entire pages within your knowledge base.

## Use Cases

### The quarterly audit of team documentation
A project manager needs to see if all departments have filled out their Q4 planning pages. Instead of manually checking 20 different folders, they ask their agent to `list_pages` and then check the metadata for completeness.

### Identifying high-priority product bugs
A QA tester needs to know which features are flagged as 'Critical' in the product backlog. They tell their agent to run a query using `query_database` on the relevant table, getting a filtered list immediately.

### Onboarding new team members
A new hire needs an overview of who works on what and what documentation exists. They ask their agent to combine results from `list_pages` and `list_users` for a comprehensive introduction.

## Benefits

- Stop manually listing pages. You can use `list_pages` to get an immediate inventory of your entire documentation site just by asking your agent.
- Don't copy-paste data from complex tables. The MCP lets you run a query using `query_database` and gets the results formatted for instant reading.
- Need to update a document? Use `update_page` directly through chat, rather than navigating into the page editor and manually saving changes.
- Building records is simple. Instead of filling out forms, just tell your agent what you need and let it run `create_database_row` for you.
- When collaborating, use the MCP's ability to list users (`list_users`) so you always know who has access to which sections.

## How It Works

The bottom line is: you talk to your agent, and it uses this MCP to run commands across your entire knowledge base.

1. Subscribe to this MCP and enter your FlowUs API Token.
2. Connect the token to your preferred AI client (like Cursor or Claude).
3. Ask your agent a question in plain language, like 'List all pages related to marketing' to execute actions.

## Frequently Asked Questions

**How do I find out what databases are available using the `list_databases` tool?**
You ask your agent to run the `list_databases` tool. It returns a list of all database names, letting you know exactly which structured data sets FlowUs can talk to.

**Can I update pages using the `update_page` tool?**
Yes. You tell your agent what page ID to target and what new content or metadata should go there. It executes the change, keeping your documentation current in one step.

**What is the difference between `get_database` and `list_databases`?**
`list_databases` gives you a name list of all databases. `get_database`, however, shows the actual structure—the columns and field names—for one specific database.

**How does `query_database` work with my data?**
`query_database` lets you write natural language requests that are turned into structured queries. You don't need SQL; just ask your agent for the data, and it handles the rest.

**What should I use if I need to retrieve all metadata for a specific page, like with the `get_page` tool?**
It pulls all content details and structural data associated with one unique page ID. Use this immediately after creating or finding a page; it's the fastest way to confirm the current state of that document.

**When should I use `list_blocks` instead of calling `get_page`?**
You must call `list_blocks` when you only need a list of content blocks and their types, without retrieving the full text or media data for everything. This is much faster for structural checks.

**What happens if I run `create_database_row` but forget to provide all necessary columns?**
The system will return an error detailing which required column names are missing or formatted incorrectly. Always check the database schema first using the `get_database` tool.

**How does the `list_users` tool help me manage team access and coordination?**
It lists every user currently associated with your FlowUs workspace. You use this to verify who has participation rights or to identify potential collaborators for a project.