Streamline任务与笔记MCP服务

Streamline MCP

MCP server that gives AI assistants access to your Streamline tasks, notes, tags, and workspaces.

Use one local Git checkout per machine and point your MCP clients at it. GitHub main is the source of updates; no npm publishing, release archives, or per-agent clones are needed. The npm registry package named streamline-mcp belongs to a different project.

Setup

1. Clone and build

Install Node.js 18 or later and Git, then run:

mkdir -p "$HOME/.local/share"
git clone https://github.com/RosTeHeA/streamline-mcp.git "$HOME/.local/share/streamline-mcp"
cd "$HOME/.local/share/streamline-mcp"
npm ci

npm ci installs the locked dependencies and builds automatically. If you already have a checkout, keep using its existing path instead of creating another.

2. Configure credentials

Create ~/.config/streamline-mcp/config.json:

{
  "projectURL": "https://YOUR_PROJECT_ID.supabase.co",
  "apiKey": "YOUR_SERVICE_ROLE_KEY",
  "userID": "YOUR_USER_UUID"
}

Use your existing Supabase project URL, service role key, and user ID. Keep this file outside the repository and out of chat/diagnostic output.

3. Connect your MCP clients

Use node with the absolute path to this checkout's dist/index.js. From the checkout, print that path with node -p 'process.cwd() + "/dist/index.js"' and put it in each client's configuration. Do not use ~ in the argument; clients do not necessarily expand it.

For example, in Claude Code's ~/.claude.json:

{
  "mcpServers": {
    "streamline": {
      "command": "node",
      "args": ["/absolute/path/to/streamline-mcp/dist/index.js"]
    }
  }
}

If a desktop client cannot find node, use its absolute path from command -v node. All clients on one machine can use the same checkout; each starts its own MCP process.

4. Restart/reconnect the MCP client

The tools will now be available. On another machine, repeat this setup using your own credentials configuration.

Update

From your checkout on main, run:

npm run update

This runs git pull --ff-only origin main and npm ci, including the build. Restart/reconnect the clients afterward. Their configured path stays unchanged. See update and recovery details and the changelog.

Tools

Tasks

Notes

Tags

Workspaces

Examples

Basic Tasks

# Create a task with tags and due date
create_task(name: "Review PR", due_date: "tomorrow", tags: ["work"], is_urgent: true)

# Search tasks due today
search_tasks(due_before: "today", include_completed: false)

# Complete a task
complete_task(uuid: "550e8400-e29b-41d4-a716-446655440000")

Append a task-note contribution

append_task_note(
  uuid: "550e8400-e29b-41d4-a716-446655440000",
  content: "Follow-up: reviewed the draft.",
  request_id: "d797f1b5-a051-48a5-813b-eed7c0d40ec2"
)

Generate a fresh request UUID for each contribution, then reuse it with identical content for every retry, including after a timeout. The append is transactional; existing notes are preserved and concurrent appends are serialized. A later intentional rewrite can still replace notes. update_task(notes) keeps its full-replacement behavior.

Requires an explicitly approved SQL migration before deployment. See deployment, permissions, limits, and rollback.

Recurring Tasks

# Create a daily recurring task
create_recurring_task(
  name: "Morning standup",
  due_date: "tomorrow",
  frequency: "daily",
  tags: ["work"]
)

# Create a weekly task on specific days
create_recurring_task(
  name: "Gym workout",
  due_date: "2025-02-15",
  frequency: "weekly",
  interval: 1,
  weekdays: [2, 4, 6],  # Mon, Wed, Fri (1=Sun, 7=Sat)
  tags: ["health"]
)

# Create a monthly task
create_recurring_task(
  name: "Pay rent",
  due_date: "2025-03-01",
  frequency: "monthly",
  day_of_month: 1,
  tags: ["bills"]
)

# Complete a recurring task (auto-creates next occurrence)
complete_task(uuid: "recurring-occurrence-uuid")

# Skip without completing
skip_recurring_task(uuid: "recurring-occurrence-uuid")

# Pause the series (no new occurrences until resumed)
pause_recurring_series(uuid: "any-task-in-series")

# Resume a paused series
resume_recurring_series(uuid: "any-task-in-series")

# End the series permanently
end_recurring_series(uuid: "any-task-in-series")

Workspace Filtering

# Search tasks in a specific workspace
search_tasks(workspace: "Work", due_before: "today")

# Search notes in a workspace
search_notes(workspace: "Projects", query: "meeting notes", limit: 10)

# List workspaces with their filtering rules
list_workspaces(include_rules: true)

# Get workspace details by name
read_workspace(name: "Work")

Notes

# Append to a note
update_note(uuid: "...", append: "\n\n## Follow-up\nNew content here")

Recurring Tasks - How It Works

Recurring tasks in Streamline use a template/occurrence model:

1. Template: A hidden "master" task that stores the recurrence rule
2. Occurrences: The visible tasks you interact with

When you complete or skip a recurring task occurrence:

• The occurrence is marked complete/skipped
• The next occurrence is automatically created based on the rule

Recurrence Options

Anchor Types

• scheduledDueDate (default): Next task is scheduled relative to when it was supposed to be done. Good for fixed schedules like "every Monday".

• completionDate: Next task is scheduled relative to when you actually completed it. Good for tasks like "2 weeks after I change the oil".

Environment Variables

You can use environment variables instead of a config file:

SUPABASE_URL=https://YOUR_PROJECT_ID.supabase.co
SUPABASE_API_KEY=your_service_role_key
SUPABASE_USER_ID=your_user_uuid

Development

npm install
npm run build
npm start
npm test # isolated local PostgreSQL + MCP tests; no production database

Changelog

v1.1.0

• Added full recurring task support:
  • create_recurring_task - Create tasks with recurrence rules
  • skip_recurring_task - Skip occurrences
  • pause_recurring_series / resume_recurring_series - Control series
  • end_recurring_series - End series permanently
  • complete_task now auto-creates next occurrence for recurring tasks
• Added include_recurring_templates option to search_tasks
• read_task now shows recurrence details

v1.0.0

• Initial release with tasks, notes, tags, and workspaces