# YDB Qdrant Code Indexer YDB Qdrant Code Indexer is a hosted GitHub App for coding agents. It indexes selected GitHub repositories into YDB-backed Qdrant-compatible vector storage and exposes searchable project memory through hosted Streamable HTTP MCP. ## Pages - [Product page](https://ydb-qdrant.tech/code-indexer/) - [Install GitHub App](https://github.com/apps/ydb-qdrant-code-indexer/installations/new) - [Dashboard](https://ydb-qdrant.tech/code-indexer/dashboard/) - [Privacy](https://ydb-qdrant.tech/code-indexer/privacy/) - [Support](https://ydb-qdrant.tech/code-indexer/support/) - [Status](https://ydb-qdrant.tech/code-indexer/status/) - [Auth and scoped access](https://ydb-qdrant.tech/docs/auth/) - [MCP server card](https://ydb-qdrant.tech/.well-known/mcp/server-card.json) - [MCP manifest](https://ydb-qdrant.tech/.well-known/mcp.json) ## What is indexed - GitHub account, installation, and repository metadata needed to show access and indexing status. - Code snippets selected by repository permissions and repository indexing configuration. - Embedding vectors generated from indexed snippets. - Search payloads used by hosted MCP code search. ## How indexing refreshes The GitHub App receives repository webhooks and refreshes indexed code chunks after pushes and pull requests. The dashboard shows repository status, chunk counts, last indexed commit SHA, active indexing jobs, and reindex controls. ## Storage and MCP Code chunks, embeddings, GitHub metadata, and search payloads live in YDB-backed Qdrant-compatible collections. Coding agents use the hosted MCP endpoint at `https://code-indexer.ydb-qdrant.tech/mcp` to list repositories, inspect repository indexes, and call `search_code` by owner, repository, and natural-language or code-oriented query. Generic MCP configuration: ```json { "mcpServers": { "ydb-qdrant-code-indexer": { "headers": { "Authorization": "Bearer " }, "url": "https://code-indexer.ydb-qdrant.tech/mcp" } } } ``` Hosted MCP exposes three read-only tools: - `list_repositories`: returns repositories available to the token, including owner, repo id, installation id, default branch, status, indexed chunk count, and last indexed SHA/time. - `list_repository_indexes`: returns the default branch index plus recent pull request indexes for one repository. - `search_code`: searches indexed chunks with `owner`, `repo`, optional `prNumber`, `query`, and `top`. ## Permissions and tokens GitHub permissions are scoped to installed repositories and cover repository metadata, contents, pull requests, and checks for indexing and repository-aware search. MCP tokens are created in the dashboard, shown once, stored as hashes, and can be revoked from the dashboard. Revoked tokens stop future hosted MCP searches. ## Beta quotas and privacy The public beta limits repository count, indexed chunks, and daily searches. Uninstalling the GitHub App or removing a repository deletes indexed collections for removed repositories. The dashboard delete-data action removes sessions, MCP/API tokens, GitHub user data, linked installation rows, repository rows, and indexed repository data where eligible.