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
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)

8 hours ago
Alloy

2 days ago