About flowcore/mcp-flowcore-platform
flowcore/mcp-flowcore-platform is an MCP server published by flowcore-io in the Data category: mCP server for managing and interacting with Flowcore Platform.
The repository has 9 stars and 6 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.
Install
git clone https://github.com/flowcore-io/mcp-flowcore-platformThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Tools (22)
create_data_coreCreate a data core in a tenant
Parameters not published.
create_event_typeCreate an event type in a flow type
Parameters not published.
create_flow_typeCreate a flow type in a data core
Parameters not published.
get_data_coreGet a data core
Parameters not published.
get_event_typeGet an event type
Parameters not published.
get_event_type_infoGet 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
Parameters not published.
get_eventsGet 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
Parameters not published.
get_flow_typeGet a flow type
Parameters not published.
get_tenantGet a tenant
Parameters not published.
get_time_bucketsGet 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.
Parameters not published.
Show all 22 tools
ingestIngest events into an event type. This is useful for ingesting events into an event type, and then using the get_events tool to get the events for a specific time bucket. The events are stored in time buckets, and can be fetched by using the get_time_buckets tool. When you fetch events from a time bucket, you can use the cursor to paginate through the events. When ingesting events, you can only ingest a stringified JSON array of events. **max 25 events per request**
Parameters not published.
list_data_coresList all data cores for a tenant
Parameters not published.
list_event_typesList all event types for a flow type
Parameters not published.
list_flow_typesList all flow types for a data core
Parameters not published.
list_tenantsList all tenants I have access to
Parameters not published.
request_delete_data_coreRequest 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.
Parameters not published.
request_delete_event_typeRequest 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.
Parameters not published.
request_delete_flow_typeRequest 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.
Parameters not published.
request_truncate_event_typeRequest 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.
Parameters not published.
update_data_coreUpdate a data core
Parameters not published.
update_event_typeUpdate an event type
Parameters not published.
update_flow_typeUpdate a flow type
Parameters not published.
Ask AI
Ask AI about flowcore/mcp-flowcore-platform
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 9 hours ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- !License declaredNo license file. Legally you have no right to use it in a product.
- !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
Releases
README
Flowcore Platform MCP Server
A Model Context Protocol (MCP) server for managing and interacting with the Flowcore Platform.
If you're curious about how it works, you can check out our video, where we set it up and demonstrate what it can do.
If you like this solution, but would like to reduce the hallucinations, reduce token usage, increase the amount of data you can look through and also speed up querying exponentially - then we recommend you also check out our local read model mcp server,
Usage with npx
You can run this package directly using npx without installing it:
npx @flowcore/platform-mcp-server --username <username> --pat <pat>
Replace <username> and <pat> with your Flowcore username and PAT (Personal Access Token).
Installation
If you prefer to install the package globally:
npm install -g @flowcore/platform-mcp-server
Then run it:
platform-mcp-server --username <username> --pat <pat>
Development
To install dependencies:
bun install
Run the project directly with Bun:
bun run src/index.ts --username <username> --pat <pat>
Building
Build the project:
bun run build
Run the built project:
node dist/cli.js --username <username> --pat <pat>
Environment Variables
| Variable | Type | Description | Default | Required |
|---|---|---|---|---|
| USERNAME | string | Flowcore username | - | ✓ |
| PAT | string | Flowcore PAT (Personal Access Token) | - | ✓ |
About
This project uses the Model Context Protocol (MCP) to provide a standardized interface for interacting with the Flowcore Platform. It allows AI assistants to query and manage Flowcore resources through a structured API.
Originally created using bun init in bun v1.2.3. Bun is a fast all-in-one JavaScript runtime.
Questions
if you have any questions or cool ideas, then feel free to join our Discord community. Otherwise you can find us on all major social platforms
README fetched from the repository 9 hours ago. The original is authoritative.