FlowyTeam OKR MCP Server

Create a new FlowyTeam company account. Only call this tool when the user explicitly requests account creation and provides all required details. Requires MCP registration to be enabled by the platform administrator. Password is optional — if omitted, a secure temporary password is generated and included in the verification email. A verification email with a 6-digit code is sent — ask the user to share the code, then call auth_verify_email to activate the account and receive the api_token immediately. Alternatively the user can click the verification link in the email to activate via the browser, then copy the api_token from FlowyTeam Settings → MCP & AI Integration.

Activate a newly registered FlowyTeam account and receive the api_token. Call this after auth_register once the user shares the 6-digit code from their verification email. Also accepts the long token from the verification link URL as a fallback. On success, the account is activated and an api_token is returned — use it as the Bearer token and reconfigure the MCP connection.

Retrieve the api_token for an existing FlowyTeam account using email and password. Only call this tool when the user explicitly provides their credentials and requests a login — never proactively. Note: for new accounts use auth_register + auth_verify_email instead. Existing users can also copy their token directly from FlowyTeam Settings → MCP & AI Integration. Returns an api_token — reconfigure the MCP connection with it as the Bearer token.

Manage tasks: list, create, update, delete, mark complete. Filter by status, priority, project, assignee, due date; archived=true lists archived tasks. A new task needs the person it is assigned to (assigned_to), as on the web form. DELETE archives a task: dry_run=true previews it, permanent=true removes an archived one for good, and PUT with restore=true brings it back.

Manage projects and their sub-resources (milestones, members, categories, files). Set resource=project (default), milestone, member, category, or file. All lookups are name-based — no IDs needed. Admins have full access. Members can view/update their own projects, and perform full CRUD on milestones, members, and files. POST requires project_name, start_date, and either deadline (Y-m-d) or without_deadline=true. If the user has not given a deadline, ask which they want before calling this tool, do not call it and wait to be refused.

Manage task categories: list, create, update, delete. Lookup by ID or category name.

Manage employee leave requests: list, create, approve, reject, cancel. Filter by status, employee, date range. Approving or rejecting recalculates the allowance and notifies the employee, and settles every date of a multi-date request at once. Approval authority follows the company leave approval setting: an admin caller may decide any request, a reporting manager may decide their own team when the setting allows managers, and nobody but an admin decides their own request. Every write returns the employee remaining days, used days and allowance, so no follow-up call is needed to read them. Set reject_reason when rejecting.

Manage leave types (annual, sick, etc.): list, create, update, delete. Admin-only for write operations. POST needs type_name and no_of_leaves, the days each employee is entitled to per year.

Read how many leave days an employee is entitled to, has used, and has left, per leave type. Name the person with employee_name. PUT recalculates the figures, the same recalculation the admin leave pages run; it needs employee_name, or all set to true for every employee. Approving leave already recalculates on its own, so PUT is only for a manual refresh.

Manage attendance: clock-in, clock-out, list records. Filter by employee, date, month, year. A list returns at most 25 records with a total count; when total exceeds what was returned, say so in the answer.

Manage employees: list, show full profile, create, update (profile/department/designation/status/skills), deactivate/delete. Always resolve by name or email — never require an ID from the user. Members read and update their own record. With the view, add, edit or delete employees permission they also list other non-admin employees, create employees, update the basic record of other non-admin employees, or delete them, as in the web app. Salary, bank details, manager flag, status, login and reporting line changes need an admin. Pay, bank and identity fields are left out of every record unless include_private is true, for an admin or for your own record.

Manage departments/teams: list, show details with members, create, update, delete, add/remove members. Always resolve by name — never require an ID from the user.

Manage job designations/positions: list (with member counts), create, update, delete. Always resolve by name — never require an ID from the user.

Manage clients: list, create, update, delete. Filter by name, company. POST requires email as well as the company or contact name. If the user has not given an email, ask for it before calling this tool rather than calling it and waiting to be refused.

Manage support tickets and their conversation replies. Supports full CRUD (list, create, update, delete), reply/conversation management (resource=reply), ticket statistics (action=stats), and close/reopen actions. Name-based lookups for agent, requester, type, and channel. Admins and privileged members have full access. Regular members can manage their own tickets (create, view, reply, close, reopen).

Manage ticket types/classifications: list, create, update, delete. Lookup by name or ID.

Manage ticket channels (e.g. email, phone, chat): list, create, update, delete. Requires the tickets module.

List ticket agents and their assigned groups.

Manage OKR objectives: list, create, update, delete. Filter by cycle, type (company/team/personal), team, employee or leader; archived=true lists the archived ones. Writes return the objective as stored. POST with the action parameter copies one into another cycle (target_cycle_id). PUT with retro writes its retro notes once its cycle is being scored. GET by id adds its retro, and with history=true every change with who, when and how. PUT with dry_run=true previews an update, an alignment change included, with the progress it moves; PUT with items updates up to 50 objectives at once, all or none. DELETE archives: one with key results needs cascade=true, dry_run=true previews it, permanent=true removes an archived one for good, and PUT with restore=true brings it back.

