Back to MCP Servers
🧩

Gemdex MCP Server

API key required

Persistent memory layer for AI coding agents: save, recall, update via Gemini plus LanceDB

To add Gemdex to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs 8 environment variables, listed below.

AIDevTools

Install

npx -y gemdex-mcp@1.0.47

Environment variables

GEMINI_API_KEYSet in your MCP config
GEMDEX_MODESet in your MCP config
LANCEDB_PATHSet in your MCP config
EMBEDDING_MODELSet in your MCP config
GEMDEX_REMOTE_URLSet in your MCP config
GEMDEX_REMOTE_TOKENSet in your MCP config
GEMDEX_REMOTE_NAMESet in your MCP config
GEMDEX_TRUST_RANKINGSet in your MCP config

Install with your client

Terminal
claude mcp add gemdex --env GEMINI_API_KEY=<YOUR_GEMINI_API_KEY> --env GEMDEX_MODE=<YOUR_GEMDEX_MODE> --env LANCEDB_PATH=<YOUR_LANCEDB_PATH> --env EMBEDDING_MODEL=<YOUR_EMBEDDING_MODEL> --env GEMDEX_REMOTE_URL=<YOUR_GEMDEX_REMOTE_URL> --env GEMDEX_REMOTE_TOKEN=<YOUR_GEMDEX_REMOTE_TOKEN> --env GEMDEX_REMOTE_NAME=<YOUR_GEMDEX_REMOTE_NAME> --env GEMDEX_TRUST_RANKING=<YOUR_GEMDEX_TRUST_RANKING> -- npx -y gemdex-mcp@1.0.47

Run this in a terminal to add the server to Claude Code.

What this does

Gemdex exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

GEMINI_API_KEY
GEMDEX_MODE
LANCEDB_PATH
EMBEDDING_MODEL
GEMDEX_REMOTE_URL
GEMDEX_REMOTE_TOKEN
GEMDEX_REMOTE_NAME
GEMDEX_TRUST_RANKING

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Frequently asked questions

How do I install Gemdex?

Run the Claude Code command in the install section to add Gemdex to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Gemdex?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Gemdex as well.

Does Gemdex need an API key?

Yes. Before it can run, set these environment variables: GEMINI_API_KEY, GEMDEX_MODE, LANCEDB_PATH, EMBEDDING_MODEL, GEMDEX_REMOTE_URL, GEMDEX_REMOTE_TOKEN, GEMDEX_REMOTE_NAME, GEMDEX_TRUST_RANKING. They go in the env block of your MCP config.

Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.

Is this your MCP server?

Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.

Listed on clauderules.net

Add this badge to your README

Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.

Markdown
[![Listed on clauderules.net](https://clauderules.net/api/badge/io-github-nikships-gemdex)](https://clauderules.net/mcp/io-github-nikships-gemdex)
HTML
<a href="https://clauderules.net/mcp/io-github-nikships-gemdex" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-nikships-gemdex" alt="Listed on clauderules.net" /></a>