Enables AI agents to manage knowledge through graph-native memory, hybrid RAG, and codebase indexing.
Também conhecido como GCTRL-TECH/platform, gctrl-mcp
- Stars
- 7
- Ferramentas
- 23
- Downloads, 30 dias
- —
- Versão mais recente
- 1.2.0
- Último commit
- 6 de nov. de 2026
- Licença
- AGPL-3.0
O que é o MCP Ground Control?
Ground Control é um MCP server. Enables AI agents to manage knowledge through graph-native memory, hybrid RAG, and codebase indexing. Ele expõe 23 ferramentas, como gctrl_extract, gctrl_query, gctrl_search_entities.
Resumo gerado a partir do README do projeto
Sobre o MCP server de Ground Control
Ground Control provides a specialized knowledge management system for AI agents using graph-native memory and hybrid RAG. It allows agents to extract knowledge from text into Neo4j entities and Qdrant vectors, or manage structured information similar to Obsidian notes through the gctrl_store tool. The server functions as an authenticated proxy to a GCTRL harness, requiring a GCTRL_API_TOKEN and a GCTRL_GATEWAY_URL for connection.
Developers can use the server in direct mode to index local repositories into a codebase knowledge base. This mode utilizes the gctrl_code_index tool and requires the optional gctrl-code-indexer package to function. Once indexed, agents can navigate code structures using gctrl_code_symbol, gctrl_code_trace, and gctrl_code_architecture. This approach enables agents to perform impact analysis with gctrl_code_impact and query complex relationships through the knowledge graph, significantly reducing token usage compared to traditional text searching.
O que você pode fazer com ele
- 1Extract structured knowledge from textAn agent can transform raw text into organized entities and vectors within a knowledge graph.
- 2Analyze code change impactsA developer can ask an agent to determine how changing a specific symbol will affect the rest of the codebase.
- 3Perform hybrid RAG queriesUsers can ask complex questions that combine graph-based relationships with vector search.
Escrito a partir do README do projeto. Cada caso de uso é verificado com uma citação dele.
Como instalar o MCP Ground Control
Formatos verificados em 10 nov 2026Adicionar ao CursorAdicionar ao GooseInstalar o MCP Ground Control no Claude Code
$ claude mcp add --env 'GCTRL_API_TOKEN=<YOUR_GCTRL_API_TOKEN>' gctrl -- npx -y gctrl-mcpInstalar o MCP Ground Control no Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"gctrl": {
"command": "npx",
"args": [
"-y",
"gctrl-mcp"
],
"env": {
"GCTRL_API_TOKEN": "<YOUR_GCTRL_API_TOKEN>"
}
}
}
}Instalar o MCP Ground Control no VS Code
.vscode/mcp.json
{
"servers": {
"gctrl": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"gctrl-mcp"
],
"env": {
"GCTRL_API_TOKEN": "<YOUR_GCTRL_API_TOKEN>"
}
}
}
}Instalar o MCP Ground Control no VS Code CLI
$ code --add-mcp '{"name":"gctrl","type":"stdio","command":"npx","args":["-y","gctrl-mcp"],"env":{"GCTRL_API_TOKEN":"<YOUR_GCTRL_API_TOKEN>"}}'Instalar o MCP Ground Control no Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"gctrl": {
"command": "npx",
"args": [
"-y",
"gctrl-mcp"
],
"env": {
"GCTRL_API_TOKEN": "<YOUR_GCTRL_API_TOKEN>"
}
}
}
}Instalar o MCP Ground Control no Codex
$ codex mcp add gctrl --env 'GCTRL_API_TOKEN=<YOUR_GCTRL_API_TOKEN>' -- npx -y gctrl-mcpInstalar o MCP Ground Control no Codex config.toml
~/.codex/config.toml
[mcp_servers.gctrl] command = "npx" args = ["-y", "gctrl-mcp"] [mcp_servers.gctrl.env] GCTRL_API_TOKEN = "<YOUR_GCTRL_API_TOKEN>"
Instalar o MCP Ground Control no Gemini CLI
$ gemini mcp add -s user -e 'GCTRL_API_TOKEN=<YOUR_GCTRL_API_TOKEN>' gctrl npx -- -y gctrl-mcpInstalar o MCP Ground Control no Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"gctrl": {
"command": "npx",
"args": [
"-y",
"gctrl-mcp"
],
"env": {
"GCTRL_API_TOKEN": "<YOUR_GCTRL_API_TOKEN>"
}
}
}
}Ferramentas do MCP Ground Control 23
Detectadas a partir do READMEgctrl_extractgctrl_querygctrl_search_entitiesgctrl_list_graphsgctrl_fusegctrl_list_ontologiesgctrl_list_extractionsgctrl_storegctrl_schemagctrl_code_indexgctrl_code_symbolgctrl_code_trace
| gctrl_extract | — | |
| gctrl_query | — | |
| gctrl_search_entities | — | |
| gctrl_list_graphs | — | |
| gctrl_fuse | — | |
| gctrl_list_ontologies | — | |
| gctrl_list_extractions | — | |
| gctrl_store | — | |
| gctrl_schema | — | |
| gctrl_code_index | — | |
| gctrl_code_symbol | — | |
| gctrl_code_trace | — |
Mostrar todas as 23 ferramentasMostrar menos ferramentas
gctrl_code_impactgctrl_code_architectureborghive_extractborghive_queryborghive_storeborghive_fuseborghive_search_entitiesborghive_list_graphsborghive_list_ontologiesborghive_list_extractionsborghive_schema
| gctrl_code_impact | — | |
| gctrl_code_architecture | — | |
| borghive_extract | — | |
| borghive_query | — | |
| borghive_store | — | |
| borghive_fuse | — | |
| borghive_search_entities | — | |
| borghive_list_graphs | — | |
| borghive_list_ontologies | — | |
| borghive_list_extractions | — | |
| borghive_schema | — |
Configuração
GCTRL_API_TOKENObrigatórioSecretoScoped GCTRL Access Token (gctrl_…) created in Settings → Access Control
GCTRL_API_URLDirect GCTRL API base URL (alternative to gateway mode), e.g. http://localhost:4000/api
GCTRL_CODE_AUTO_INDEXGCTRL_GATEWAY_URLURL of your GCTRL harness MCP gateway, e.g. http://localhost:4000/api/agent/mcp (recommended mode)
GCTRL_MCP_TOOLS
| Nome | Descrição | Tipo |
|---|---|---|
| GCTRL_API_TOKEN | Scoped GCTRL Access Token (gctrl_…) created in Settings → Access Control | ObrigatórioSecreto |
| GCTRL_API_URL | Direct GCTRL API base URL (alternative to gateway mode), e.g. http://localhost:4000/api | |
| GCTRL_CODE_AUTO_INDEX | — | |
| GCTRL_GATEWAY_URL | URL of your GCTRL harness MCP gateway, e.g. http://localhost:4000/api/agent/mcp (recommended mode) | |
| GCTRL_MCP_TOOLS | — |
Verificações automatizadas
Executado em 12 de nov. de 2026Relatório completo →Passou em nossas verificações automatizadas. Isso não é uma auditoria de segurança: leia o código e dê ao servidor o acesso mais restrito de que ele precisa. Como as verificações funcionam
- Repositório de origem vinculado e acessívelPassou
- Licença de código aberto (OSI)Passou
- Commit ou release no último anoPassou
- Nome do pacote não é próximo a um pacote popularPassou
- O endpoint remoto usa HTTPSNão verificado
- Ferramentas destrutivas estão rotuladasPassou
- Sem instruções ocultas para o modeloPassou
- Nenhum aviso crítico no pacote ou em suas dependênciasPassou
README
Ver no GitHubGround Control (GCTRL) MCP Server
Exposes Ground Control's knowledge management as MCP tools for Claude and other AI agents.
Tools Available
| Tool | Description |
|---|---|
gctrl_extract |
Extract knowledge from text → Neo4j entities + Qdrant vectors |
gctrl_query |
Ask questions about knowledge graphs (hybrid RAG) |
gctrl_search_entities |
Search for specific entities by name/type |
gctrl_list_graphs |
List all knowledge graph compilations |
gctrl_fuse |
Merge extraction jobs into unified graphs |
gctrl_list_ontologies |
List available ontologies |
gctrl_list_extractions |
List recent extraction jobs |
gctrl_store |
Store knowledge (like Obsidian notes, but with KG extraction) |
gctrl_schema |
Get the knowledge graph schema |
gctrl_code_index |
Index a local repo into a Codebase KB (compilation type CODE). Direct mode only (it indexes THIS machine, so a gateway cannot serve it) and needs the optional gctrl-code-indexer package - without it the tool returns an install hint and every other tool keeps working. |
gctrl_code_symbol |
Find code symbols by name/path/regex (proxied to the HTTP gateway) |
gctrl_code_trace |
Trace callers/callees of a symbol (proxied to the HTTP gateway) |
gctrl_code_impact |
Impact analysis for changed symbols/files (proxied to the HTTP gateway) |
gctrl_code_architecture |
Languages, hotspots, communities for a Codebase KB (proxied to the HTTP gateway) |
Deprecated names (alias, removal in v2)
Every tool above is also exposed under its legacy name for backwards
compatibility with existing .mcp.json configs. The aliases log a
deprecation warning to stderr on every invocation and will be removed
in v2.0 — please migrate.
| Deprecated alias | Use instead |
|---|---|
borghive_extract |
gctrl_extract |
borghive_query |
gctrl_query |
borghive_store |
gctrl_store |
borghive_fuse |
gctrl_fuse |
borghive_search_entities |
gctrl_search_entities |
borghive_list_graphs |
gctrl_list_graphs |
borghive_list_ontologies |
gctrl_list_ontologies |
borghive_list_extractions |
gctrl_list_extractions |
borghive_schema |
gctrl_schema |
Quickstart (npm)
Published on npm as gctrl-mcp and in the
official MCP Registry as io.github.GCTRL-TECH/gctrl. Add to your MCP client config
(Claude Code, Claude Desktop, Cursor, Codex, …):
{
"mcpServers": {
"gctrl": {
"command": "npx",
"args": ["-y", "gctrl-mcp"],
"env": {
"GCTRL_GATEWAY_URL": "http://localhost:4000/api/agent/mcp",
"GCTRL_API_TOKEN": "gctrl_..."
}
}
}
}
Requires a running GCTRL harness (get started).
Coding with GCTRL (recommended for coding agents)
Run the server in direct mode next to your gateway entry so the agent gets the local code tools, and let it keep the repository's Codebase KB current on its own:
{
"mcpServers": {
"gctrl": { "command": "npx", "args": ["-y", "gctrl-mcp"],
"env": { "GCTRL_GATEWAY_URL": "https://<host>/api/agent/mcp", "GCTRL_API_TOKEN": "gctrl_..." } },
"gctrl-code": { "command": "npx", "args": ["-y", "gctrl-mcp"],
"env": { "GCTRL_API_URL": "https://<host>/api", "GCTRL_API_TOKEN": "gctrl_...",
"GCTRL_MCP_TOOLS": "code", "GCTRL_CODE_AUTO_INDEX": "cwd" } }
}
}
With GCTRL_CODE_AUTO_INDEX=cwd the server indexes the directory the MCP client launched it
in (incremental - a warm repo takes seconds) right after start-up, and the agent's first
gctrl_code_symbol hits a current graph. The server's instructions carry the coding
protocol every connected agent follows: index once per session, navigate through
gctrl_code_symbol / gctrl_code_trace / gctrl_code_architecture BEFORE reading files,
run gctrl_code_impact before changing a symbol, re-index after larger edits, ask
gctrl_query for the why and store decisions next to the symbols with gctrl_store.
Measured on GCTRL's own repository: structural questions answered through the graph used
95.6 % fewer tokens than grep-and-read.
Configuration
| Env var | Purpose |
|---|---|
GCTRL_GATEWAY_URL |
Recommended: URL of your harness's MCP gateway (http://<host>:4000/api/agent/mcp). The stdio server acts as a thin authenticated proxy. |
GCTRL_API_URL |
Alternative direct mode: GCTRL API base URL (http://<host>:4000/api); tools run locally against the API. |
GCTRL_API_TOKEN |
Scoped GCTRL Access Token (gctrl_…), created in Settings → Access Control with a clearance level + per-graph grants. Least privilege — the agent sees exactly what the token is cleared for. |
GCTRL_MCP_TOOLS |
Optional tool-set filter. Set to code to register only the local code tools (gctrl_code_index, gctrl_code_symbol, gctrl_code_trace, gctrl_code_impact, gctrl_code_architecture) — used for the Anvil/Hermes gctrl-code stdio entry, kept separate from the HTTP-gateway gctrl/gctrl-projekt entries. Direct mode only: in gateway mode the gateway's own tool list is proxied verbatim, so the filter has no effect and the server says so on startup. |
| GCTRL_CODE_AUTO_INDEX | Direct mode: cwd (or a repository path) indexes that repository in the background right after start-up - incremental, never fatal. Makes the Codebase KB automatic instead of a habit. |
| GCTRL_CODE_COMPILATION_ID | Direct mode: the CODE compilation gctrl_code_index uses when the agent passes none (one project = one repo = one code graph). An explicit compilationId from the agent still wins. |
| GCTRL_CODE_FOLDER | Direct mode: folder path (Users/<name>/Code) for a code graph the server auto-creates as <repo> (code). Hosts that launch the server per user (Anvil) set it so every colleague's code lands in their own folder; without it GCTRL files under the account owner's Users/<owner>/Code. |
Dev-only fallback: GCTRL_EMAIL + GCTRL_PASSWORD (full-clearance JWT). Avoid in production.
Build from source
cd borghive/services/mcp
npm install
npm run build
Working on the code indexer
gctrl-code-indexer is an optional dependency and is not on npm yet, so a plain
npm install here will not fetch it. To develop or test gctrl_code_index against the
in-repo package, link it once:
cd borghive/packages/code-indexer && npm ci && npm run build
cd ../../services/mcp && npm install ../../packages/code-indexer --no-save
# or: npm link ../../packages/code-indexer
The server's types for the indexer are declared locally, so npm run build passes with
or without the package installed - the difference is only whether gctrl_code_index
works at runtime or returns its install hint.
Publish order
gctrl-mcp and gctrl-code-indexer are two npm packages and must go out in this order:
- Publish
gctrl-code-indexer@0.1.0. - Switch
optionalDependenciesinservices/mcp/package.jsonto a real registry range (it already reads^0.1.0; confirm it resolves) and re-runnpm install. - Bump
gctrl-mcpto1.1.0(package.json + package-lock.json root). - Publish
gctrl-mcp.
Bumping gctrl-mcp BEFORE the indexer is on npm would break npx gctrl-mcp for every
existing user - which is exactly why the version sits at 1.0.1 today.
Perguntas sobre o MCP Ground Control
Como adiciono o MCP Ground Control ao Claude Code?
Execute claude mcp add --env 'GCTRL_API_TOKEN=<YOUR_GCTRL_API_TOKEN>' gctrl -- npx -y gctrl-mcp no seu terminal. Adicione --scope user para torná-lo disponível em todos os projetos.
Como adiciono o MCP Ground Control ao Cursor?
Abra ~/.cursor/mcp.json e adicione o servidor em mcpServers, usando a configuração do Cursor mostrada na seção de instalação acima.
Quais ferramentas o MCP Ground Control oferece?
Ele expõe 23 ferramentas, incluindo gctrl_extract, gctrl_query, gctrl_search_entities, gctrl_list_graphs, gctrl_fuse.
How can I use GCTRL for coding tasks?
You can run the server in direct mode to provide local code tools like symbol searching, tracing, and impact analysis for your repository.
What is required to use the gctrl_code_index tool?
The tool requires the optional gctrl-code-indexer package to be installed; otherwise, it will return an install hint.
How does the security model work for GCTRL?
It uses scoped GCTRL Access Tokens with specific clearance levels and per-graph grants to ensure the agent only sees authorized data.