Trello Mcp

Created By
kocaklia year ago
Trello Desktop MCP A Model Context Protocol (MCP) server that provides comprehensive Trello integration for Claude Desktop. This server enables Claude to interact with Trello boards, cards, lists, and more through a secure local connection. Features 🔍 Search & Discovery Universal Search: Search across all Trello content (boards, cards, members, organizations) User Boards: Get all boards accessible to the current user Board Details: Retrieve detailed information about boards including lists and cards 📝 Card Management Create Cards: Add new cards to any list with descriptions, due dates, and assignments Update Cards: Modify card properties like name, description, due dates, and status Move Cards: Transfer cards between lists to update workflow status Get Card Details: Fetch comprehensive card information including members, labels, and checklists 💬 Collaboration Add Comments: Post comments on cards for team communication Member Management: View board members and member details Activity History: Track card actions and changes 📋 Organization List Management: Create new lists and get cards within specific lists Labels: View and manage board labels for categorization Checklists: Access card checklists and checklist items Attachments: View card attachments and linked files
Overview

What is Trello Mcp?

Trello Mcp is a Model Context Protocol (MCP) server that provides comprehensive integration with Trello for the Claude Desktop application, allowing users to interact with Trello boards, cards, and lists through a secure local connection.

How to use Trello Mcp?

To use Trello Mcp, you need to install the server, configure it with your Trello API credentials, and set it up in the Claude Desktop application. After configuration, you can use natural language commands to interact with Trello.

Key features of Trello Mcp?

  • Universal Search: Search across all Trello content including boards, cards, and members.
  • Card Management: Create, update, move, and retrieve card details.
  • Collaboration Tools: Add comments, manage members, and track activity history.
  • List Management: Create lists and manage labels and checklists.

Use cases of Trello Mcp?

  1. Managing project tasks by creating and updating Trello cards.
  2. Collaborating with team members through comments and activity tracking.
  3. Organizing projects by managing lists and labels effectively.

FAQ from Trello Mcp?

  • What are the prerequisites for using Trello Mcp?

You need Node.js 18+, a Claude Desktop application, and a Trello account with API credentials.

  • Is Trello Mcp free to use?

Yes! Trello Mcp is free to use for anyone with a Trello account.

  • How secure is Trello Mcp?

API credentials are stored locally, and all API calls use HTTPS to ensure security.

Server Config

{
  "mcpServers": {
    "trello": {
      "command": "node",
      "args": [
        "/absolute/path/to/trello-desktop-mcp/dist/index.js"
      ],
      "env": {
        "TRELLO_API_KEY": "your-api-key-here",
        "TRELLO_TOKEN": "your-token-here"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kocakli
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago