Context7
by upstash
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Computer or cloud★ 64,224MITUpdated yesterday
Install
Kika
Overview
Description from the maker (original English)
Shared memory for client engagements: decisions with reasons, blockers, promises, what was tried.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Search & AI memory
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://api.getkika.app/mcpRun this in your terminal
claude mcp add --transport http kika https://api.getkika.app/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"kika": {
"url": "https://api.getkika.app/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"kika": {
"type": "http",
"url": "https://api.getkika.app/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://api.getkika.app/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account usekika, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Search & AI memoryi
- More stars than 0% of the other 7266 servers in this category
- Published to the registry more recently than 43% of the other 7266 servers in this category
- Basic checks equal to or better than 100% of the other 7266 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Kika safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.2.4) reached the registry 2 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Context7, Codebase Memory, Exa
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Codebase Memory
by DeusData
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Runs on your computer★ 48,148MITUpdated 21 days ago
Install
Exa
by exa-labs
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Runs in the cloud★ 5,213MITUpdated last month
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Kika for Claude Code
Kika gives a project one memory that every agent and every person on it reads. What was decided and why, what is blocked, what was promised and by when, what was already tried and dropped. None of that is in the repository, and an agent cannot infer it from the code.
One install gives you both halves:
- the MCP server —
get_brief,search_memory,remember,update_memory,close_loop, so an agent can read the project's memory and add to it; and - the capture hook — which records what a turn settled without the agent having to remember to.
The hook is the part no other memory product has. A handshake that says "write things down when they matter" is advice, and a model under load ignores advice. A hook is not advice.
Install
/plugin marketplace add usekika/kika-plugin/plugin install kika@kika
Then /mcp, choose kika, and approve in the browser.
That is the whole install. The plugin carries both halves, so there is nothing to clone, no script to run, and no second credential: the hook reads the OAuth token Claude Code already holds for this server and keeps refreshed.
Projects create themselves the first time something worth remembering is said in a repository. There is nothing to set up per project.
With a token instead
For CI, or a machine with no browser. Get one at getkika.app/app/connect:
claude mcp add --scope user --transport http kika https://api.getkika.app/mcp \--header "Authorization: Bearer kika_mcp_…"
--scope user matters: without it the server is bound to the one project you happened to be in. The hook reads that same header out of your MCP configuration, so it is still one credential.
Platform note
The OAuth path is verified on macOS, where Claude Code keeps the token in the login keychain. Elsewhere the hook looks for ~/.claude/.credentials.json first, which may or may not be where your build stores it. If capture is silent on Linux or Windows, use the --header form above.
For a teammate
They install the same way and sign in as themselves. What they do in their own repositories is their own memory.
To put them on a project of yours, add them at getkika.app/app/projects — the project, then People, then the email address they sign in with. They do not need an account first; the invitation waits and is claimed the first time they sign in.
From then on their checkout of that repository resolves to *your* project rather than a second copy of it: what they decide, you read, and every fact shows who recorded it and from which branch. Everyone on a project can read and write its memory; only the owner decides who else is on it.
Until you add them, a repository that already belongs to a project is refused rather than duplicated. The agent is told the project exists, that they are not on it, and that whoever set it up can add them.
What leaves your machine
When a finished turn looks like it settled something, the hook posts to https://api.getkika.app/hooks/turn:
- the last assistant message (at most 8,000 characters) and the last message you typed (at most 4,000), keeping the end of each rather than the beginning
- the working directory, and
git remote get-url originfor it - the Claude Code session id
It does not send your source code, your environment, or any other conversation. Most turns are discarded on your machine before any request is made at all.
Once per project, when Kika first creates the project for a repository, it asks for that repository's docs so the project starts with an overview rather than an empty page. The hook then posts to https://api.getkika.app/hooks/bootstrap:
- up to 12 committed markdown files from the top two levels of the repository (README, CLAUDE.md, AGENTS.md, architecture docs first), at most 8,000 characters each. Only files
git ls-fileslists — never untracked files, never anything under a dot-directory - the subjects and dates of the last 60 commits (at most 4,000 characters)
- the working directory, git remote and branch
This happens once per project and never again.
It reads a credential in one of four places, in this order: the Authorization header you configured on the MCP server, the OAuth access token Claude Code holds for this server (macOS keychain, or ~/.claude/.credentials.json), ~/.kika/token, or ~/.kika/hooks-key. It never reads a credential belonging to any other server.
~/.kika/hooks-key exists because an OAuth access token lasts an hour and only the agent renews it — so without it, capture stopped an hour into any session where the agent did not happen to call Kika. While your OAuth sign-in is fresh, the session-start hook asks for a capture-only key once per machine and saves it there, readable only by you. The server accepts that key on the hooks and refuses it on the MCP tools, so it cannot search or read your memory beyond the session brief, and it cannot mint another key. It is listed at getkika.app/app/connect as "capture only", and revoking it there works like any key. With none of them present, capture exits immediately and sends nothing.
What it does say: once a day, at the start of a session, if no credential is found or the server rejects the one it has, you see one line — "Kika is not signed in … nothing from this session will be remembered". Capture that is off should never look like capture with nothing to save. That check runs on your machine and sends nothing but the request it was going to make anyway.
The hook runs after your turn ends and never blocks it. It exits quietly in every path, including failure: a hook that interrupts you is a hook you disable.
Seeing and undoing what it saved
getkika.app/app/trail shows every turn the hook saw, including the ones it saved nothing from and why, and what each cost you.
Anything recorded this way is marked agent-written and unverified. It can never overwrite something from one of your meetings, it never reaches your meeting notes, and every entry is listed at getkika.app/app/activity with an Undo that removes it.
Turning it off
Remove the plugin. Removing only the MCP server (claude mcp remove kika) leaves the hooks installed with no token to find: nothing is sent, and the once-a-day "not signed in" line appears until the plugin is removed too.