Skip to main content
Glama
sol2flow MCP server

sol2flow MCP server

Official
by sol2flow

sol2flow MCP server

An MCP server for sol2flow: it lets AI assistants (Claude Desktop, Claude Code, Cursor, VS Code and other MCP clients) read and change your boards and tasks. It talks to sol2flow only through its public REST API with your personal API key, so it can do exactly what you can do in the app, nothing more.

  • Hosted: https://mcp.sol2flow.com/mcp for sol2flow cloud (Streamable HTTP, your key in the Authorization header).

  • Local: npx -y @sol2flow/mcp (stdio), for the cloud or your own instance.

  • Self-hosted: the Docker image ghcr.io/sol2flow/mcp next to your sol2flow.

User guide: docs.sol2flow.com → Integrations → MCP server.

Quick start

  1. In sol2flow, open Settings → API keys and create a key. Full access lets the assistant change things; Read only lets it only look (the write tools are then hidden or refused).

  2. Add the server to your client (replace sf_… with the key; for your own instance set SOL2FLOW_URL).

Claude Code

claude mcp add sol2flow --env SOL2FLOW_API_KEY=sf_… -- npx -y @sol2flow/mcp
# or the hosted server
claude mcp add --transport http sol2flow https://mcp.sol2flow.com/mcp --header "Authorization: Bearer sf_…"

Claude Desktop (claude_desktop_config.json), Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "sol2flow": {
      "command": "npx",
      "args": ["-y", "@sol2flow/mcp"],
      "env": { "SOL2FLOW_URL": "https://app.sol2flow.com", "SOL2FLOW_API_KEY": "sf_…" }
    }
  }
}

Cursor also takes the hosted server: "sol2flow": { "url": "https://mcp.sol2flow.com/mcp", "headers": { "Authorization": "Bearer sf_…" } }.

VS Code (.vscode/mcp.json; the key is asked for once and stored by VS Code):

{
  "inputs": [{ "type": "promptString", "id": "sol2flow-key", "description": "sol2flow API key", "password": true }],
  "servers": {
    "sol2flow": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@sol2flow/mcp"],
      "env": { "SOL2FLOW_API_KEY": "${input:sol2flow-key}" }
    }
  }
}

The hosted variant: "sol2flow": { "type": "http", "url": "https://mcp.sol2flow.com/mcp", "headers": { "Authorization": "Bearer ${input:sol2flow-key}" } }.

Claude.ai and ChatGPT connectors need OAuth sign-in instead of a key; that comes in a later version.

Related MCP server: projectflow-mcp

Tools

34 tools, named verb_noun. Read tools carry readOnlyHint; write tools say whether they are destructive and idempotent. Deleting is not offered: archive_task hides a task, unarchive_task brings it back.

Tool

What it does

API requests

whoami

Your account, the key (scope, expiry; sol2flow 1.8+), the API version, workspaces

2

list_workspaces

Workspaces with their slugs and your role

1

list_boards

Boards of a workspace (keys, task counts)

1

get_board

A board's lists with their tasks in board order (up to 300 tasks)

2–4

search

Boards and tasks by name, key or text (like ⌘K)

1 per workspace

list_tasks

Tasks filtered by board, list, assignee, label, text, due dates, last change

1–4

get_task

A task in full: description, checklist, links, latest comments

3

list_attachments

A task's attachments (name, type, size, id)

1

get_file

A file by id or URL: images as images (≤ 3 MB), text files as text (≤ 24 KB)

1–2

list_labels

Labels of a board or workspace

1

list_people

Members of a workspace

1

list_time_entries

Logged time, by board, task, person and period

1–3

get_timer

Your running timer

1

list_notifications

Your notifications

1

list_my_invitations

Pending invitations to you

1

create_task

A task with description, labels, assignees, dates, estimate

2–4

update_task

Fields, labels, assignees and list, step by step, reporting each step

2–7

move_task

To a list and position (top, bottom, before/after a task) or another board

3–5

archive_task

Archive (read-only until unarchived)

