CONNECTED AI TOOLS · DOCUMENT WRITING · TICKET ACTIONS

From a conversation to work saved in Eforge.

Connect an AI tool through MCP to explore your chosen sources, create and edit documents, and work on your own tickets. Keep the results in Eforge, with permissions and history around the work.

YOUR CONNECTED AI TOOLIllustrative example · sample content

YOU ASK

“Update the Risks section in Project kickoff, then create a follow-up ticket assigned to me.”

Personal key · Projects documents · Your own tickets

DOCUMENT UPDATEDProject kickoff

Risks section revised. Other sections preserved.

Saved in document History
TICKET CREATEDReview delivery risks

WF-142 · Assigned to you

Ready for follow-up in Eforge

Open the returned Eforge links to review the saved document and ticket.

INSIDE THE WORKSPACE

Bring your AI tool into the context of your work.

01

Find the context

Read selected documents, search records, explore data grid rows, and review your own tickets before deciding what to do next.

02

Put the work in place

Create a document, refine a section, open a follow-up ticket, or post a progress update. The tool returns links to the results in Eforge.

03

Keep control

Choose document-writing sources, use your existing permissions, and review agent changes. Workspace owners can stop all agent writing at once.

DOCUMENTS FROM THE CONVERSATION

Write it where your team can use it.

Turn meeting notes into an editor document in a chosen vault. Add a conclusion, revise a named section, or replace a draft when that is what you ask for. Your AI tool works with the saved document and returns its Eforge link.

  • Create documents and optionally place them in a folder or dataset
  • Append, prepend, revise a section, or replace document content
  • Read the latest revision before editing; changes are refused while someone has the editor open
  • Review each agent edit in History and restore an earlier version

FOLLOW-UP WITHOUT LOSING THE THREAD

Keep your own tickets moving.

Ask your connected tool to create a ticket, update its status, assign the next step, or change its due date. Post a progress message or reply to an existing discussion thread on tickets you created or are assigned to.

  • Create and update titles, descriptions, priorities, statuses, and due dates
  • Add or remove assignees, tags, and links to readable items
  • Post discussion messages as you; ticket field changes identify the agent key in History
  • Return to the ticket through its reference and Eforge link

ACCESS YOU CAN DEFINE

Your permissions travel with the key.

Connect a compatible MCP client through Eforge sign-in or an agent key. Personal keys include your own tickets and can write documents only in selected sources you can edit. Shared keys remain read-only and never include tickets.

  • Grant regular members personal-key access individually
  • Choose document-writing sources separately from reading sources
  • Set expiry and lower usage limits; disconnect apps or revoke keys
  • Turn off all agent writing from Workspace Configuration while permitted reads continue

PUT IT IN CONTEXT

Turn a project review into a brief and a next step.

Ask your AI tool to read the project material, save a summary in an allowed vault, and create a ticket assigned to you for an open question. Review the document and ticket in Eforge, then ask for a discussion update as the work progresses.

  1. 1Read the selected sources
  2. 2Save the document
  3. 3Create and follow up on your ticket

Agent access currently requires a Business workspace. Document writes use Markdown; tables and mentions are not supported, and rewritten text may lose rich formatting. Agent tools cannot delete documents, tickets, or discussion messages. Review saved results; ticket history has no automatic restore.

MAKE ROOM FOR DEEPER UNDERSTANDING

Meet your next information workspace.

Join the early-access list