Capabilities: the CLI and MCP server side by side

Everything you and your agents can do with FEATit from a terminal or an AI assistant, with the CLI command and the MCP tool for each, side by side.

An agent reaches FEATit through the featit command line or through the MCP server, and both offer the same capabilities. Each capability below names the command, and the MCP tool and action, that do it. Where only one of them offers something, it says why: it works on your own computer, it needs a person’s own sign-in, or it is for the people who run a work area or the deployment. Where the other side is on its way, it says so.

Everything here comes from one catalogue that FEATit’s own checks hold against the CLI and both MCP servers, so nothing is added to either without this page.

Work items

File, find, change and close the issues, features, tasks and actions on a board.

What you can do	CLI	MCP
List and filter items. Every item on a board, filtered by type, state, priority, responsible or release.	`featit list`	`featit_items` list
Read one item in full. An item with its comment trail, or the one context an agent taking it needs: parents, governing decisions, plan and the rules of its stage.	`featit show`, `featit show --context`	`featit_items` show, `featit_items` context, `fetch`
Read the skill for an item. The skill for the work on an item, from its type’s task skill or the nearest item above it, as an assistant’s SKILL.md.	`featit skill`	`featit_items` context
Search. Full-text search across titles and content of every work area you may read.	`featit search`	`search`
File an item. An issue, feature, task, action or decision, filed with its parts and release in one step. A scheduled run that only reports files through its narrowed tool.	`featit new`	`featit_item_change` create, `featit_item_propose` create
Check a request for clarity. The questions the work area’s assistant asks before a request is filed, then the request restated, filed with the original message kept beside it.	`featit clarity`, `featit new --original-file`	`featit_item_change` clarity, `featit_item_change` create
Read what a request must say. The clarity guide, the fields with their allowed values and required flags, and the upload limits of a request form, in the reader’s language, refused as the form is.	`featit expectations`	`featit_items` expectations
Change an item. State, responsible, priority, content, parts or release, refused when the item moved since it was read. Reopening is a change of state.	`featit update`, `featit update --state`, `featit update --displace`	`featit_item_change` update, `featit_item_change` move, `featit_item_change` reopen
Put an item under a parent. Cluster related work under one lead item, or take it out again.	`featit parent`	`featit_item_change` update
Close an item. Into whatever this work area calls closed, through the gates its flow sets.	`featit close`	`featit_item_change` close
Move an item to another work area. The item keeps its history, and its old key still finds it.	`featit move`	`featit_item_change` transfer
Turn a task into an action, or back. Code work and work that is not code are told apart. The old key still finds it.	`featit convert`	`featit_item_change` convert
Fold a repeated request into the item it repeats. Its askers are counted on the item that stays.	`featit merge`	`featit_item_change` merge
Link two items. Implements, blocks, relates, duplicates or addresses, and taking a link away.	`featit relate`, `featit unrelate`	`featit_item_change` relate, `featit_item_change` unrelate
How an item got here. Every change to one item, by whom and when.	`featit history`	`featit_items` history
Watch an item. Be told about its changes, as yourself or as your agent, and stop again.	`featit watch`, `featit unwatch`	`featit_item_change` watch, `featit_item_change` unwatch
Who watches an item. Everyone and every agent told about an item’s changes.	`featit watchers`	`featit_items` watchers
Share an item with guests. Customers, testers or partners read the item as their role allows, and you see who reads it.	`featit share`	`featit_item_change` share
Make the item this one asks for. Where an item’s type makes another (`makes`), one step files it: yours, on the same part, and linked as implementing this one.	`featit make`	`featit_item_change` make
Make the designs from the master. Every design below an item whose format field says how it is made gets its picture from the master: at its format’s size, in its own language, never over a hand edit.	`featit designs`	`featit_item_change` make_designs
Ask the reporter to confirm the fix. Once the fix ships, the person who reported it is asked whether it is fixed for them.	`featit confirm-request`	`featit_item_change` request_confirmation

Comments, questions and attachments

Discuss an item where the work is, ask a question that waits for its answer, and keep the files it produced.

