Server Details
Data transformation toolkit — standardize, reshape, and normalize messy data
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
10 toolsdiffInspect
Compare two data files and show what changed (added, removed, modified rows).
| Name | Required | Description | Default |
|---|---|---|---|
| path_after | Yes | Path to transformed file | |
| path_before | Yes | Path to original file |
explain_transformInspect
Describe what a specific transform does, its mode, and input types.
| Name | Required | Description | Default |
|---|---|---|---|
| transform_name | Yes | Name of the transform |
learnInspect
Generate a YAML config from data patterns.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Path to data file |
list_domainsInspect
List available domain packs (e.g., people_hr, ecommerce, finance).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_transformsInspect
List all registered transforms with their modes, input types, and auto-apply status.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
mapInspect
Auto-map schemas between source and target files.
| Name | Required | Description | Default |
|---|---|---|---|
| source | Yes | Source file path | |
| target | Yes | Target file path |
profileInspect
Profile a data file showing column types, nulls, and patterns.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Path to data file |
select_from_findingsInspect
Map GoldenCheck findings to recommended GoldenFlow transforms. Bridge tool for Check-to-Flow handoff.
| Name | Required | Description | Default |
|---|---|---|---|
| findings | Yes | List of GoldenCheck findings (each with 'check' and 'column' fields) |
transformInspect
Transform a data file using GoldenFlow. Zero-config or config-driven.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Path to data file | |
| config | No | Optional YAML config path |
validateInspect
Dry-run transform on a file. Shows what would change without writing output.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Path to data file | |
| config | No | Optional YAML config path |
Verify Ownership
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.
Sign in to verify ownershipControl your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!