Skip to main content
Room MCP gives you programmatic access to the contents of a room. Unlike Agent MCP — which talks to a single deployed agent — Room MCP lets you enumerate a room’s workflows and their feature views, then download the underlying data as Parquet. This is ideal for pulling Corvic-processed data into your own data stack, notebooks, or downstream pipelines.

Endpoint and credentials

Never hard-code your access token. Load it from an environment variable or secrets manager, and keep it out of source control.

Room MCP tools

In the API, workflows are identified as data apps (list_data_apps, data_app_id). These map to the Workflows you build on the canvas.

Prerequisites

Install the MCP and HTTP client libraries:

Example

This script connects to Room MCP, lists the workflows in a room, lists a workflow’s feature views, and downloads a feature view’s Parquet payload.

How it works

1

Connect

Open a streamable_http_client to the MCP URL with your Bearer token, then start a ClientSession and call initialize().
2

List workflows

Call list_data_apps with the room_id (paginate with entries_per_page and cursor).
3

List feature views

Pick a data_app_id from the result and call list_feature_views. Each feature view includes a Parquet url.
4

Download the data

Fetch the feature view’s url with the same authenticated HTTP client to get the raw Parquet bytes.

MCP Overview

Agent vs. room access and credentials.

Agent MCP

Talk to a deployed agent instead.

Workflows

Build the pipelines exposed here.

Corvic Tables

Understand feature views and tables.