What you can do	CLI	MCP
Comment on an item. A markdown comment in the item’s trail, attributed to the agent that wrote it and its owner.	`featit comment`	`featit_item_change` comment, `featit_item_propose` comment
Read comments. One item’s trail, or every comment of a recent window across the board.	`featit comments`, `featit recent-comments`	`featit_items` comments, `featit_items` recent_comments
Pin a comment. Keep up to three comments at the top of their item, and unpin them.	`featit comment-pin`, `featit comment-unpin`	`featit_item_change` pin_comment, `featit_item_change` unpin_comment
Ask and answer questions. A question in an item’s conversation with options to answer, claimed by whoever answers it, and the open questions waiting for you.	`featit ask`, `featit answer`, `featit question-claim`, `featit ask send`, `featit questions`	`featit_item_change` ask, `featit_item_change` answer, `featit_item_change` question_claim, `featit_item_change` question_send, `featit_items` questions
Read attachments. An item’s files, or the recent ones across the board, with a download link and a context-sized version for agents.	`featit attachments`, `featit recent-attachments`	`featit_items` attachments
Attach files to an item. Upload the output an item produced, and the next version of a file, keeping every earlier one. Over MCP a file up to 1 MB goes inline. A larger one goes to a short-lived upload address that takes that one file.	`featit attachment-upload`, `featit attachment-version`	`featit_item_change` attachment_upload, `featit_item_change` attachment_version
Keep an attachment longer. Extend or pin how long a file’s original is kept.	`featit attachment-retention`	Not on MCP. Storage policy is a person’s choice, not an agent’s step.
Read your inbox. What you or your agent were told since you last looked: mentions, replies, assignments.	`featit inbox`	`featit_inbox` list
Mark the inbox read. Clear what you have seen, so the next look shows only what is new.	`featit inbox-read`	`featit_inbox_change` mark_read
Acknowledge a FEATit instruction. Say that an instruction a schedule sent you was read, or is done. Reading the inbox does not.	`featit instruction`	`featit_inbox_change` ack_instruction

Flow, waiting and hand-offs

Move an item through its delivery flow, let it wait on other work, and hand a step to a person or an agent.

What you can do	CLI	MCP
Where an item stands on its flow. The node it waits at, the routes its runs took, and why.	`featit flow`, `featit flow-history`	`featit_items` delivery_flow, `featit_items` flow_history
Take a named output of a node. One branch of parallel paths, taken on purpose.	`featit advance`	`featit_item_change` advance
Place an item at a node. A work-area admin’s correction, skipping entry rules, with the reason on record.	`featit reposition`	`featit_item_change` reposition
Wait, postpone and resume. An item waits on other items, a date or a release, with why, comes back by itself, or is brought back now.	`featit wait`, `featit postpone`, `featit resume`	`featit_item_change` wait, `featit_item_change` postpone, `featit_item_change` resume
Hand a step to a person. Filed for them, and the item waits on it.	`featit hand-off`	`featit_item_change` hand_off
Hand an item to an agent. Its adapter starts the agent with the item’s context.	`featit hand`	`featit_item_change` hand

Decisions, holds and your queue

Put a decision to the person who owns it, answer what waits for you, and release what the rules hold.

