GitHub, once
Point ContextHub at the repositories your team already writes in. We sync READMEs, docs, and issues.
Shared context for AI tools
ContextHub syncs GitHub into a private team library, then lets Cursor, Claude, and other MCP clients look it up — so nobody pastes the same runbook into chat again.
MCP live path
Agents search the same private library your team already wrote down.
Connect sources once. Search them yourself. Then let coding agents use the same library over MCP.
Point ContextHub at the repositories your team already writes in. We sync READMEs, docs, and issues.
Search runbooks, APIs, and decisions from the dashboard — the same library your AI tools will use.
Create a key, paste a short config, and Cursor or Claude can look things up without leaving the workspace.
Documents and keys belong to the workspace, not a shared password. Agents never see another team’s docs.
01
Use your Google account. Each person gets their own login, then joins a shared workspace.
02
Pick the repositories to sync. ContextHub keeps the library current.
03
Create an MCP key and paste the config. Agents search and open documents in your workspace.
mcp.json
Cursor / Claude{
"mcpServers": {
"contexthub": {
"url": "https://entangleit.com/contexthub/api/mcp",
"headers": {
"Authorization": "Bearer ch_..."
}
}
}
}Your AI tools can search and open documents. Keys stay inside the workspace that created them.
Start free. Upgrade to Pro when you need more seats, sources, and MCP keys.
Free
For a small team proving the loop
Most teams
$29/month
or $290/year
The documents you sync from GitHub — READMEs, markdown, and issues — in a private team library. MCP keys can only see that workspace.
No. Sign in, connect GitHub with a personal access token, and generate an MCP key. OAuth and billing are optional upgrades.
No. Search and MCP tools are scoped to the workspace that issued the key.
Starter is free with tighter caps on seats, connectors, keys, and repositories. Pro raises those limits when the whole team is on board.