MCP.so
ログイン

MCP Server Trello

@MCP-Mirror

基本情報

カテゴリ

その他

ライセンス

MIT license

トランスポート

stdio

作者

MCP-Mirror

MCP Server Trello について

Mirror of

MCP Server Trello の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "trello": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-trello"
      ],
      "env": {
        "TRELLO_API_KEY": "",
        "TRELLO_TOKEN": "",
        "TRELLO_BOARD_ID": ""
      }
    }
  }
}

MCP Server Trello のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is MCP Server Trello?

MCP Server Trello is a Model Context Protocol (MCP) server that provides tools for interacting with Trello boards. It handles rate limiting, type safety, and error handling automatically, and is intended for developers using MCP-enabled applications.

How to use MCP Server Trello?

Install via npm: npm install @modelcontextprotocol/mcp-server-trello. Configure in your MCP settings file with the required environment variables TRELLO_API_KEY, TRELLO_TOKEN, and TRELLO_BOARD_ID. The server exposes tools like get_cards_by_list_id, get_lists, get_recent_activity, add_card_to_list, update_card_details, archive_card, add_list_to_board, archive_list, and get_my_cards.

Key features of MCP Server Trello

  • Full Trello board integration: cards, lists, board activities
  • Built-in rate limiting respecting Trello’s API limits
  • Type-safe implementation in TypeScript
  • Input validation for all API inputs
  • Graceful error handling with informative messages

Use cases of MCP Server Trello

  • Automate card creation and updates across Trello lists
  • Retrieve and display board activity for reporting
  • Move or archive cards and lists based on triggers
  • Fetch all cards assigned to the current user

よくある質問

1

What environment variables are required?

`TRELLO_API_KEY` (from https://trello.com/app-key), `TRELLO_TOKEN` (generate using your API key), and `TRELLO_BOARD_ID` (found in the board URL).

2

How does rate limiting work?

The server uses a token bucket algorithm to comply with Trello’s limits: 300 requests per 10 seconds per API key and 100 requests per 10 seconds per token. Requests are queued if limits are reached.

3

What runtime dependencies are needed?

Node.js 16 or higher and npm or yarn.

4

What transport or authentication does the server use?

It uses Trello’s REST API with an API key and token provided via environment variables. The MCP transport is handled by the Model Context Protocol SDK.

5

Are there any known limitations?

The server requires a single board ID; it does not support switching boards dynamically. Rate limits are enforced automatically.

コメント

「その他」の他のコンテンツ