What you can do	CLI	MCP
Read decisions. A work area’s decisions with their options and answers, and those waiting for your answer across every work area you read, oldest first.	`featit decisions`, `featit decisions --mine`, `featit decisions --revision-requested`	`featit_decisions` list, `featit_decisions` waiting, `featit_decisions` access_requests, `featit_decisions` revision_requested
Raise and answer decisions. File a decision for a person or a named agent, answer, revise, supersede, withdraw, claim, refuse, ask for its revision or postpone it.	`featit decide new`, `featit decide answer`, `featit decide unanswer`, `featit decide supersede`, `featit decide unsupersede`, `featit decide claim`, `featit decide refuse`, `featit decide request-revision`, `featit decide withdraw`, `featit decide revise`, `featit decide postpone`, `featit decide resume`	`featit_decision_change` file, `featit_decision_change` answer, `featit_decision_change` unanswer, `featit_decision_change` supersede, `featit_decision_change` unsupersede, `featit_decision_change` claim, `featit_decision_change` refuse, `featit_decision_change` request_revision, `featit_decision_change` withdraw, `featit_decision_change` revise, `featit_decision_change` postpone, `featit_decision_change` resume
Verify the signed decision chain. Read a work area’s signed chain and check it on your own side.	`featit chain`	`featit_decisions` chain
Everything waiting on you. Items you are responsible for, holds you may answer and questions asked of you, in one list.	`featit tasks`	`featit_tasks` list
Answer holds. Held filings, agents’ held moves and node requests: confirm one, or decline it.	`featit holds`, `featit confirm`, `featit decline`	`featit_items` holds, `featit_item_change` confirm, `featit_item_change` decline

Planning and the roadmap

The queue in the order the work area sets, the plan on each item, ideas, their owners and proposals, and the roadmap.

What you can do	CLI	MCP
The queue. What to take next, ordered by the work area’s own rules.	`featit next-up`	`featit_items` next_up
Saved queue queries. Save a next-up query, make one your default, list and remove them.	`featit next-up-configs`, `featit next-up-config-save`, `featit next-up-config-default`, `featit next-up-config-delete`	`featit_items` next_up_configs, `featit_item_change` next_up_config_save, `featit_item_change` next_up_config_default, `featit_item_change` next_up_config_delete
The plan on an item. Objective, next actions and their owners, changed only against the revision you read, and superseded actions kept.	`featit plan`	`featit_items` plan, `featit_item_change` plan_start, `featit_item_change` plan_update, `featit_item_change` plan_supersede
An agent’s list. The items an agent holds, what they wait on, and the decisions blocking them.	`featit packet`	`featit_items` packet
Your ideas. The ideas you reported, each with how long it has waited.	`featit ideas`	`featit_items` ideas
Who owns the ideas. The owners, the proposal writer, the owner’s mail, changing an idea’s owner, and the history of the owner’s guide.	`featit owner-flow`	`featit_work_areas` owner_flow, `featit_work_area_change` set_owner_flow, `featit_work_area_change` change_idea_owner, `featit_work_areas` guide_history
The owner’s guide. The guide an owner’s assistant reads in a work area, with its revision.	`featit guide`	`featit_work_areas` guide
Challenge an idea. The challenge points a work area weighs, the challenge on an idea, saved against its proposal.	`featit challenge`, `featit challenge --save`, `featit challenge-points`	`featit_items` challenge, `featit_item_change` challenge_save, `featit_work_areas` challenge_points
Answer a challenge question. The owner answers in their own client, or an agent answers for the record, with its reason.	`featit answer --choose`	`featit_item_change` challenge_answer
Proposals on ideas. Read and write the proposal or the card on an idea, put a card to its owner, widen an idea, or say a small change grew larger than agreed.	`featit proposal`, `featit proposal save`, `featit proposal put`, `featit proposal widen`, `featit proposal larger`	`featit_items` proposal, `featit_item_change` save_proposal, `featit_item_change` put_to_owner, `featit_item_change` widen, `featit_item_change` mark_larger_than_agreed
Most recent items. What changed last: completed, active or in progress.	`featit latest`	Not on MCP. Composed by the CLI from reads MCP already offers. A connection composes the same answer from those tools.
What changed. An overview or an event list of the changes across a board.	`featit activity`	Not on MCP. Composed by the CLI from the item changes a view reads. One item’s history is a tool of its own.
The roadmap. Periods, releases or topics grouped by part: the same lanes the web Roadmap shows.	`featit roadmap`	`featit_roadmap` lanes

Releases and verification

Plan releases, ship them once, record checks and verification, and audit what claims to be done.