Manage OKR key results: list, create, update, delete, update progress. Link to objectives. Each key result lists the tasks working toward it and its linked KPIs (indicator_ids); GET by id adds the confidence history. Use the checkins tool for check-in history and who has not checked in. GET finds key results at risk with confidence_max, status and stale_weeks, and archived=true lists the archived ones. In a cycle being scored, PUT sets final_score and score_note; contributor_ids names who helps (no rights); GET by id with history=true lists every change with who, when and how. PUT with move_to_objective_id moves one to another objective in its cycle; PUT with items updates up to 50 at once, all or none; POST with the action parameter turns one into a task under target_key_result_id and archives it. Each takes dry_run=true to preview. DELETE archives it and unlinks its tasks: dry_run=true previews that with the new weight total, permanent=true removes an archived one for good, and PUT with restore=true brings it back.

Key result check-ins. GET lists the check-in history, newest first; with missing=true it lists the key results in a cycle nobody checked in on during a week, with their leader and the owner a reminder goes to. POST records a check-in on a key result: its current value, confidence, status, remarks, blockers and the source of the value. The key result and objective scores update as the web form updates them. DELETE with id archives a blank or mistaken check-in (the key result keeps its value; dry_run=true previews, permanent=true removes an archived one for good), and PUT with id and restore=true brings it back.

Discussion threads on OKR objectives and key results, the same threads the web pages show. GET lists the comments on one objective or key result, oldest first, each with its replies. POST adds a comment, or a reply with parent_id. PUT edits your own comment. DELETE archives a comment with its replies (dry_run=true previews, permanent=true removes an archived one for good), and PUT with restore=true brings it back; the author, admins and the objective's owner or leader may. Anyone who can read the objective may comment.

How a performance cycle's OKRs align. Returns the objectives in tree order from the company objectives down, each with its depth, its key results and which objectives support each key result; then the team objectives (and with include_personal the personal ones) aligned to nothing, the objectives aligned to something the tree does not reach, and the company key results nothing contributes to. Defaults to the current cycle. Personal objectives are left out unless include_personal is true.

OKR health check for a performance cycle, in one call: objectives and key results with no owner (a key result counts as owned when someone would get its check-in reminder, and those owned through their objective are listed apart), objectives whose key result weights do not total 100 (a notice: scores are weighted averages), key results with no check-in for stale_weeks (default 2), key results off track or at confidence 3 or below for their last two check-ins, objectives with fewer than 2 key results or more than the workspace allows, team and personal objectives aligned to nothing, company key results nothing supports, and KPIs linked to no key result. Each check gives a count and up to 50 items. Defaults to the current cycle; narrow with objective_type or team_id. Only what you can read is counted.

Webhooks for OKR events, admins only: a check-in saved, a key result changing status or going off track, an objective archived, a cycle going into scoring or closing (the event parameter lists them). GET lists them; POST subscribes a URL (target_url) to an event, optionally with a secret that signs each delivery (X-FlowyTeam-Signature: sha256 HMAC of the body); DELETE removes one by id. A delivery is JSON with the event, the company, when it was sent and the data; it goes out within a minute and is retried three times.

OKR reminders that FlowyTeam sends in the app, and by email when asked, under the admin's name. GET with preview=true shows who a reminder would reach and who it would leave out, without sending; show it to the user before sending. POST sends it. GET without preview lists the reminders sent. Audiences: the owners of key results with no check-in in a week, or everyone leading an objective or key result in a cycle. A person gets one reminder per audience per week. Admins only.

Manage KPI indicators: list, create, update, delete. Filter by category, employee. Lookup by title or ID. GET returns each KPI's owner, red and green thresholds, latest recorded value and the key results it is linked to.

Manage KPI indicator categories/types: list, create, update, delete. Lookup by name or ID.

Manage KPI indicator records (actual values per period): list, add, delete. Lookup by indicator_id + period_key.

Manage OKR performance cycles: list, create, update, delete. Lookup by name or ID. GET flags the cycle the workspace is in today as current and gives each status. End of cycle: PUT status moves a cycle to scoring (final scores on key results open) and to closed, which freezes the scores and locks it; dry_run=true lists what is missing first and fill_missing=true fills unscored key results. GET by id with scorecard=true returns each objective and key result with its baseline, target, final value, score and retro, and averages per objective type and team; history=true lists who changed the cycle.

Manage company holidays: list, create, update, delete. Filter by year, upcoming/past. Lookup by ID or holiday name.

Manage sales leads: list, create, update, delete. Filter by status, agent, date range.

Manage client invoices: list, create, update status, delete. Filter by client, status, date range.

Manage client estimates/quotes: list, create, update, delete. Filter by client, status, date.

Manage company events/calendar: list, create, update, delete. Filter by month, year, date range.

Manage expenses and claims: list, create, update status (approve/reject), delete. Filter by employee, category, status, date range.

Manage expense categories: list, create, update, delete. Admin-only for write operations.

Manage notice board: list, create, update, delete. Filter by date range or audience (all/employee/client).

Manage client contracts: list, create, update, delete. Filter by client, status, date range.

Manage project/task time logs: list, create (start timer), update (stop timer/edit), delete. Filter by project, employee, date.