Trello MCP Server

Created By
shnvta year ago
Overview

what is Trello MCP Server?

Trello MCP Server is a Model Context Protocol (MCP) server designed to integrate Trello with AI assistants, allowing AI agents to utilize Trello API functionalities through MCP tools.

how to use Trello MCP Server?

To use the Trello MCP Server, clone the repository, install the necessary dependencies, set up your environment variables with your Trello API key and token, and start the server to access the available MCP tools.

key features of Trello MCP Server?

  • Integration of Trello API with AI assistants via MCP tools
  • Ability to retrieve Trello cards by board ID
  • Easy setup and development process with Node.js and pnpm

use cases of Trello MCP Server?

  1. Automating task management by retrieving Trello cards through AI agents.
  2. Enhancing productivity tools that require Trello data.
  3. Building custom AI solutions that interact with Trello boards.

FAQ from Trello MCP Server?

  • What are the prerequisites for using Trello MCP Server?

You need Node.js, pnpm (or npm), and a Trello API key and token.

  • How do I start the server?

You can start the server by running pnpm start or npm start after setting up your environment variables.

  • Can I add new tools to the server?

Yes! You can add new Trello API tools by following the provided instructions in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
shnvt
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
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