What you can do	CLI	MCP
List releases. A work area’s releases and their state.	`featit releases`	`featit_releases` list
Plan and ship releases. Create, change or delete a release, ship it once with its notes, after which it never changes.	`featit release-new`, `featit release-update`, `featit release-delete`, `featit release-ship`	`featit_release_change` create, `featit_release_change` update, `featit_release_change` delete, `featit_release_change` ship
Attach items to a release. Fixed in or found in, and filling in missing attributions in bulk.	`featit release-set`, `featit item-release`, `featit release-backfill`	`featit_release_change` set, `featit_release_change` backfill
Place and correct releases from Git. Place done items in the build that first shipped their commit, and correct a released release’s wrong commit with proof.	`featit release-place`, `featit release-correct-commit`	Not on MCP. Reads a local repository’s commit graph, tags or files. The server runs no Git.
Release readiness. What each shippable version is short of, and in which currency.	`featit release-readiness`	Not on MCP. Composed by the CLI from reads MCP already offers. A connection composes the same answer from those tools.
Record a check result. A build, test or release-test result for a commit or a release, which the check gates read.	`featit check-report`	`featit_item_change` check_report
Verification claims. Record what an item’s verification covers, and read every item’s current claim completely.	`featit verify`, `featit claims`	`featit_item_change` verify, `featit_items` claims
Freeze files for review. Freeze an item’s exact files, list the revisions, and approve one.	`featit revision-set`	`featit_items` revision_sets, `featit_item_change` freeze_revision, `featit_item_change` confirm_revision, `featit_item_change` confirm_revisions
Is the board in sync. Whether a work area’s board agrees with what it was told.	`featit sync-status`	`featit_items` sync_status
Audit items with no release. Items that say they are on trunk but name no release.	`featit audit-releaseless`	Not on MCP. Composed by the CLI from reads MCP already offers. A connection composes the same answer from those tools.
Audit resolved commits. Resolved items whose commit is missing or unreachable.	`featit audit-resolved-sha`	`featit_items` resolved_sha_audit
Where a commit is referenced. Every place on the board that names a commit, resolved against your repository.	`featit audit-sha-references`	Not on MCP. Reads a local repository’s commit graph, tags or files. The server runs no Git.

Commits

Tie commits to the items they deliver and see what each agent landed.

What you can do	CLI	MCP
Commits. Commits, linked to items or not.	`featit commits`	`featit_items` commits
Commit totals per agent. What each agent landed in a window.	`featit commit-summary`	`featit_items` commit_summary
Import commits from a repository. Record the commits of a local repository and the items they name.	`featit commit-sync`	Not on MCP. Reads a local repository’s commit graph, tags or files. The server runs no Git.
Name a file on a machine. The reference that names a file by its work-area folder and device, and which copies of files are behind their source.	`featit file-ref`, `featit document-copies`	Not on MCP. Works on the machine the CLI runs on: its files, repositories, processes or harnesses, which a server-side connection cannot reach.
Commit hooks. Install, check or remove the hooks that link commits to items.	`featit git-hooks`	Not on MCP. Works on the machine the CLI runs on: its files, repositories, processes or harnesses, which a server-side connection cannot reach.

Linked records and webhooks

Connect GitLab and GitHub, follow linked records where they live, and send events to other systems.

What you can do	CLI	MCP
Linked records. Link an item to a GitLab or GitHub issue, a merge or pull request or any page, read its card and its conversation where it lives, and take it off.	`featit links`, `featit link`, `featit unlink`, `featit external-conversation`	`featit_external_records` list, `featit_external_record_change` link, `featit_external_record_change` unlink, `featit_external_records` conversation
Reply on a linked record. A reply sent once through its stream, labelled when an agent wrote it.	`featit external-reply`	`featit_external_record_change` comment
Close or reopen a linked record. The issue or request closes or reopens where it lives.	`featit external-close`, `featit external-reopen`	`featit_external_record_change` close, `featit_external_record_change` reopen
Connected repositories. The GitLab and GitHub repositories a work area is connected to.	`featit streams`	`featit_work_areas` streams
Connect repositories. Connect a GitLab or GitHub repository, its secret shown once, and set a GitHub stream’s app.	`featit stream-connect`, `featit stream-github-app`	Not on MCP. Managing a work area, its people or the deployment is for people: no agent connection holds that permission, so MCP offers no tool that could only be refused.
Outbound webhooks. A work area’s webhooks, never their secrets, and every delivery attempt with its answer.	`featit webhooks`, `featit webhook-deliveries`	`featit_webhooks` list, `featit_webhooks` deliveries
Set up webhooks. Add, change, remove, rotate a secret and redeliver an event.	`featit webhook-add`, `featit webhook-update`, `featit webhook-remove`, `featit webhook-rotate-secret`, `featit webhook-redeliver`	Not on MCP. Managing a work area, its people or the deployment is for people: no agent connection holds that permission, so MCP offers no tool that could only be refused.

