What are the required credentials to run the server?
You need your Flowcore username and a Personal Access Token (PAT). These can be passed as `--username` and `--pat` arguments or set as environment variables `USERNAME` and `PAT`.
@flowcore-io
Basic information
MCP server for managing and interacting with Flowcore Platform
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"mcp-flowcore-platform": {
"command": "npx",
"args": [
"@flowcore/platform-mcp-server",
"--username",
"<username>",
"--pat",
"<pat>"
]
}
}
}Get a tenant
Get a data core
Get a flow type
Get an event type
List all tenants I have access to
List all data cores for a tenant
List all flow types for a data core
List all event types for a flow type
Get event information about an event type, like first and last time bucket and 5 example events. Sensitive data should not be needed as it is masked in a correct format in the response, but if you need it ask the user if they are sure they want to include sensitive data, is **false** by default. **DO NOT** fetch sensitive data from the event type on your own initiative, if you deem it necessary to fetch sensitive data, **ALWAYS** ask the user if they are sure they want to include sensitive data, is **false** by default
Get events for an event type, this can be paginated by using the cursor returned from the previous call. This is good for getting the payload of the events to inspect them. You can pageinate by using the cursor returned from the previous call. You can also filter by event id, time bucket, from event id, to event id, order, and page size. The order is ascending by default, and the page size is 500 by default. The cursor returned can be called nextCursor, it is a stringified object or a string, you need to pass it as is to paginate. Sensitive data should not be needed as it is masked in a correct format in the response, but if you need it ask the user if they are sure they want to include sensitive data, is **false** by default. **DO NOT** fetch sensitive data from the event type on your own initiative, if you deem it necessary to fetch sensitive data, **ALWAYS** ask the user if they are sure they want to include sensitive data, is **false** by default
Get time buckets for an event type, this is useful for getting the time buckets for an event type, and then using the get_events tool to get the events for a specific time bucket. The time bucket is in the format of YYYYMMDDhhiiss, normally the ii and ss are 0000. It can be paginated by using the cursor returned from the previous call.
Create a data core in a tenant
Update a data core
Update a flow type
Update an event type
Create a flow type in a data core
Create an event type in a flow type
Request to delete an event type, this will delete all events in the event type, this is irreversible. If wait for delete is true the tool will wait up to 25 seconds for the event type to be deleted, if not it will return immediately, you have to use the get_event_type tool to check if the event type is deleted.
Request to truncate an event type, this will delete all events in the event type, this is irreversible. If wait for truncate is true the tool will wait up to 25 seconds for the event type to be truncated, if not it will return immediately, you have to use the get_event_type tool to check if the event type is truncated.
Request to delete a flow type, this will delete all events in the flow type, this is irreversible. If wait for delete is true the tool will wait up to 25 seconds for the flow type to be deleted, if not it will return immediately, you have to use the get_flow_type tool to check if the flow type is deleted.
Request to delete a data core, this will delete all events in the data core, this is irreversible. If wait for delete is true the tool will wait up to 25 seconds for the data core to be deleted, if not it will return immediately, you have to use the get_data_core tool to check if the data core is deleted.
A Model Context Protocol (MCP) server for managing and interacting with the Flowcore Platform. It provides a standardized interface that allows AI assistants to query and manage Flowcore resources through a structured API. The server is built with Bun and can be run via npx or globally installed.
Run directly using npx without installation: npx @flowcore/platform-mcp-server --username <username> --pat <pat>. Alternatively, install globally with npm install -g @flowcore/platform-mcp-server and then run platform-mcp-server --username <username> --pat <pat>. Replace <username> and <pat> with your Flowcore username and Personal Access Token. Environment variables USERNAME and PAT can also be used instead of command-line arguments.
You need your Flowcore username and a Personal Access Token (PAT). These can be passed as `--username` and `--pat` arguments or set as environment variables `USERNAME` and `PAT`.
Use `npx @flowcore/platform-mcp-server --username <username> --pat <pat>` to execute the server directly without any installation.
Yes, the README recommends checking out the [local read model MCP server](https://github.com/flowcore-io/mcp-flowcore-local-readmodel) to reduce hallucinations, token usage, and speed up querying, especially when handling large amounts of data.
Join the Flowcore Discord community at https://discord.gg/4fmSaR4wFR for questions and ideas. A demonstration video is also available on YouTube.
The server is built and tested with Bun (v1.2.3 or later). For development, you need Bun installed; for production use, you can run via npx or the built Node.js compatible output.
Hindsight: Agent Memory That Learns

A free remote MCP server for The Living Bread. Bible passages read word for word from a stored public domain text with an evidence label, keyword search and cross references, real churches, gatherings and prayer groups w
๐ The fast, Pythonic way to build MCP servers and clients.
MCP Toolbox for Databases is an open source MCP server for databases.

A good sequence diagram can solve almost any communication problem in engineering. Volley lets your agent write them as plain text, with the real request and response payloads on every arrow. It checks its own syntax wi
Comments