Skip to main content
Profound MCP gives AI assistants tools to find, read, write, and manage documents in Profound Docs, the collaborative documents in the Profound platform, such as memos and briefs. To connect your MCP client to the hosted server, refer to the Connection guides.
Documents in Profound Docs are not Knowledge Base documents. To add content that AI assistants and Agents search and retrieve, use the add_knowledge_base_document tool instead. Refer to Knowledge Base.

​
How the tools work together

1

Find a document

Ask whether a document exists or which ones changed recently. The assistant searches document names with list_docs and links you to each result.
2

Read it

Ask for a summary or the full text. The assistant reads the document with get_doc, skimming the opening by default and loading the whole body when the task needs it.
3

Create or revise

Ask for a new document and the assistant drafts and saves it with create_doc. Ask for a change to an existing one and it rewrites the document with replace_doc_content.
4

Rename, reshare, or delete

Ask to rename a document or change who sees it (update_doc), or to delete one the assistant created earlier (delete_doc).

​
Behavior and safety

Write tools default to preview mode: the assistant receives a plan of the change first, and nothing changes until it applies that plan. The exception is delete_doc, which has no preview and deletes on the first call.

​
Behaviors

​
MCP hints

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.

​
Profound Docs tools

Finds documents and their details, such as the name, owner, visibility, and link (url). Results are ordered by most recently modified first and never include the document body.Example prompts:
  • “Do we already have a doc about our AEO strategy?”
  • “Which Profound docs changed most recently?”
InputsLimitations:
  • The tool doesn’t filter by document author or owner. To find one person’s documents, the assistant lists all documents and reads each row’s owner, which can take a while.
  • The tool doesn’t return a total document count.
Reads one document. The default preview returns only the opening of the body. When the task needs the full text or the discussion on it, the assistant loads the complete body or the comments.Example prompts:
  • “Summarize the AEO strategy memo.”
  • “Read the Q3 retro in full, including the comments people left on it.”
Inputs
Creates a new document from content the assistant has drafted. The tool takes the complete body in one call.Example prompts:
  • “Write a Q3 AEO retro based on this quarter’s visibility data and save it as a Profound doc.”
  • “Draft a competitor brief and store it in Profound so I can share it later.”
InputsNotes:
  • Document titles are unique within an organization: creating a document with a title that already exists returns the existing document and discards the new body.
  • New documents are visible only to their creator.
  • When the call fails between creating the document and storing its body, the document exists but is empty, and the response reports content_written: false. A retry returns the same empty document instead of filling it.
Use with caution: this tool replaces the entire document body, clears all tabs except the main tab, and clears all comments.
Replaces a document’s content with new text. Any change to an existing document, from ticking a box to rewriting a section, goes through this tool.Example prompts:
  • “Add a section on shopping prompts to the AEO strategy memo.”
  • “Fix the typos in the Q3 retro.”
InputsNotes:
  • When the document content is replaced, the title updates to match the new content’s first heading, unless skip_title_sync is true.
Renames a document, changes who can see it, or both in one call.Example prompts:
  • “Rename the strategy memo to ‘AEO strategy H2’.”
  • “Make the Q3 retro visible to the whole organization.”
InputsNotes:
  • At least one of name or visibility is required. A call with neither returns an error.
  • A document rename doesn’t change the document’s first heading, and permanently stops the title from following it. For example, if you rename “AEO strategy” to “AEO strategy H2”, the first heading of the document still says “AEO strategy”.
  • View-only is the sole access level that update_doc can grant to everyone at an organization. If everyone at an organization already has edit access, setting visibility to organization through MCP downgrades that access to view-only.
  • The tool works only for documents created through MCP or ones you created yourself in the Profound platform. A document shared with you, even with edit access, can’t be renamed or reshared, and only its creator can change its visibility.
Deletes a document the assistant created through an MCP connection earlier, such as a draft that turned out wrong or a duplicate. This is the one write tool with no preview mode.Example prompts:
  • “Delete the draft you created earlier, we’re keeping the final version.”
  • “That brief turned out to be a duplicate, remove it.”
InputsNotes:
  • Deletion works only for documents created through MCP, and only by their creator.
  • Deletions are final: you can’t undo them.

​
Resources