4
16
Fork
You've already forked app
3

Officiel MCP client. #4

Open
opened 2026年06月11日 10:26:38 +02:00 by louis2038 · 1 comment

I know the repository has only recently been published and that the current priority is probably code stabilization, but I would still like to suggest a long-term feature idea.

It would be great to have an official MCP integration, something clean and well maintained, similar to the Logseq MCP project:
https://github.com/ergut/mcp-logseq

For me, this would be a real game changer. An LLM assistant becomes far more useful when it can access and navigate a structured personal knowledge base. With an MCP integration, the model could keep contextual awareness across different sessions, explore notes through wikilinks, and even generate intermediate reports during ongoing research work.

One of the biggest strengths of this kind of workflow is that the memory becomes explicit and inspectable. Users can organize and curate their own knowledge while the assistant traverses the graph structure naturally. It also reduces manual context injection and token consumption significantly.

Thanks for your work :)

I know the repository has only recently been published and that the current priority is probably code stabilization, but I would still like to suggest a long-term feature idea. It would be great to have an official MCP integration, something clean and well maintained, similar to the Logseq MCP project: https://github.com/ergut/mcp-logseq For me, this would be a real game changer. An LLM assistant becomes far more useful when it can access and navigate a structured personal knowledge base. With an MCP integration, the model could keep contextual awareness across different sessions, explore notes through wikilinks, and even generate intermediate reports during ongoing research work. One of the biggest strengths of this kind of workflow is that the memory becomes explicit and inspectable. Users can organize and curate their own knowledge while the assistant traverses the graph structure naturally. It also reduces manual context injection and token consumption significantly. Thanks for your work :)
Owner
Copy link

@louis2038 Thank you for sending this suggestion and the Logseq example. I think you're probably right that this would be useful to people. I'll add this to the roadmap to explore. Not sure how soon I'll be able to look into it but it seems like something worth thinking about.

@louis2038 Thank you for sending this suggestion and the Logseq example. I think you're probably right that this would be useful to people. I'll add this to the roadmap to explore. Not sure how soon I'll be able to look into it but it seems like something worth thinking about.
Sign in to join this conversation.
No Branch/Tag specified
main
v26.7.3
v26.7.2
v26.6.18
v26.6.16
v26.6.14
v26.6.12
26.6.10
v26.6.10
v26.6.8
26.6.6
v26.6.2
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
InkyCap/app#4
Reference in a new issue
InkyCap/app
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?