Skip to main content
Profound MCP gives AI assistants tools to read and manage Projects, including their instructions, linked chats, attached resources, activity, and suggestions. To connect your MCP client to the hosted server, refer to the Connection guides.
These tools don’t list Projects from the legacy v1 version, but you can migrate them into the current version with migrate_project_to_v2. Learn more about Projects in About Projects.

How the tools work together

1

Resolve the Project category

Projects are scoped to a category, so before doing anything with Projects, the assistant resolves the category with list_categories.
2

Find a Project

Ask what work exists in a category. The assistant lists its Projects with list_projects, narrowing by status or name when you ask for it.
3

Read it

Ask about one Project. The assistant reads its instructions, visibility, viewers, and linked chats with get_project. It reads what happened in the Project with get_project_activity, the files and links attached to it with list_project_resources, and the work Aim suggests for it with list_project_suggestions.
4

Create or change a Project

Ask for a new Project, or to change an existing one. The assistant uses create_project, update_project, and archive_project. Archiving sets a Project aside without deleting it.
5

Act on suggestions

Ask for fresh suggestions with refresh_project_suggestions. Ask to start, archive, or restore a suggestion with act_on_project_suggestion.
6

Move an earlier Project to the current version

Ask to copy a Project from the previous version of Projects, along with its tasks. The assistant uses migrate_project_to_v2.

Behavior and safety

Behaviors

Every write tool defaults to preview mode: the assistant receives a plan of the change first, shows it to you, and applies the change only after you confirm it in a separate reply. Profound can disable the write tools for an organization on request.

MCP hints

The read tools (list_projects, get_project, get_project_activity, list_project_resources, and list_project_suggestions) are marked readOnlyHint: true and idempotentHint: true: they only read data and are safe to retry. The following MCP hints are set on the write tools: Every write tool also sets openWorldHint: true, which tells your MCP client that the writes land in the live, shared environment, so the client may ask you to confirm before running them.

Projects tools

Every tool also takes an optional organization_id. It’s only needed when a call fails because the category is shared by several of your organizations. In that case, the assistant passes the organization to act in.
Lists the Projects in a category that you can see, most recently updated first. Each row is a summary with the name, status, visibility, description, and number of open suggestions.Example prompts:
  • “What projects do we have in the Banking category?”
  • “Show me my archived projects.”
Inputs
Reads one Project, including its instructions, visibility, viewers, and linked chats. The assistant uses the Project’s instructions as the brief for work it does in the Project.Example prompts:
  • “Walk me through the instructions on the ‘Rank top three on savings accounts’ project.”
  • “Which chats are linked to that project?”
Inputs
Ask your assistant to compare live metrics against the Project’s goal. The Project details pair well with the analytics tools.
Reads a Project’s history, such as when it was created or renamed, when chats were linked, and when suggestions were started. Events come newest first, grouped by day, each with a one-line summary and the name of who did it.Example prompts:
  • “What changed on the savings project this week?”
  • “Who started the last suggestion on that project?”
Inputs
Lists the files, links, and other resources attached to a Project. Each row has a resource type, a title, and the chat it came from when it was attached from one. The assistant reads these as the Project’s reference material before doing work in it.Example prompts:
  • “What reference files are attached to the savings project?”
  • “Which chat did that document come from?”
Inputs
Lists the suggested work for a Project, newest first, each with its full content and sources. A suggestion is proposed (open), added (started as Project work), or archived (set aside, with the reason).Example prompts:
  • “What is Aim suggesting for the savings project?”
  • “Show me the suggestions we archived on that project.”
Inputs
Creates an empty Project in a category. The Project starts with no chats, resources, or suggestions. The preview shows the Project that would be created.Example prompts:
  • “Create a project called ‘Win savings account answers’ in the Banking category.”
  • “Start a project for our product launch, and share it with the whole organization.”
Inputs
Changes a Project’s name, description, instructions, icon, or color. The assistant sends only what changes, and the preview shows the old and new value of each field.Example prompts:
  • “Rename the savings project to ‘Win savings account answers’.”
  • “Replace the instructions on that project with a shorter brief.”
InputsNotes:
  • The assistant passes at least one field to change or clear.
  • The name can be changed but never cleared.
Archives a Project, or restores an archived one. Archiving keeps the Project, its chats, and its history, and only moves it out of the default active list, so the change is reversible.Example prompts:
  • “Archive the holiday campaign project, it’s done.”
  • “Restore the savings project from the archive.”
Inputs
Starts, archives, or restores one suggestion. Starting a suggestion turns it into work on the Project, and starting one that’s already started changes nothing. Archiving sets a proposed suggestion aside, and restoring returns an archived suggestion to proposed. The tool refuses any other change.Example prompts:
  • “Start the first suggestion on the savings project.”
  • “Archive that suggestion, we already covered it.”
Inputs
Generates fresh Project suggestions for your organization in a category. Generation runs in the background and takes a few minutes, so the assistant lists suggestions again later instead of right away.Example prompts:
  • “Refresh the project suggestions for the Banking category.”
  • “Check for new suggestions after the refresh finishes.”
InputsNotes:
  • Refreshes are rate limited per user. When the limit is reached, the request fails and says when to try again.
Copies a Project from the previous version of Projects, along with its tasks, into a new Project in the current version. The new Project is visible to your organization, and the original is left as it is. The preview names the Project and the number of tasks it would copy.Example prompts:
  • “Move our ‘Rank top three on savings accounts’ project to the new version of Projects.”
  • “Show me what migrating that project would copy.”
InputsNotes:
  • Project IDs from the previous version don’t work with the other Projects tools, and the reverse.
  • Migrating the same Project again returns the Project it already became.

Resources