Summary
The distinctive axis is the user one: it answers who has been shaping an entry and what else they have touched, over a window you set.
Search and single-wiki retrieval are the ordinary half. What is less common is that creation and editing are separate queries against a user id bounded by timeFrameSeconds, with GET_USER_WIKI_ACTIVITIES folding them together behind an activityType. That makes a provenance question answerable rather than guessable — not only what an entry says, but who has been writing it and how recently. Everything in this set reads; nothing here creates or edits a wiki.
What it is
A read-only IQ.wiki client with five tools covering search, a single wiki by id, and a user's created, edited and combined wiki activity.
What you get
- Search and read: SEARCH_WIKI finds wikis matching a query, GET_WIKI returns one by its id.
- Contribution history by user: GET_USER_CREATED_WIKIS and GET_USER_EDITED_WIKIS each take a user id with a timeFrameSeconds window, and GET_USER_WIKI_ACTIVITIES returns creations or edits together, selected by activityType.
Requirements
No credentials are configured on the server.
Setup effort
One command — npx -y @iqai/mcp-iqwiki