Ferris

View saved version →

---
name: ferris-project-tools
description: Work with Ferris projects, tasks, issues, epics, requirements, documents, meetings, and client contacts, and search project or Ferris product knowledge. Use when working with client projects, tracking tasks, reviewing documents, searching project context, or answering how Ferris itself works.
---

# Ferris Project Tools

Use the Ferris MCP tools to find what changed, search project knowledge, and manage tasks and documents. Every tool runs as the signed-in Ferris user and only reaches projects that user can access.

## When to Use

- Finding what changed for the user recently, or what to work on next (`list_my_recent_updates`)
- Searching project knowledge for meetings, decisions, documents, and notes
- Answering how Ferris itself works (Inbox, Tasks, Chat, client portal, magic links, meetings, knowledge, sync, workflows, agents, integrations) with `search_software_context` and bank `ferris-documentation`
- Looking up third-party platform docs (Qualtrics, EngineHire, and others) attached to a project
- Creating, updating, or tracking tasks, issues, epics, and requirements
- Browsing project documents and their summaries
- Looking up project members, contacts, and actors for task assignment

## Key Workflow Pattern

For "what's new" or "what should I do next" questions, start with `list_my_recent_updates`. It works across all of the user's projects and needs no ids.

Most other tools need a `project_id`. Get it from `list_projects` (optionally with `name_filter`), then pass it to the other calls.

To pick the right search tool:

- Client engagement knowledge (meetings, decisions, SOW, people, project documents) → `search_project_context`
- How Ferris itself works → `search_software_context` with `bank: "ferris-documentation"`
- How a connected platform works (Qualtrics, EngineHire, etc.) → `search_software_context` with that bank's name

Do not use `search_software_context` for what happened on an engagement. Do not use `search_project_context` for Ferris product how-to.

## Rules the server enforces

- A tool refuses inputs it does not list. Send only the inputs in the tables below.
- Ids are UUIDs. A task number like `97` is not a `task_id`; get the id from `list_tasks` or `search_tasks`.
- List tools page with `limit` and `offset`. When a response has `has_more: true`, call again with a higher `offset`.
- Task and epic `assignees` are objects with `actor_id` (from `list_project_actors`) and a RACI `raci_role`: `responsible`, `accountable`, `consulted`, or `informed`. Sending `assignees` replaces the whole set.

Task statuses: `backlog`, `pending`, `in_progress`, `review`, `blocked`, `completed`, `cancelled`. Priorities: `critical`, `high`, `medium`, `low`.

## Search notes

`search_project_context` searches all project knowledge: meetings, documents, and notes. Use `document_ids` from `list_documents` to search only those documents.

`search_software_context` searches a software bank attached to the project:

- `bank: "ferris-documentation"`: Ferris product how-to
- Other banks (`qualtrics`, `enginehire`, ...): third-party platform docs enabled on the project

If the bank is not enabled on the project, the tool returns the banks that are. Ask complete questions, not keywords. If a Ferris how-to result is an overview page, run one follow-up query for the related topic.

Use Ferris how-to facts in your answer without citing them, and do not mention the bank name. Third-party banks may include a `source_url`, which you can cite.

## Tool Reference

### Your updates

| Tool | Required | Optional |
| ---- | -------- | -------- |
| `list_my_recent_updates` | -- | `days`, `project_id`, `limit` |

### Organizations and projects

| Tool | Required | Optional |
| ---- | -------- | -------- |
| `list_organizations` | -- | -- |
| `list_projects` | -- | `name_filter`, `limit`, `offset` |
| `get_project` | `project_id` | -- |
| `update_project` | `project_id` | `name`, `description`, `language` 

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: whats-next
description: Look at what changed for the user in Ferris over the last few days and propose concrete next tasks. Use when the user asks what's new, what changed, what needs their attention, or what to work on next in Ferris.
---

# What's next in Ferris

Turn the user's recent Ferris activity into a short, ordered list of next actions.

## Steps

1. Call `list_my_recent_updates` with `days: 7`. If the user names a project, first get its id from `list_projects` and pass it as `project_id`. If the user asks about a shorter or longer period, set `days` from 1 to 14.
2. If the response has `has_more: true`, call again with a higher `limit` (up to 100). If it has `projects_skipped`, tell the user that some projects were left out, and offer to look at one project at a time.
3. Read the updates and decide what needs the user. Put them in this order:
   - `client_question`: a client is waiting for an answer.
   - `mention`: someone asked the user something.
   - `unblocked`: work the user can start now.
   - `assigned` and `meeting_action_item`: new work for the user.
   - `comment` and `updated`: changes to the user's tasks to review.
4. For the most important items, call `get_task` or `list_task_comments` when the reason alone does not say what to do.
5. Answer with three to five next actions. For each one, give:
   - the action, as one short sentence that starts with a verb ("Reply to Dana about the go-live date")
   - the project and task, with the task's link
   - why it matters now, in a few words
6. End with one line that lists the updates you did not include, grouped by type, so the user knows nothing was hidden.

## Rules

- Do not create, change, or comment on anything unless the user asks. Offer instead: "Want me to draft the reply to Dana?"
- If there are no updates, say so in one line and offer to look further back with a larger `days`.
- Use the dates in the updates. Say "yesterday" or "on Monday", not raw timestamps.