Content
View differences
Updated by Dominic Bräunlein 9 days ago
**As** an OpenProject administrator
**I want to** manage MCP settings, including naming and visibility of tools and resources
**so that** I can align AI terminology with the organization’s language and ensure secure use
<br>
**Acceptance criteria**
* A new page under Administration → Artificial intelligence (AI) → MCP.
* Link to documentation
* Admins can:
* Edit the description of the MCP server (textfield) e.g "This is the OpenProject MCP" will be described as "This is the ProjectOne MCP server" for other instances. &quot;OpenProject&quot; → &quot;ProjectOne&quot;.
* Section Tools
* OpenProject implements a set of tools which can be enabled, renamed and descriptions could be changed
* Enable + Rename Tools are e.g. searchProject, searchWorkPackage
* Display a info how renaming this tools would benefit
* TODO: Create text on why renaming is wanted
* Section Resources
* OpenProject provides a set of resources which can be enabled, renamed and descriptions could be changed
* Enable + Rename Resources are e.g. version, user
* Display a info how renaming this resources would benefit
* TODO: Create text on why renaming is wanted
* Default values for server description and tools are seeded.
* TODO: Default values are to be defined
* Changes apply dynamically with no server restart required.
<br>
**Technical notes**
* Changes reflected in /mcp/metadata and /mcp/list\_tools/resources responses.
<br>
**Permissions and visibility considerations**
* Visible only to administrators.
* Hidden when the MCP feature is globally disabled.
<br>
**Out of scope**
* Prompt management (to be added in a later iteration).
* Field-level renaming or attribute schema customization.
<br>
**I want to** manage MCP settings, including naming and visibility of tools and resources
**so that** I can align AI terminology with the organization’s language and ensure secure use
<br>
**Acceptance criteria**
* A new page under Administration → Artificial intelligence (AI) → MCP.
* Link to documentation
* Admins can:
* Edit the description of the MCP server (textfield) e.g "This is the OpenProject MCP" will be described as "This is the ProjectOne MCP server" for other instances.
* Section Tools
* OpenProject implements a set of tools which can be enabled, renamed and descriptions could be changed
*
* TODO: Create text on why renaming is wanted
* OpenProject provides a set of resources which can be enabled, renamed and descriptions could be changed
*
* TODO: Create text on why renaming is wanted
* Default values for server description and tools are seeded.
* TODO: Default values are to be defined
* Changes apply dynamically with no server restart required.
<br>
* Changes reflected in /mcp/metadata and /mcp/list\_tools/resources responses.
<br>
* Visible only to administrators.
* Hidden when the MCP feature is globally disabled.
<br>
**Out of scope**
* Prompt management (to be added in a later iteration).
* Field-level renaming or attribute schema customization.
<br>