nextcloud / nextcloud/context_agent
MCP for individual users set in user settings
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24
- Forks
- 16
- Avg merge
- 7d 20h
- Merged PRs (30d)
- 3
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Feature request
Which Nextcloud Version are you currently using:
32
Is your feature request related to a problem? Please describe.
Users can have access to individual MCP servers with different credentials than other users.
Describe the solution you'd like
It would be fantastic if the user is able to set its own .json file with MCP servers specifications. Currently only the administrator is able to set MCPs to share between users with the same credentials for all users.
Describe alternatives you've considered
There is no alternative.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing administrator MCP configuration and the user settings entry point; inspect how shared .json server specifications and credentials are loaded. The issue is complete when users can define their own MCP server specifications and credentials without changing the administrator's shared configuration, with access isolated per user.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100