Documents, pages and reviews

Keep documents on pages and items, review files on their exact revision, and share one document with one person.

What you can do	CLI	MCP
Documents. List and read documents on a page, an item or the whole work area. Save one, and attach it to another place or detach it.	`featit documents`, `featit document`, `featit document-save`, `featit document-attach`, `featit document-detach`	`featit_documents` list, `featit_documents` show, `featit_document_change` save, `featit_document_change` attach, `featit_document_change` detach
Review repository files. Comment on and propose changes to a file on its exact revision, answer, resolve and accept them, and hand saved discussions on as one item.	`featit file-review`	`featit_file_reviews` repositories, `featit_file_reviews` list, `featit_file_reviews` show, `featit_file_reviews` messages, `featit_file_reviews` history, `featit_file_reviews` compare, `featit_file_reviews` capture, `featit_file_review_change` comment, `featit_file_review_change` propose, `featit_file_review_change` reply, `featit_file_review_change` edit, `featit_file_review_change` resolve, `featit_file_review_change` reopen, `featit_file_review_change` accept, `featit_file_review_change` reject, `featit_file_review_change` withdraw, `featit_file_review_hand_on` item
Share one document with one person. Without work-area membership: share, discuss, propose changes and keep snapshots.	`featit artifact-share`	`featit_artifact_shares` policy, `featit_artifact_shares` list, `featit_artifact_shares` received, `featit_artifact_shares` show, `featit_artifact_shares` content, `featit_artifact_shares` discussions, `featit_artifact_shares` discussion, `featit_artifact_shares` messages, `featit_artifact_shares` history, `featit_artifact_shares` snapshot_status, `featit_artifact_share_change` policy_update, `featit_artifact_share_change` create, `featit_artifact_share_change` update, `featit_artifact_share_change` revoke, `featit_artifact_share_change` resend, `featit_artifact_share_change` accept, `featit_artifact_share_change` prepare_snapshot, `featit_artifact_share_change` comment, `featit_artifact_share_change` propose, `featit_artifact_share_change` reply, `featit_artifact_share_change` edit, `featit_artifact_share_change` discussion_status, `featit_artifact_share_change` finalize_snapshot
The page tree. The pages below Home, in the order every reader sees them.	`featit pages`	`featit_work_areas` pages
Arrange pages. Create, move and rename pages, choose their icons, the README titles, and the defaults page blocks show.	`featit page-new`, `featit page-move`, `featit page-update`, `featit page-icons`, `featit block-defaults`, `featit work-area-document-names`	Not on MCP. Managing a work area, its people or the deployment is for people: no agent connection holds that permission, so MCP offers no tool that could only be refused.
Every share in a work area. Each item and page shared here, with whom and by whom, and removing a share.	`featit shares`	Not on MCP. Managing a work area, its people or the deployment is for people: no agent connection holds that permission, so MCP offers no tool that could only be refused.

Parts

Say what a work area is made of, and file every item on the part it changes.

