Skip to main content
Glama
mcp-teamline

mcp-teamline

by aroy314

mcp-teamline

MCP stdio server that wraps the Teamline API so MCP hosts (Cursor, Claude, etc.) can call Teamline.

API docs: https://support.teamline.app/article/64-integrating-using-the-teamline-api

This repository is MIT-licensed. The Teamline API itself is governed by Teamline Terms of Service; using this server against Teamline means those terms apply to the API traffic.

Prerequisites

  • Node.js 20 or later

Related MCP server: Basecamp MCP Server

Environment

Set TEAMLINE_API_KEY in the environment. Create a key at https://my.teamline.app/settings/api

The token is read only from the environment. It is never a tool argument and is never logged.

Optional: TEAMLINE_HTTP_ENCODING=json or form (default json). The official article does not document the HTTP method or encoding; this server POSTs JSON { token, ...params } by default, with form-urlencoded as a fallback.

Cursor (mcp.json)

Using the GitHub package:

{
  "mcpServers": {
    "teamline": {
      "command": "npx",
      "args": ["-y", "github:aroy314/mcp-teamline"],
      "env": {
        "TEAMLINE_API_KEY": ""
      }
    }
  }
}

Fill TEAMLINE_API_KEY from your local secret store or OS environment. Do not commit a real key.

Local run

Install dependencies and compile TypeScript, then start with: node dist/index.js

Provide TEAMLINE_API_KEY in the environment when launching. After install, the bin name is mcp-teamline.

Tools

Tool

Input

Description

teamline_auth_test

none

Calls Teamline auth.test and returns the authenticated user as JSON (id, name, email).

teamline_tasks_list

optional: limit (number), channel (#name or slackId), list (~name or id; channel required if list is set), user (@name, email, or slackId), complete (boolean; true = only completed)

Calls Teamline tasks.list. If channel and user are omitted, the API defaults to yourself. Returns the task array as JSON.

teamline_tasks_create

name (required); optional: description, assign (string[] of @name/email/slackId), channel, list (channel required if set), personal (boolean), due (ISO8601 or human string), notify (string[])

Calls Teamline tasks.create. Returns the created task as JSON.

teamline_tasks_complete

task (required, id string)

Calls Teamline tasks.complete. Returns the completed task as JSON.

teamline_webhooks_create

event (required, currently only tasks_completed), url (required), name (optional)

Calls Teamline webhooks.create to register a user-provided URL. This server registers the URL; it does not receive webhook POSTs. Returns the hook as JSON.

teamline_webhooks_remove

hook (required, id string)

Calls Teamline webhooks.remove. Returns the removed hook as JSON.

If TEAMLINE_API_KEY is missing, tools return a clear error without calling the network.

License

MIT (c) 2026 Alexandre Roy. Teamline ToS apply to use of the Teamline API.

Available Tools

6 tools
teamline_auth_testTest Teamline authenticationA
Read-onlyIdempotent

Verify TEAMLINE_API_KEY against Teamline auth.test and return the authenticated user (id, name, email). Takes no arguments; the API token is read only from the environment.

Inputs: no named parameters.

teamline_tasks_completeComplete a Teamline taskA

Mark a Teamline task complete via tasks.complete. Requires task (id string). Token is read only from TEAMLINE_API_KEY.

Inputs: task (required).

teamline_tasks_createCreate a Teamline taskA

Create a Teamline task via tasks.create. name is required. Optional: description, assign (string[] of @name/email/slackId), channel (#name or slackId), list (~name or id; channel required if list is set), personal (boolean), due (ISO8601 or human string), notify (string[]). Token is read only from TEAMLINE_API_KEY.

Inputs: name (required), due, list, assign, +4 more.

teamline_tasks_listList Teamline tasksA
Read-onlyIdempotent

List Teamline tasks via tasks.list. Optional filters: limit, channel (#name or slackId), list (~name or id; channel required if list is set), user (@name, email, or slackId), complete (true = only completed). If channel and user are omitted, the API defaults to yourself. Token is read only from TEAMLINE_API_KEY.

Inputs: list, user, limit, channel, +1 more.

teamline_webhooks_createCreate a Teamline webhookA

Register a user-provided URL via webhooks.create. Official event is currently only tasks_completed. url is required; name is optional. This server registers the URL; the MCP stdio process does not receive Teamline POSTs. Token is read only from TEAMLINE_API_KEY.

Inputs: url (required), event (required), name.

teamline_webhooks_removeRemove a Teamline webhookA
Destructive

Remove a Teamline webhook via webhooks.remove. Requires hook (id string). Token is read only from TEAMLINE_API_KEY.

Inputs: hook (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    Tasks and webhooks are clearly separated by the teamline_ prefix and verb. Within tasks, list/create/complete are distinct operations, though list could be confused with create if an agent overlooks the verb. Webhooks create/remove are clearly distinct.

    Naming Consistency4/5

    All tools follow a consistent teamline_<domain>_<verb> pattern (auth_test, tasks_list, tasks_create, tasks_complete, webhooks_create, webhooks_remove). The only minor deviation is 'auth_test' using a noun-verb inversion (test as verb) rather than 'test_auth', but it's readable and consistent in style.

    Tool Count5/5

    Six tools is well-scoped for a task management integration. Each tool covers a distinct operation needed for basic task lifecycle and webhook management. No redundant tools, and the count feels appropriate (within the 3-15 ideal range).

    Completeness3/5

    The tools cover task list, create, and complete, but lack update (e.g., edit task name, due date, assignee) and delete operations. Webhooks support create/remove but no list. A user cannot edit an existing task without recreating it, which is a notable gap in a task management API.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers