Trello MCP Server
# Trello MCP Server
TrelloのAPIと連携するMCP（Model Context Protocol）サーバーです。
## セットアップ
### 1. 依存関係のインストール
```bash
npm install
```
### 2. ビルド
```bash
npm run build
```
### 3. Trello API認証情報の取得
1. [Trello Developer Portal](https://trello.com/app-key) にアクセスしてAPI Keyを取得
2. 同じページでTokenを生成
### 4. 環境変数の設定
以下の環境変数を設定してください：
- `TRELLO_API_KEY`: TrelloのAPI Key
- `TRELLO_TOKEN`: Trelloのアクセストークン
## Cursor/Claudeでの設定
`~/.cursor/mcp.json` (または該当する設定ファイル) に以下を追加：
```json
{
"mcpServers": {
"trello": {
"command": "node",
"args": ["C:\\Users\\hirok\\Documents\\MCPs\\trello-mcp\\dist\\index.js"],
"env": {
"TRELLO_API_KEY": "your-api-key",
"TRELLO_TOKEN": "your-token"
}
}
}
}
```
## 利用可能なツール
| ツール名 | 説明 |
|---------|------|
| `get_boards` | 認証ユーザーの全ボードを取得 |
| `get_lists` | 指定ボードの全リストを取得 |
| `get_cards` | 指定リストの全カードを取得 |
| `create_card` | 新しいカードを作成 |
| `update_card` | カードを更新 |
| `delete_card` | カードを削除 |
## 開発
```bash
# TypeScriptのコンパイル監視
npm run build -- --watch
# 開発モードで実行
npm run dev
```
## ライセンス
ISCTDQS
Scored across 7 tools
Each tool has a clearly distinct purpose targeting specific Trello resources and actions, with no overlap in functionality. For example, get_boards, get_lists, and get_cards handle different retrieval operations, while create_card, update_card, and delete_card manage the card lifecycle distinctly.
All tools follow a consistent verb_noun pattern with the 'tre__' prefix, using clear action verbs like create, delete, get, invite, and update. The naming is uniform and predictable across all seven tools, making them easily distinguishable and readable.
With 7 tools, this server is well-scoped for managing Trello boards, lists, cards, and members. Each tool serves a specific purpose without redundancy, covering core operations like retrieval, creation, updates, and invitations in a concise and effective manner.
The tool set provides solid CRUD coverage for cards and basic board/list management, with minor gaps such as missing operations for updating or deleting boards/lists, and no tools for handling comments or attachments on cards. However, the core workflows for card lifecycle and board access are adequately covered.