What you can do	CLI	MCP
Read parts. A work area’s parts as a tree with open items per part, and one part with its owner, related parts, documents and history.	`featit parts`, `featit part`	`featit_parts` list, `featit_parts` show
Shape parts. Create, rename, move, split, merge, retire, reopen, delete and relate parts.	`featit part-new`, `featit part-update`, `featit part-move`, `featit part-split`, `featit part-merge`, `featit part-retire`, `featit part-reopen`, `featit part-delete`, `featit part-relate`, `featit part-unrelate`	`featit_part_change` create, `featit_part_change` update, `featit_part_change` move, `featit_part_change` split, `featit_part_change` merge, `featit_part_change` retire, `featit_part_change` reopen, `featit_part_change` delete, `featit_part_change` relate, `featit_part_change` unrelate

Schedules

Regular work somebody expects, the run that checks in, and the alert when it does not.

What you can do	CLI	MCP
Read schedules. The regular work a work area expects, who answers for it, and one schedule with its newest runs.	`featit schedules`, `featit schedule`	`featit_schedules` list, `featit_schedules` show
Define schedules. Create, change and retire a schedule, set the prompt it holds, tag it with the work area’s labels, and mute its alerts for a while.	`featit schedule new`, `featit schedule update`, `featit schedule retire`, `featit schedule update --prompt-file`, `featit schedule mute`, `featit schedule unmute`, `featit schedule tag`	`featit_schedule_change` create, `featit_schedule_change` update, `featit_schedule_change` retire, `featit_schedule_change` set_prompt, `featit_schedule_change` mute, `featit_schedule_change` unmute, `featit_schedule_change` tag
Check a run in. A run says it started and how it finished, so a missed one is noticed.	`featit schedule run start`, `featit schedule run finish`	`featit_schedule_change` run_start, `featit_schedule_change` run_finish

Work areas and their rules

Create work areas and read the rules, flows, statuses and service levels they work by.

What you can do	CLI	MCP
Your work areas. The work areas you may work in, your namespaces, and where you may create one.	`featit work-areas`, `featit namespaces`	`featit_work_areas` list, `featit_work_areas` namespaces
Create a work area. An assistant creates one only after you confirm it.	`featit work-area-new`	`featit_work_area_change` create
Work-area types. The kinds of work area a new one can be.	`featit work-area-types`	`featit_work_areas` types
Export a work area. Everything in it, as JSON or CSV.	`featit export`	`featit_work_areas` export
Export a work area with its files. One archive of the export and every attached file, written to a file, which an empty work area imports.	`featit export`	Not on MCP. Works on the machine the CLI runs on: its files, repositories, processes or harnesses, which a server-side connection cannot reach. Managing a work area, its people or the deployment is for people: no agent connection holds that permission, so MCP offers no tool that could only be refused.
The rules in force. Workflow rules, the effective policy, the in-progress cap and the moves allowed between statuses.	`featit work-area-rules`, `featit work-area-transitions`	`featit_work_areas` rules
Flows and statuses. The flow an item type moves through, and the statuses items may hold.	`featit work-area-flow`, `featit work-area-statuses`	`featit_work_areas` work_area_flow, `featit_work_areas` statuses
Declared repositories. The repositories a work area resolves paths in.	`featit work-area-repos`	`featit_work_areas` repos
Service levels. How long items may take here, and when their clock runs.	`featit service-levels`	`featit_work_area_change` service_levels
Apps that report here. The apps a work area accepts reports from, and pausing one while its owner allows it.	`featit trust-source`	`featit_work_area_change` trust_source_status
Configure a work area. Its settings and workflow, item types and their policies, packages, imports, repositories, folders and which agents may be assigned.	`featit work-area-update`, `featit item-type`, `featit item-type-policy`, `featit package`, `featit import`, `featit work-area-repo-declare`, `featit work-area-repo-delete`, `featit work-area`, `featit work-area-agents`	Not on MCP. Managing a work area, its people or the deployment is for people: no agent connection holds that permission, so MCP offers no tool that could only be refused.
View as a role. See a work area as a role or a member sees it, for one command.	`featit as-if`	Not on MCP. A person’s own view of a work area: no agent credential may start one, and MCP says so.

People and access

Who works where: members, guests, invitations, and an agent asking for access and being given it.

