Coupler Analytics
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Optional logging level | |
| LOG_STDIO | No | Optional flag to capture STDIO messages in the log file | |
| COUPLER_API_HOST | No | Optional Coupler.io API host URL | https://app.coupler.io/mcp |
| COUPLER_ACCESS_TOKEN | Yes | Your Coupler.io Personal Access Token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-dataA | Get data from a Coupler.io data flow run. Make sure to first query a sample of 5 rows from |
| get-schemaA | Get data table schema from a Coupler.io data flow. Get column names from |
| list-dataflowsA | List my Coupler.io data flows. Use this to get the ID (uuid format) of a data flow by its name. |
| get-dataflowB | Get a Coupler.io data flow by ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: listing flows, getting a specific flow, retrieving schema, and fetching data. No functional overlap exists.
All tool names follow a consistent verb-noun pattern (get-data, get-dataflow, get-schema, list-dataflows) using lowercase with hyphens. Minor variation between 'get' and 'list' but the structure is uniform.
With only 4 tools, the set is well-scoped for exploring and fetching data from Coupler.io data flows. No unnecessary tools, and the count fits the domain.
The set covers the full read workflow: list flows, examine metadata, get schema, retrieve data. Missing CRUD operations (create/update/delete) but that aligns with a read-only analysis tool.