store_knowledgeLABSCO SUMMARY
Your notes live somewhere you can also open by hand.
The store is a Trello board, so the same snippets stay readable, editable and shareable in an app you already have while the agent reaches them through search. Nothing ends up locked inside a database only the server understands.
What it is
An MCP server that uses a Trello board as a knowledge base. Snippets and notes are stored as cards, organised across lists, and categorised with Trello labels; retrieval searches titles, descriptions and labels.
What you get
- A snippet or a note stored as a card on your knowledge board
- Stored knowledge retrieved by asking for it
- Search across card titles, descriptions and labels
- The topics currently in the board listed
Requirements
A Trello API key and token, created through a Power-Up at trello.com/power-ups/admin, plus the board ID of the board you will use. Node.js runs it, and the repository expects direnv for the environment variables.
Setup effort
Build from source — git clone https://github.com/pscheit/trello-knowledge-mcp-server.git
USE CASES
01
Saving something you had to work out once
Store it as a card with labels for how you will look for it later, on the list where that kind of thing belongs.
02
Getting back the snippet you know you saved
Search across titles, descriptions and labels, then pull the one that matches in full.
03
Seeing what you have written down so far
List the topics on the board before adding a new one, which is how you notice you have already answered this.
04
Sharing a team knowledge base an assistant can also read
Everyone adds cards the ordinary Trello way; the agent searches the same board and answers from what is on it.
4 tools
Listed in project docs. Your client may show a different list.
search_knowledgeget_knowledgelist_topicsBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- node on PATH
- TRELLO_API_KEY in your environment
- TRELLO_TOKEN in your environment
- TRELLO_KNOWLEDGE_BOARD_ID in your environment
Where it runs
All 3 documented setups run the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/pscheit/trello-knowledge-mcp-server.git
cd trello-knowledge-mcp-server
npm installMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"trello-knowledge": {
"command": "node",
"args": [
"<YOUR_PATH_TO_TRELLO_KNOWLEDGE_MCP_SERVER>/src/index.js"
],
"env": {
"TRELLO_API_KEY": "<YOUR_TRELLO_API_KEY>",
"TRELLO_TOKEN": "<YOUR_TRELLO_TOKEN>",
"TRELLO_KNOWLEDGE_BOARD_ID": "<YOUR_TRELLO_KNOWLEDGE_BOARD_ID>"
}
}
}
}<YOUR_PATH_TO_TRELLO_KNOWLEDGE_MCP_SERVER> is the full path of the folder the clone step created. Your Trello API key and token come from the Power-Up you create at trello.com/power-ups/admin; the knowledge board ID is in the board's URL.
Claude Desktop — Windows
CLAUDE DESKTOP — WINDOWS · JSON
{
"mcpServers": {
"trello-knowledge": {
"command": "C:\\Program Files\\nodejs\\node.exe",
"args": [
"C:\\Users\\<YOUR_USERNAME>\\<YOUR_PATH_TO_TRELLO_KNOWLEDGE_MCP_SERVER>\\src\\index.js"
],
"env": {
"TRELLO_API_KEY": "<YOUR_TRELLO_API_KEY>",
"TRELLO_TOKEN": "<YOUR_TRELLO_TOKEN>",
"TRELLO_KNOWLEDGE_BOARD_ID": "<YOUR_TRELLO_KNOWLEDGE_BOARD_ID>"
}
}
}
}For Windows when node is not on PATH. The trello-knowledge-mcp-server path is the folder you cloned; the three values are the same as above.
Claude Desktop — direnv
CLAUDE DESKTOP — DIRENV · JSON
{
"mcpServers": {
"trello-knowledge": {
"command": "bash",
"args": [
"-c",
"cd <YOUR_PATH_TO_TRELLO_KNOWLEDGE_MCP_SERVER> && eval \"$(direnv export bash)\" && node src/index.js"
],
"cwd": "<YOUR_PATH_TO_TRELLO_KNOWLEDGE_MCP_SERVER>"
}
}
}This one reads the three values from the .envrc file in the clone instead of an env block: put TRELLO_API_KEY, TRELLO_TOKEN and TRELLO_KNOWLEDGE_BOARD_ID in .envrc, run direnv allow in that folder. <YOUR_PATH_TO_TRELLO_KNOWLEDGE_MCP_SERVER> is the folder's full path.
