Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Trackfusion MCP Server list tasks in project 'Q3 Planning'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP (Model Context Protocol) server for Trackfusion. Exposes projects & tasks to AI assistants like Claude, OpenClaw, etc.
npm install
npm run buildRelated MCP server: TickTick MCP
Copy the example env file and fill in your API key:
cp .env.example .envEdit .env with your values:
TRACKFUSION_API_KEY=tf_your_key_here
TRACKFUSION_API_URL=https://europe-west1-oz-track.cloudfunctions.net/api # optional, defaults to productionThe server loads .env automatically via dotenv.
mcporter add trackfusion --stdio "node /path/to/trackfusion/mcp/dist/index.js" --env TRACKFUSION_API_KEY=tf_xxxAdd to claude_desktop_config.json:
{
"mcpServers": {
"trackfusion": {
"command": "node",
"args": ["/path/to/trackfusion/mcp/dist/index.js"],
"env": {
"TRACKFUSION_API_KEY": "tf_your_key_here"
}
}
}
}Tool | Description |
| List all projects with task counts |
| List tasks in a project (optional status filter) |
| Get full task details |
| Create a new task |
| Update a task (status, title, priority, etc.) |
Log in to Trackfusion
Go to Settings → API Keys
Click "New Key", select scopes, and copy the generated key
Log an interaction with a person (meeting, call, message, etc.)
Inputs: date (required), note (required), typeId (required), personId (required), +2 more.
Add a glass of water for a specific date (default 250ml)
Inputs: dateString (required), amountMl.
Create a custom food definition with nutritional info per serving
Inputs: fat (required), name (required), carbs (required), protein (required), +10 more.
Create a new habit with a goal frequency
Inputs: name (required), goalPeriod (required), goalFrequency (required), color, +4 more.
Record a new income entry. Use list_spending_sources to get valid source IDs.
Inputs: date (required), name (required), income (required), sourceId (required), +1 more.
Track a new item/product purchase
Inputs: name (required), currency (required), categoryId (required), purchaseDate (required), +4 more.
Create a new journal entry with rich text content
Inputs: title (required), content (required), mood, emoji.
Log a meal entry. Can reference a food definition or be a quick-add with just calories.
Inputs: calories (required), foodName (required), mealType (required), dateString (required), +10 more.
Create a reusable meal template from a list of foods
Inputs: name (required), items (required).
Add a new person to your CRM
Inputs: name (required), relationshipTypeId (required), birthday, location, +6 more.
Record a new expense. Use list_spending_categories and list_spending_sources first to get valid IDs.
Inputs: date (required), amount (required), sourceId (required), categoryId (required), +1 more.
Create a new task in a project
Inputs: title (required), projectId (required), status, dueDate, +2 more.
Log a workout session with exercises and sets
Inputs: date (required), exercises (required), name, notes, +2 more.
Delete a custom food definition (cannot delete system foods)
Inputs: foodId (required).
Remove a friend (also removes them from any shared projects)
Inputs: friendshipId (required).
Delete a tracked item permanently
Inputs: itemId (required).
Delete a meal entry
Inputs: entryId (required).
Delete a meal template
Inputs: id (required).
Delete an expense record permanently
Inputs: spendingId (required).
Get historical price data for an asset
Inputs: assetId (required), to, from, limit.
Get the day entry (daily notes) for a specific date
Inputs: dateString (required).
Get a daily diet summary with totals and meals grouped by type
Inputs: date (required).
Get user diet profile (TDEE calculation inputs: sex, DOB, height, activity, goal, macro preset)
Inputs: no named parameters.
Get analytics for a habit: streaks, completion rate, monthly/yearly completions
Inputs: habitId (required).
Get the user's daily nutrition goals (calories and macros)
Inputs: no named parameters.
Get personal records (PRs), optionally filtered by exercise
Inputs: exerciseId.
Get portfolio overview: total value, P&L, allocation, and all holdings
Inputs: no named parameters.
Get monthly spending analytics (total spend & income for a month)
Inputs: yearMonth (required).
Get full details of a specific task
Inputs: taskId (required).
Get water intake for a specific date
Inputs: date (required).
List available assets (stocks, crypto, etc.) with current prices
Inputs: search, assetType.
List available exercise definitions (system + custom)
Inputs: no named parameters.
List food definitions (system + custom). Optionally search by name or filter by category.
Inputs: search, category.
List pending friend requests (sent and received)
Inputs: no named parameters.
List your accepted friends
Inputs: no named parameters.
List all habits, optionally filtered by active status. Returns name, goal, streak info, and priority.
Inputs: active.
List income records, optionally filtered by date range
Inputs: to, from.
List investment transactions (buys/sells), optionally filtered
Inputs: to, from, limit, assetId, +1 more.
List all item categories (needed for creating items)
Inputs: no named parameters.
List tracked items/products, optionally filtered by status or category
Inputs: status, categoryId.
List journal entries, optionally filtered by date range
Inputs: to, from, limit.
List journal todos (task items), optionally filtered by completion status
Inputs: completed.
List logged meal entries. Filter by date, date range, or meal type.
Inputs: to, date, from, limit, +1 more.
List all saved meal templates (reusable food combinations)
Inputs: no named parameters.
List people in your CRM, optionally filtered by search or relationship type
Inputs: search, archived, relationshipTypeId.
List all Trackfusion projects with task counts and metadata
Inputs: includeArchived.
List all spending categories (needed for creating expenses)
Inputs: no named parameters.
List expense records, optionally filtered by date range, category, or source
Inputs: to, from, limit, sourceId, +1 more.
List all payment sources (needed for creating expenses and incomes)
Inputs: no named parameters.
List tasks in a project, optionally filtered by status
Inputs: projectId (required), status.
List workout sessions, optionally filtered by date range
Inputs: to, from, limit.
List saved workout templates
Inputs: no named parameters.
Log all items from a meal template as meal entries for a specific date and meal
Inputs: id (required), mealType (required), dateString (required).
Look up a product by barcode. Tries Open Food Facts first, then UPC ItemDB as fallback.
Inputs: barcode (required).
Accept or reject a pending friend request
Inputs: action (required), friendshipId (required).
Search or browse community-contributed food definitions, sorted by popularity
Inputs: limit, search, barcode, category.
Search or browse community-shared meal templates, sorted by popularity
Inputs: limit, search.
Search external food databases (Open Food Facts + USDA) for nutrition data
Inputs: query (required), page, source.
Send a friend request by email address
Inputs: email (required).
Set/update user diet profile for TDEE calculation and goal setup
Inputs: sex (required), heightCm (required), weightGoal (required), dateOfBirth (required), +5 more.
Set daily nutrition goals (calories and macro targets)
Inputs: fatGrams (required), carbsGrams (required), proteinGrams (required), dailyCalories (required).
Set water intake to a specific amount for a date
Inputs: glasses (required), amountMl (required), dateString (required).
Toggle a habit completion for a specific date. If already completed, removes it. If not completed, marks it done.
Inputs: date (required), habitId (required).
Toggle a journal todo completion, or update its fields
Inputs: todoId (required), title, dueDate, priority, +1 more.
Update a custom food definition (cannot update system foods)
Inputs: foodId (required), fat, name, brand, +11 more.
Update a habit (name, goal, active status, etc.)
Inputs: habitId (required), name, color, emoji, +6 more.
Update an existing tracked item
Inputs: itemId (required), name, notes, status, +1 more.
Update an existing meal entry
Inputs: entryId (required), fat, carbs, notes, +11 more.
Update a meal template name or items
Inputs: id (required), name, items.
Update a person in your CRM
Inputs: personId (required), name, birthday, location, +7 more.
Update an existing expense record
Inputs: spendingId (required), date, amount, sourceId, +2 more.
Update an existing task (title, description, status, priority, due date)
Inputs: taskId (required), title, status, dueDate, +2 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 76 tools
Most tools are grouped by clear noun objects, but the sheer number and near-synonymous actions create ambiguity: search_foods vs lookup_barcode vs search_community_foods, get_day_entry vs journal entries, create_item vs create_food_definition, and update_* vs set_* vs add_* all blur boundaries. Descriptions usually clarify, but an agent selecting among 76 tools will still struggle to pick the right one.
Names overwhelmingly follow a verb_noun snake_case pattern (list/create/update/delete/get), which is predictable and readable. Consistency is weakened by irregular singular/plural forms (spending/spendings, income/incomes, person/people) and by interchangeable verbs such as add_interaction vs create_*, set_nutrition_goals vs update_*, and log_meal_template vs create_meal_entry.
With 76 tools, the server presents an extreme, unwieldy flat namespace that is very difficult for an agent to navigate during tool selection. Even though each tool spans a different module, the aggregate count far exceeds what is appropriate for an MCP server, especially with many single-purpose tools like water intake helpers.
The server covers many domains, but several core lifecycles are incomplete: projects can be listed/shared but not created, tasks have no delete, income has no update/delete, workouts have no update/delete, and journal/day entries cannot be edited or deleted. These gaps will cause agent failures when users try to correct or manage data beyond basic creation.
Manage tasks, Focus Zone, notes, projects, and task history from compatible AI assistants.
Create and manage MeisterTask projects, tasks, and notes from your AI assistant.
Connects AI assistants to TrackingTime for querying time entries, projects, tasks, customers, and team data using natural language.
Manage Redbooth tasks, task lists, comments, tags and files from Claude and other AI assistants.