What you can do	CLI	MCP
Ask for access to a work area. An agent asks in one step, as itself, with its reason. Follows its request or withdraws it, and is told the outcome.	`featit access request`, `featit access status`, `featit access withdraw`	`featit_access_change` request, `featit_access` status, `featit_access_change` withdraw
Answer access requests. The requests waiting for your answer, approved or declined in one step, at a level never above your own.	`featit access requests`, `featit access approve`, `featit access decline`	`featit_access` requests, `featit_access_change` approve, `featit_access_change` decline
Give an agent access. Name an agent as you saw it, give it a work area, extend its access or take it away.	`featit access grant`, `featit access extend`, `featit access revoke`	`featit_access_change` grant, `featit_access_change` extend, `featit_access_change` revoke
Invite a guest. A customer, tester or partner, to one or several work areas of one organisation, in one invitation.	`featit invite`	`featit_work_area_change` invite
Who is on a work area. Its members and their roles.	`featit members`	Not on MCP. Managing a work area, its people or the deployment is for people: no agent connection holds that permission, so MCP offers no tool that could only be refused.
Who a person is to an organisation. See each person’s membership type, Member, Guest or Public participant, and make a person a Member or a Guest or give their membership an end.	`featit members --organisation`, `featit membership-type`, `featit membership-types`	`featit_work_areas` memberships, `featit_membership_change` membership_type, `featit_work_areas` membership_types
Manage people and roles. Add and remove members, change their grade, give roles in an organisation, hand a work area or organisation on, delete a work area, and manage invitation links.	`featit member-add`, `featit member-remove`, `featit work-area-role`, `featit namespace-role-grant`, `featit namespace-role-revoke`, `featit work-area-transfer`, `featit work-area-delete`, `featit organisation-transfer`, `featit invite-create`, `featit invites`, `featit invite-revoke`, `featit held-beyond-ownership`	Not on MCP. Managing a work area, its people or the deployment is for people: no agent connection holds that permission, so MCP offers no tool that could only be refused.

Admission contracts

What a filing must carry before it reaches the board, and what the gate admitted and held.

What you can do	CLI	MCP
Read the admission contract. Templates, what is required field by field, the block and validator types, its history, what the gate admitted, and a dry check of a draft.	`featit template-vocabulary`, `featit templates`, `featit template`, `featit template-check`, `featit bindings`, `featit admission-stats`, `featit contract-changes`	`featit_work_areas` admission_vocabulary, `featit_work_areas` admission_contract, `featit_work_areas` admission_template, `featit_work_areas` admission_check, `featit_work_areas` admission_stats, `featit_work_areas` admission_changes
Change the admission contract. Save and delete templates, and change what a scope requires.	`featit template-save`, `featit template-delete`, `featit binding-save`, `featit binding-delete`	Not on MCP. Managing a work area, its people or the deployment is for people: no agent connection holds that permission, so MCP offers no tool that could only be refused.
Vouch for a held filing. Confirm a filing the gate held, so it reaches the board.	`featit confirm-admission`	Not on MCP. The gate holds a filing for a person. An agent confirming it would defeat the gate.

Agents, cost and usage

The agents that work here, what they hold, what they cost, and pausing them.

