Trello MCP Server (TypeScript)

Created By
andyposta year ago
TypeScript implementation of a Model Context Protocol (MCP) server for Trello integration
Overview

what is Trello MCP Server?

Trello MCP Server is a TypeScript implementation of a Model Context Protocol (MCP) server designed for seamless integration with Trello, allowing AI assistants to interact with Trello boards, lists, and cards.

how to use Trello MCP Server?

To use the Trello MCP Server, install the dependencies, configure your Trello API credentials in a .env file, and start the server using the provided commands.

key features of Trello MCP Server?

  • Full Trello API integration through MCP tools
  • Asynchronous operations for improved performance
  • Type-safe implementation using TypeScript
  • Comprehensive error handling for various scenarios
  • Environment-based configuration for flexibility

use cases of Trello MCP Server?

  1. Automating task management by retrieving and updating Trello cards.
  2. Integrating Trello with AI assistants for enhanced productivity.
  3. Building custom applications that require Trello data manipulation.

FAQ from Trello MCP Server?

  • What are the prerequisites for using Trello MCP Server?

You need Node.js 18.x or higher, npm or yarn, and Trello API credentials.

  • How do I install Trello MCP Server?

Use the command make install to install the necessary dependencies.

  • Can I contribute to the project?

Yes! You can fork the repository, create a feature branch, and submit a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
andypost
Star
-
Language
-
License
-

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour 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.

a day ago