Streamline

Provides MCP access to Streamline data sources and actions (tasks, notes, tags, and workspaces).

javascript

0

GitHub Stars

javascript

Language

2 months ago

First Indexed

3 weeks ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "rostehea-streamline-mcp": {
      "command": "npx",
      "args": [
        "github:YOUR_USERNAME/streamline-mcp"
      ],
      "env": {
        "SUPABASE_URL": "https://YOUR_PROJECT_ID.supabase.co",
        "SUPABASE_API_KEY": "YOUR_SERVICE_ROLE_KEY",
        "SUPABASE_USER_ID": "YOUR_USER_UUID"
      }
    }
  }
}

Streamline MCP enables your AI assistants to interact with Streamline by providing access to tasks, notes, tags, and workspaces through a lightweight MCP server. Install and run the MCP, then use supported tools to manage and query your Streamline data from your assistant workflows.

How to use

You connect an MCP client to the Streamline MCP server by configuring an MCP server entry and then restarting your client. Once connected, you can search, read, create, update, and delete tasks and notes, manage tags, and explore workspaces using the available tools. The server exposes a set of practical actions that you can call from your prompts to streamline your work.

How to install

Prerequisites: ensure you have Node.js and npm installed on your machine.

Install dependencies and start the MCP locally if you prefer a local runtime.
If you want to run via the NPX-based approach, you can fetch the MCP package on demand.

Workspace Filtering

Workspaces in Streamline are defined by tag-based filtering rules. When you filter by workspace, the MCP applies those rules to return only matching items.

Example workspace rules include showing items with specific tags and excluding others. Use the list_workspaces tool to see which workspaces exist and read_workspace to view their full rule structure.

Environment variables

You can supply credentials and context via environment variables instead of a config file. The following variables are commonly used:

Tools covered by this MCP server

The server provides a suite of tools to manage your Streamline data. Use the tools to perform actions directly from your prompts.

Security and credentials

Protect your API access by using your own API keys and user identifiers. Never expose sensitive keys in prompts or logs.

Development

To build and run the MCP locally during development, follow these commands.

Available tools

search_tasks

Search tasks by name, tags, due date, status, or workspace

read_task

Get full details of a task by UUID

create_task

Create a new task with name, due date, tags, and notes

update_task

Update task attributes such as name, notes, due date, and urgency

complete_task

Mark a task as completed or uncompleted

delete_task

Move a task to trash or delete permanently

search_notes

Search notes by title, content, tags, or workspace

read_note

Get full content of a note by UUID

create_note

Create a note with markdown content

update_note

Update or append content to a note

delete_note

Move a note to trash or delete permanently

list_tags

List all tags in your workspace

create_tag

Create a new tag

tag_item

Add a tag to a task or note

untag_item

Remove a tag from a task or note

list_workspaces

List all workspaces with filtering rules

read_workspace

Get workspace details by UUID or name