What you can do	CLI	MCP
The agents. The roster, globally or assignable in one work area, and what each harness account has left of its usage limits.	`featit agents`, `featit agents limits`	`featit_work_areas` agents, `featit_work_areas` agent_limits
Pause agents. Pause and resume the agents of a work area, and read the pauses in force.	`featit agents pause`, `featit agents resume`, `featit agents pauses`	`featit_work_area_change` fleet_pause, `featit_work_area_change` fleet_resume, `featit_work_areas` fleet_pauses
What agents cost. One item, a release or a work area, by agent, person or model.	`featit cost`	`featit_items` cost
Budgets. A token or money budget on an item or a release. At its limit, starts are refused until it is raised.	`featit budget`	`featit_items` budget, `featit_item_change` set_budget
Register and manage agents. Register an agent, change it, take it out of service, merge or fold agents, answer creation requests, and mint its credentials.	`featit agent-new`, `featit agent-update`, `featit agent-deactivate`, `featit agent-merge`, `featit agent-fold-subagents`, `featit agent-requests`, `featit agent-credential`	Not on MCP. Registering and managing an agent is its owner’s act: no agent may create, change or approve an agent.
Hand agents their list. Whether FEATit hands agents their list, per work area and agent.	`featit context-policy`	Not on MCP. A person’s setting: no agent credential may write its own context policy.
Machines, plan and prices. The machines the app has reported, use against the plan, and an organisation’s prices and rates.	`featit machines`, `featit usage`, `featit prices`	Not on MCP. Operator and billing views and settings, for the people who run the deployment.
A runner reports itself. A runner with no bridge reports its own session and token usage.	`featit agent`, `featit agent-session-sync`	Not on MCP. The runner’s own process reports over REST with its agent key. An MCP connection is a conversation, not that process.
Machine relays. The relays your machines use, your switch for each, and a relay’s usage.	`featit relay`	Not on MCP. A person’s routing choice for their own machines. A relay’s usage names the people on it and is refused to an agent.

Who you are signed in as, and the setup that lives on your own computer.

What you can do	CLI	MCP
Who you are. The agent or person signed in, its owner, the work areas it may work in, and the kind of credential it holds.	`featit whoami`	`featit_whoami` show
Sign in and out. Create an account, sign in from a browser, with a connection code or credentials, list what may act as you, and end a credential.	`featit login`, `featit register`, `featit logout`, `featit credentials`, `featit credential-revoke`	Not on MCP. A person’s own sign-in and credentials: a connection is itself a credential, granted once when it is added, and mints or ends none.
Terms of use. The terms in force on this deployment, and accepting them for your own account.	`featit terms`	Not on MCP. A person’s own sign-in and credentials: a connection is itself a credential, granted once when it is added, and mints or ends none.
Verification links. A one-time, read-only link for an independent verifier, and ending one.	`featit verification-link`, `featit verification-revoke`	Not on MCP. A person’s own sign-in and credentials: a connection is itself a credential, granted once when it is added, and mints or ends none.
Connect this machine’s assistants. The skill, hooks and one sign-in for every assistant on a computer, removed again per assistant.	`featit connect`, `featit disconnect`, `featit skill-install`, `featit skill-status`, `featit skill-uninstall`, `featit session-capture`	Not on MCP. Works on the machine the CLI runs on: its files, repositories, processes or harnesses, which a server-side connection cannot reach.
The CLI itself. Install the CLI and its bridge, choose a profile and an active work area, read its version and its help.	`featit cli-install`, `featit bridge`, `featit profile`, `featit use-work-area`, `featit version`, `featit help`	Not on MCP. Describes or configures the command line on its machine. A connection is bound to one deployment, names the work area on every call, and reads each tool’s own description.
Local services. Run the development and stable stacks on this machine and copy one database onto the other.	`featit dev`, `featit stable`, `featit db-sync`	Not on MCP. Works on the machine the CLI runs on: its files, repositories, processes or harnesses, which a server-side connection cannot reach.

Deployment and bulk operations

Imports, repairs and deployment settings an operator runs, with their dry runs.

What you can do	CLI	MCP
Deployment settings. Who may sign up, who administers the deployment, connection codes and ties to a central account, the outbound mail log, and first setup.	`featit system`, `featit connection-codes`, `featit connection-ties`, `featit mail-deliveries`, `featit bootstrap`	Not on MCP. Running the deployment is its administrators’ work, done with their own sign-in or the setup token, and kept off MCP on purpose.
Imports and bulk repair. Import an etrun board or a feedback workspace, backfill accounts and identities, organise orphans and rebuild responsibility from history.	`featit import-etrun`, `featit import-feedback-collector`, `featit feedback-account-backfill`, `featit backfill-external-identities`, `featit organize-features`, `featit recover-responsible`, `featit activity-recover`	Not on MCP. An operator’s bulk write or repair across a whole board, run once from a terminal with its dry run. Not an agent’s step.

Capabilities