Question 1

How does Dependency Context discover my project's dependencies?

Accepted Answer

It first looks for a custom `dependency-context.json` file in the project root. If not present, it falls back to scanning `package.json` (Node.js) or `requirements.txt` (Python).

Question 2

What do I need to run Dependency Context?

Accepted Answer

Node.js and npm are required. A GitHub personal access token is optional but recommended to avoid API rate limits. No external database or cloud service is needed—vector embeddings run locally.

Question 3

Where is the indexed documentation stored?

Accepted Answer

Documentation is cloned into a `dependency-context` folder within your project directory. Each dependency gets its own folder containing Markdown documentation from its repository.

Question 4

What credentials does it need?

Accepted Answer

It reads `GITHUB_TOKEN`, `MODEL_NAME`, `DEBUG`, `MIN_CHUNK_SIZE`, `MAX_CHUNK_SIZE`, `CHUNKS_RETURNED` from the environment. Store these in your client's env block or a secrets manager — never commit them to a repository — and grant the narrowest scope that still covers your use case.

Variable	Description	Required
GITHUB_TOKEN	Credential the server authenticates with.	Yes
MODEL_NAME	Configuration value read at startup.	Optional
DEBUG	Configuration value read at startup.	Optional
MIN_CHUNK_SIZE	Configuration value read at startup.	Optional
MAX_CHUNK_SIZE	Configuration value read at startup.	Optional
CHUNKS_RETURNED	Configuration value read at startup.	Optional

Dependency Context MCP Server

What is the Dependency Context MCP Server?

More MCP options

Configuration

Frequently asked questions

Alternatives to the Dependency Context MCP Server

Memory

Sequential Thinking

Agenticmemory

MCP Nutrition Tools

Aegntic MCP

Mindm