1

unarchive_task

Bring an archived task back

1

add_comment

A comment or reply (Markdown, mentions)

1

add_checklist_items

Checklist items, in order

1 per item

update_checklist_item

Tick, untick or edit an item

1–2

link_tasks

blocks / blocked by / relates to / duplicates

1

unlink_tasks

Remove links between two tasks

2

log_time

Time on a task (1h30m, 45m)

1

start_timer

Start your timer (stops a running one)

1

stop_timer

Stop it; the time is logged

1

update_time_entry

Change one of your entries

1

mark_notifications_read

Some or all

1 per id, or 1

respond_to_invitation

Accept or decline

1

create_board

A board with its lists

1

create_list

A list at the end of a board

1

create_label

A board label

1

Plus reference lookups: a task key (PRD-12) or board name costs one search the first time and is then cached for 10 minutes; the workspace list is fetched once a minute at most. Every request counts against the key's rate limit (600 requests per 10 minutes, at most 120 of them writes) and, where plans apply, the organization's daily API limit.

Prompts: plan_my_day and board_standup. No resources yet (a sol2flow://task/{key} resource is planned).

References

  • Task: its key (PRD-12, also an old key after a move), its URL in the app, or its id.

  • Board: its key (PRD), name, URL or id. List, label: name or id.

  • Person: me, @username, a name, or an id.

  • Workspace: the slug. Default: the workspace parameter, then SOL2FLOW_WORKSPACE (or ?workspace= on the HTTP endpoint), then your only workspace. With several and none chosen, key lookups search them all (up to 10).

Output is compact Markdown (at most about 25 000 characters, with a notice when cut); response_format: "json" returns the API's data. Descriptions and comments are read and written as Markdown.

Read-only mode

--read-only, READ_ONLY=true or ?read_only=1 hide every write tool. In stdio mode a read-only key hides them automatically (sol2flow 1.8+ tells the server the key's scope); otherwise a write answers with a clear "this key is read-only".

How it works

  • Every tool call becomes REST API requests with your key: Authorization: Bearer sf_…, User-Agent: sol2flow-mcp/<version>, 15 s per request, 45 s per tool, independent requests in parallel.

  • Permissions are the API's: plan, key scope, the workspace's API access switch and your roles apply exactly as for the API. There is no separate MCP permission.

  • Retries: reads only — on rate_limited with Retry-After ≤ 10 s (twice) and on server or network errors (once). Never the daily plan limit, never a write: the API has no idempotency keys, so a write without an answer is reported as "may or may not have been applied; check first".

  • Versions: the server reads the Sol2flow-Api-Version header (sol2flow 1.8+). Without it, it assumes 1.7.0 and does without the newer features; a tool that needs an endpoint the instance doesn't have says the instance is too old.

  • Errors become tool results the model can act on: a refused key (how to create one and where to update it), API switched off (instance or workspace), plan, read-only plan, read-only key, permission, not found, archived task (unarchive_task first), too large, invalid parameter (named as the tool's parameter), rate limits with the time until they reset, server errors.

Configuration

Variable

Default

What it does

SOL2FLOW_URL

https://app.sol2flow.com

The sol2flow instance (…/api/v1 is added). In HTTP mode fixed by the operator: clients can't change it

SOL2FLOW_API_KEY

—

stdio only: the API key. Or SOL2FLOW_API_KEY_FILE (a Docker secret). There is no flag, so it never shows in ps

SOL2FLOW_WORKSPACE

—

The default workspace slug

READ_ONLY

false

Hide the write tools (same as --read-only)

MCP_TRANSPORT

stdio

stdio or http (same as --stdio / --http; the image sets http)

HOST, PORT

127.0.0.1, 3000

HTTP: where to listen (the image: 0.0.0.0)

ALLOWED_HOSTS

loopback only

HTTP: accepted Host headers (host or host:port, comma-separated). Unset on a public bind: any (a warning)

ALLOWED_ORIGINS

localhost origins

HTTP: accepted Origin headers of browser clients; * for any. Requests without Origin are always accepted

TRUST_PROXY_HOPS

0

HTTP: proxies in front; the client IP is that many X-Forwarded-For entries from the right

FORWARD_CLIENT_IP

false

HTTP: send the client IP upstream as X-Forwarded-For (when sol2flow trusts this server as its proxy)

LOG_LEVEL

info

debug adds one line per API request

LOG_FILE

—

Also write the log to dated files next to this path (e.g. /data/logs/mcp.log; see Logging)

LOG_FILE_MAX_SIZE, LOG_FILE_FREQUENCY, LOG_FILE_MAX_FILES

none, daily, 10

Rotation: as in the app and the website

SENTRY_DSN, SENTRY_ENVIRONMENT, SENTRY_RELEASE

—, production, version

Error tracking (image only; or SENTRY_DSN_FILE)

Flags: --stdio, --http, --read-only, --host, --port, --version, --help.

Hosting (Streamable HTTP)

POST /mcp is stateless: each request builds a fresh server around that request's key and answers with JSON (no SSE streams, no sessions, so it works behind tunnels that buffer). Nothing is stored. GET /healthz answers {"status":"ok","version":"…"}; GET and DELETE /mcp answer 405. Query parameters: workspace=<slug> (the default workspace) and read_only=1.

Protections: no or malformed key → 401 with WWW-Authenticate; Host and Origin checks against DNS rebinding; bodies up to 1 MB (413); 15 s to send the headers, 60 s per request; at most 100 requests in flight per process (503); at most 30 rejected keys per client IP in 10 minutes (429); a key sol2flow refused isn't sent upstream again for 5 minutes.

  • Docker Swarm: examples/swarm-stack.yml (secrets, logs on a host directory owned by 1001:1001).

  • Self-hosting: examples/compose.selfhosted.yml puts the server next to your sol2flow's app service; give it a host name behind your reverse proxy and set ALLOWED_HOSTS to it.

docker run --rm -p 3000:3000 --read-only -e SOL2FLOW_URL=https://flow.example.com \
  -e ALLOWED_HOSTS=mcp.example.com ghcr.io/sol2flow/mcp

The image (linux/amd64, linux/arm64) is one bundled file on node:22-alpine, runs as 1001:1001, works with a read-only root filesystem, and has a health check.

Logging

JSON lines (pino) on stdout in HTTP mode and on stderr in stdio mode (stdout is the protocol). Each tool call logs the tool, the outcome, the duration, the number of API requests, the client IP (HTTP) and the key's public 8-character prefix; with LOG_LEVEL=debug also each upstream operation and its status. Never the key, tool arguments or results: on top of not logging them, the usual field names are redacted and every line is scrubbed of anything shaped like a key or a bearer token.

LOG_FILE writes the same lines to mcp-YYYY-MM-DD.log files with mcp.log as a symlink to the current one (LOG_FILE_FREQUENCY daily · hourly · none, LOG_FILE_MAX_SIZE like 20m, LOG_FILE_MAX_FILES kept, 0 = all). A file that can't be written never stops the server: one warning, then the console only.

Error tracking

Off unless SENTRY_DSN (or SENTRY_DSN_FILE) is set, and only in the Docker image (the npm package doesn't ship the SDK). Only server errors from sol2flow and unexpected errors are sent, without requests, headers, bodies, arguments, results or user data. Works with sentry.io, Bugsink and GlitchTip.

Privacy

The server stores nothing: no keys (in HTTP mode only a fingerprint of keys sol2flow refused, for 5 minutes), no content. Resolved references (task key → id) are cached in memory for 10 minutes per key fingerprint. What reaches the AI assistant is up to you and the assistant's provider.

Contributing

Building, testing and releasing: DEVELOPMENT.md. Contributions: CONTRIBUTING.md.

License

MIT (see LICENSE); the bundled packages' licences are in THIRD-PARTY-NOTICES.md. Security reports: SECURITY.md.

Available Tools

34 tools
add_checklist_itemsAdd checklist itemsB

sol2flow: add items to the end of a task's checklist, in the order given (one request each).

Inputs: task (required), items (required), workspace.

add_commentComment on a taskA

sol2flow: add a comment (Markdown) to a task, or a reply to a top-level comment (reply_to: its id from get_task). Mention someone with @[Name](user:): they are notified.

Inputs: task (required), text (required), reply_to, workspace.

archive_taskArchive a taskA
DestructiveIdempotent

sol2flow: archive a task. It leaves lists, search and counts, stays in timesheets and exports, and is read-only until unarchive_task. Already archived: no change. (Deleting is not offered: archiving is the safe way.)

Inputs: task (required), workspace.

create_boardCreate a boardA

sol2flow: create a board in a workspace, optionally with its lists (in order). You become its board admin. access WORKSPACE (default): every workspace member gets default_role; RESTRICTED: only people added to it.

Inputs: name (required), lists, access, workspace, +1 more.

create_labelCreate a board labelA
Idempotent

sol2flow: create a label on a board. If a label with that name exists (workspace or board), that one is returned instead. Colors: yellow, orange, red, pink, purple, blue, cyan, green, gray or #RRGGBB.

Inputs: name (required), board (required), color, workspace.

create_listAdd a list to a boardA

sol2flow: add a list (column) at the end of a board. Editors and board admins.

Inputs: name (required), board (required), workspace.

create_taskCreate a taskA

sol2flow: create a task on a board, in a list (default: the first list), with an optional Markdown description, labels (names), assignees ("me", usernames or names), dates and an estimate. Editors and board admins.

Inputs: board (required), title (required), list, labels, +7 more.

get_boardShow a boardA
Read-only

sol2flow: a board with its lists and, in each list, its tasks in board order (key, title, due date, assignees, labels). Shows up to 300 tasks.

Inputs: board (required), workspace, include_tasks, response_format.

get_fileOpen a fileA
Read-only

sol2flow: one file, by its id (from list_attachments) or its URL (an image link in a description or comment, …/files/). PNG, JPEG, GIF and WebP images up to 3 MB come back as an image you can look at, text files up to 24 KB as text; anything else as its name, type and size.

Inputs: file (required).

get_taskShow a taskA
Read-only

sol2flow: one task in full: list, assignees, labels, dates, estimate, description (Markdown), checklist (with item ids), links to other tasks and the latest comments.

Inputs: task (required), comments, workspace, response_format.

get_timerRunning timerA
Read-only

sol2flow: your running timer, if any (task and start time).

Inputs: response_format.

list_attachmentsList a task’s attachmentsA
Read-only

sol2flow: the files attached to a task (name, type, size, id). get_file opens one: images as images, text files as text. Images inside the description are not attachments: get_task shows them as links, get_file opens those too.

Inputs: task (required), workspace, response_format.

list_boardsList boardsB
Read-only

sol2flow: the boards you can open in a workspace, with their keys (PRD), task counts and your role.

Inputs: limit, query, cursor, archived, +2 more.

list_labelsList labelsA
Read-only

sol2flow: labels. With board: the ones usable on that board (the workspace's labels and the board's own); without: the workspace's labels.

Inputs: board, workspace, response_format.

list_my_invitationsList my invitationsA
Read-only

sol2flow: pending invitations to your verified email address (workspace, board, role, who invited you). respond_to_invitation accepts or declines one.

Inputs: response_format.

list_notificationsList notificationsB
Read-only

sol2flow: your notifications, newest change first (assignments, mentions, comments, due dates, …).

Inputs: limit, cursor, unread_only, response_format.

list_peopleList peopleA
Read-only

sol2flow: members of a workspace (name, @username, role), e.g. to find whom to assign. Guests of a workspace can't list its members.

Inputs: role, limit, query, cursor, +2 more.

list_tasksList tasksA
Read-only

sol2flow: tasks on a board, or on every board of a workspace, filtered by list, assignee ("me", a username or name), label, text, due dates or last change. Ordered by last change, oldest first (use updated_since for what's new). Archived tasks only with include_archived.

Inputs: list, board, label, limit, +9 more.

list_time_entriesList time entriesA
Read-only

sol2flow: logged time in a workspace, newest first, optionally for one board, task or person, and a period. You see your own entries; board and workspace admins see more.

Inputs: to, from, task, user, +5 more.

list_workspacesList workspacesA
Read-only

sol2flow: the workspaces you can open, with their slugs (the workspace parameter of other tools) and your role.

Inputs: response_format.

log_timeLog timeA

sol2flow: log time spent on a task (1 minute to 24 hours), with an optional note. Without started_at the entry ends now.

Inputs: task (required), duration (required), note, workspace, +1 more.

mark_notifications_readMark notifications readA
Idempotent

sol2flow: mark notifications read: the given ids (from list_notifications), or all of them.

Inputs: all, ids.

move_taskMove a taskA
Idempotent

sol2flow: move a task to another list and/or position (top, bottom, or before/after another task), or to a list of another board in the same workspace (the task then gets a new key there; the old key still finds it).

Inputs: task (required), list, after, board, +3 more.

respond_to_invitationAccept or decline an invitationA
Destructive

sol2flow: accept or decline one invitation from list_my_invitations. Accepting joins the workspace (and the board, if it's a board invitation). Declining can't be undone.

Inputs: response (required), invitation_id (required).

start_timerStart a timerA
Destructive

sol2flow: start your timer on a task. One timer at a time: a timer running on another task is stopped and its time logged.

Inputs: task (required), workspace.

stop_timerStop the timerA
Idempotent

sol2flow: stop your running timer; its time is logged on the task.

Inputs: no named parameters.

unarchive_taskUnarchive a taskA
Idempotent

sol2flow: bring an archived task back into its list (the first list if that one is gone).

Inputs: task (required), workspace.

update_checklist_itemTick or edit a checklist itemB
DestructiveIdempotent

sol2flow: tick or untick a checklist item, or change its text. The item: its id (from get_task), or with task its number (1 = first) or its text.

Inputs: item (required), done, task, text, +1 more.

update_taskUpdate a taskA
DestructiveIdempotent

sol2flow: change a task: title, description (Markdown), start/due date, estimate (null clears), labels and assignees (set all, or add/remove some), and the list it is in. Fields left out stay as they are. The changes are applied step by step and the answer lists each step.

Inputs: task (required), list, title, labels, +10 more.

update_time_entryChange a time entryA
DestructiveIdempotent

sol2flow: change one of your time entries (id from list_time_entries): start, duration or note (null clears it). A running timer only takes a note.

Inputs: entry_id (required), note, duration, started_at.

whoamiWho am IA
Read-only

sol2flow: the account this API key belongs to (name, username, time zone), the key itself (name, scope, expiry; sol2flow 1.8+), the instance and its API version, and your workspaces with the default one. Start here.

Inputs: response_format.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 34 tools

    Disambiguation4/5

    Most tools have clearly distinct resource+action purposes, and descriptions clarify edge cases like image links versus attachments. A few boundaries blur: update_task can change a task's list while move_task also moves it, and list_tasks, get_board, and search all return overlapping task views.

    Naming Consistency4/5

    Almost all tools follow a snake_case verb_noun pattern (create_task, list_labels, update_checklist_item, archive_task). Minor deviations like whoami and search are readable but not part of that pattern.

    Tool Count2/5

    34 tools is heavy, exceeding the 25+ threshold where surfaces become hard for an agent to navigate. Many operations are justified by the broad project-management domain, but the set could be consolidated (e.g. board/list/label management split across many create-only tools).

    Completeness3/5

    Core task lifecycle is well covered, including create, update, move, archive/unarchive, comments, checklists, time tracking, and files. Notable gaps remain: no update or delete for boards, lists, and labels; no checklist item removal; no time-entry deletion; and only the latest comments are exposed via get_task.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers