Wiki access

[robbiemu]

Describe the feature or problem you’d like to solve

I would like to be able to provide access directly to my project's wiki in the mcp server.

Proposed solution

it is probably conceptually beneficial to group repo wiki access in the same place you provide other access to the repo (rather than needing to set up a web tool, etc, and hoping the agent recognizes the full relationship). Retrieving the same via https://github.com/search?q=repo%3Aorg%2Frepo+search_term&type=wikis adds a lot of junk in the context that the agent then needs to responsibly compact.

The repo's wiki is not currently accessible using search_code, at least not by any combination of "repo:org/repo.wiki" or "type:wiki" or "type:wikis"

Example prompts or workflows (for tools/toolsets only)

Git Repository Operations:

Tools to clone and interact with the wiki repo:

• clone_wiki_repository: Clone the wiki repo locally for full access
• list_wiki_pages: Parse directory contents to list available pages
• get_wiki_page_content: Retrieve raw markdown content of specific pages
• search_wiki_content: Implement local search functionality across cloned wiki content

Wiki Management Tools:

Page Operations:

• create_wiki_page: Create new wiki pages
• update_wiki_page: Modify existing wiki pages
• delete_wiki_page: Remove wiki pages

[nicusbonannus]

Any news about this feature?

[nils-kt]

Any news about this feature?

Yes, it would be really helpful if they actually implemented that...

[tommaso-moro]

Hi @robbiemu thank you for sharing this. Unfortunately, it looks like there are no APIs to get a repository's wiki so there is not much that can be done here on our side to implement these tools.

I am closing this issue for now and will be keeping an eye out for updates on this front from the official GitHub API. Feel free to get in touch if you think this should be re-opened!

[robbiemu]

Hi @tommaso-moro I think you are wrong? That thread says basically it was not added to another API (the api.github.../repos/ api). but there is the Git transfer protocol:

git ls-remote https://$GH_PUBLIC_REPOS@github.com/robbiemu/aclarai.wiki.git
359004105dd97183c4c2feaeb0948f52d85d0573	HEAD
359004105dd97183c4c2feaeb0948f52d85d0573	refs/heads/master

petition to reopen

[tommaso-moro]

Thank you for your reply @robbiemu I am reopening this while we investigate this possibility. Will keep you posted on this!

[Jikodis]

Thank you for your reply @robbiemu I am reopening this while we investigate this possibility. Will keep you posted on this!

This sounds like it would be very useful. Our main use case is AI searchable docs for internal team repos. Currently our docs are in a GitHub repo in markdown, and developers can search our docs using the #githubRepo tool in GitHub Copilot chat. It actually works really well.

GitHub Copilot Spaces look interesting, but the docs on them specifically call out that they are not for large amounts of context, and are limited in that way. Some of our documentation is pretty comprehensive.

Alternatives are custom RAG solutions or expensive cloud solutions like Confluence Cloud with Rovo. Being able to stay within the GitHub ecosystem for AI searchable documentation would be ideal.