Coupler.io official MCP server

Name: Coupler.io official MCP server
Author: railsware

@railsware

代码仓库

关于 Coupler.io official MCP server

Coupler.io MCP server

#coupler-io #mcp-server #data-integration

基本信息

分类

其他

许可证

MIT license

运行时

node

传输方式

stdio

发布者

railsware

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "coupler": {
      "command": "docker",
      "args": [
        "run",
        "--pull=always",
        "-e",
        "COUPLER_ACCESS_TOKEN",
        "--rm",
        "-i",
        "ghcr.io/railsware/coupler-io-mcp-server"
      ],
      "env": {
        "COUPLER_ACCESS_TOKEN": "<your_token>"
      }
    }
  }
}

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Coupler.io official MCP server?

The Coupler.io official MCP server is a Model Context Protocol (MCP) server that provides seamless integration with Coupler.io APIs. It is designed for users who need to extract and analyze data from Coupler.io data flows, and is currently in early alpha with incomplete features and subject to breaking changes.

How to use Coupler.io official MCP server?

Run the server in a Docker container using a Coupler.io Personal Access Token. Configure it in Claude Desktop by adding a JSON entry to mcpServers with the Docker command and the COUPLER_ACCESS_TOKEN environment variable.

Key features of Coupler.io official MCP server

Extract data from Coupler.io data flows as SQLite files.
Execute read‑only queries on extracted data flow results.
Retrieve data flow schema files.
Run entirely in a Docker container with STDIO transport.
Authenticate via a Personal Access Token.

Use cases of Coupler.io official MCP server

Analyzing data from Coupler.io data flows by running SQL queries.
Inspecting data flow schemas for validation or debugging.
Automating data extraction from dashboard or dataset template flows.

FAQ from Coupler.io official MCP server

What tools does the server provide?

It provides two tools: get-data (queries a data flow result as a SQLite file) and get-schema (retrieves the data flow schema file). Both require a dataflowId and executionId.