# ctxpipe docs

> ctxpipe turns your code, tickets, and docs into one organized, current, inspectable repo that your whole agent fleet reads over MCP. Open source.

These docs tell you how to set up ctxpipe, connect your tools and your coding agents, and self-host it. Each link opens the page as Markdown. For what ctxpipe is, who it is for, and how it compares, read https://www.ctxpipe.ai/llms.txt.

## Docs

- [Getting started with ctxpipe](https://docs.ctxpipe.ai/docs/getting-started.mdx): ctxpipe keeps your engineering knowledge current in git and serves it to every coding agent over MCP.
- [Hosted quickstart](https://docs.ctxpipe.ai/docs/getting-started/quickstart.mdx): Sign up, connect GitHub, create a Workspace, and connect your coding agent.
- [Common workflows](https://docs.ctxpipe.ai/docs/getting-started/common-workflows.mdx): Where a shared, git-backed Workspace helps engineers and their coding agents.
- [Get support](https://docs.ctxpipe.ai/docs/getting-started/get-in-touch.mdx): Product, community, and open-source support channels for ctxpipe.
- [Workspaces](https://docs.ctxpipe.ai/docs/workspaces.mdx): A Workspace is a git repository of team knowledge, plus the code repositories that it searches.
- [Create a Workspace](https://docs.ctxpipe.ai/docs/workspaces/create-workspace.mdx): Choose or create the git repository that holds the knowledge of a Workspace.
- [Workspace settings](https://docs.ctxpipe.ai/docs/workspaces/settings.mdx): Manage the repositories and sources of a Workspace, and read its status, ingestion, write access, and upgrades.
- [Knowledge files](https://docs.ctxpipe.ai/docs/workspaces/knowledge-files.mdx): How Markdown files, links, and claims in the Workspace repository become search results and the knowledge graph.
- [Linked repositories](https://docs.ctxpipe.ai/docs/workspaces/linked-repositories.mdx): Add code repositories to a Workspace, so that chat and agents can search them.
- [How indexing works](https://docs.ctxpipe.ai/docs/workspaces/indexing.mdx): What ctxpipe builds after content reaches a Workspace, and how to read indexing states.
- [Workspace chat](https://docs.ctxpipe.ai/docs/workspaces/chat.mdx): Ask questions about a Workspace, change its files in a conversation, then open a pull request.
- [Knowledge graph](https://docs.ctxpipe.ai/docs/workspaces/graph.mdx): Explore the units and relationships ctxpipe built from a Workspace's files.
- [Connections](https://docs.ctxpipe.ai/docs/connections.mdx): How connections and sources bring content from your tools into a Workspace as Markdown files that you can review.
- [GitHub connector](https://docs.ctxpipe.ai/docs/connections/source-connectors/github.mdx): Connect GitHub first. It holds your Workspace repositories and gives ctxpipe access to the code that you link.
- [Linear connector](https://docs.ctxpipe.ai/docs/connections/source-connectors/linear.mdx): Mirror selected Linear teams and projects into a Workspace.
- [Notion connector](https://docs.ctxpipe.ai/docs/connections/source-connectors/notion.mdx): Mirror selected Notion pages and databases into a Workspace.
- [Confluence connector](https://docs.ctxpipe.ai/docs/connections/source-connectors/confluence.mdx): Mirror selected Confluence spaces and pages into a Workspace, through Atlassian OAuth and the ctxpipe Forge app.
- [Slack connector](https://docs.ctxpipe.ai/docs/connections/source-connectors/slack.mdx): Capture specific Slack threads into a Workspace when someone mentions the ctxpipe bot.
- [PagerDuty connector](https://docs.ctxpipe.ai/docs/connections/source-connectors/pagerduty.mdx): Mirror the incidents of selected PagerDuty services into a Workspace.
- [Buildkite connector](https://docs.ctxpipe.ai/docs/connections/source-connectors/buildkite.mdx): Connect a Buildkite organization with an API access token, and sync the latest builds of selected pipelines into a Workspace.
- [Plain connector](https://docs.ctxpipe.ai/docs/connections/source-connectors/plain.mdx): Connect Plain with a machine-user API key, and sync Help Center articles and the threads of selected labels into a Workspace.
- [Connect your agent](https://docs.ctxpipe.ai/docs/mcp/mcp-docs.mdx): Install the ctxpipe MCP in Claude Code, Cursor, Codex, OpenCode, or VS Code, with the CLI or by hand.
- [Use ctxpipe from your agent](https://docs.ctxpipe.ai/docs/mcp/use-from-your-agent.mdx): The seven read-only ctxpipe MCP tools, how an agent calls them, and how organizations and Workspaces work.
- [Connected apps](https://docs.ctxpipe.ai/docs/mcp/connected-apps.mdx): See the apps that you connected to ctxpipe with OAuth, change the organizations that each app can read, and revoke an app.
- [API keys](https://docs.ctxpipe.ai/docs/mcp/api-keys.mdx): Connect CI jobs, review bots, and other headless agents to the ctxpipe MCP with an API key.
- [Local memory](https://docs.ctxpipe.ai/docs/mcp/local-memory.mdx): How ctxpipe helps coding agents remember what your team teaches them, keep it in Git, and share it through your knowledge graph.
- [Organizations and members](https://docs.ctxpipe.ai/docs/managing-organization.mdx): Invite people to your organization, choose their roles, and see how access to content is controlled.
- [FAQ](https://docs.ctxpipe.ai/docs/resources/faq.mdx): Common questions about ctxpipe, connections, MCP, accounts, and self-hosting.
- [Data and privacy](https://docs.ctxpipe.ai/docs/resources/data-processing.mdx): How hosted ctxpipe processes your data, what you control, its sub-processors, and how it uses models.
- [Open source](https://docs.ctxpipe.ai/docs/resources/open-source.mdx): The license, the repository, and how the open-source core relates to hosted ctxpipe.

## Self hosting

- [Self-host ctxpipe](https://docs.ctxpipe.ai/docs/self-hosting.mdx): Run the open-source core of ctxpipe on your own infrastructure, and know the services and the work that you own.
- [Quickstart](https://docs.ctxpipe.ai/docs/self-hosting/quickstart.mdx): Deploy ctxpipe, set the public origin, and prove the loop from a source to an agent.
- [Architecture](https://docs.ctxpipe.ai/docs/self-hosting/architecture.mdx): Service topology and request flow for self-hosted ctxpipe.
- [Docker](https://docs.ctxpipe.ai/docs/self-hosting/deployment/docker.mdx): Run self-hosted ctxpipe with the Docker Compose deploy profile.
- [Terraform](https://docs.ctxpipe.ai/docs/self-hosting/deployment/terraform.mdx): Start from the Terraform stack of hosted ctxpipe, on Railway and Neon.
- [AWS](https://docs.ctxpipe.ai/docs/self-hosting/deployment/aws.mdx): Deploy ctxpipe on AWS with the @ctxpipe/aws-cdk CtxPipe construct.
- [Configuration](https://docs.ctxpipe.ai/docs/self-hosting/configuration.mdx): Configure Docker Compose, environment variables, and connector secrets for self-hosted ctxpipe.
- [Authentication](https://docs.ctxpipe.ai/docs/self-hosting/authentication.mdx): Establish the public auth origin, protect signing secrets, and choose sign-in methods for self-hosted ctxpipe.
- [Model configuration](https://docs.ctxpipe.ai/docs/self-hosting/models.mdx): LLM tiers, embedding models, and OpenAI-compatible providers when self-hosting ctxpipe.
- [Graph databases](https://docs.ctxpipe.ai/docs/self-hosting/graph-databases.mdx): Choose and configure an OpenCypher-compatible graph database when self-hosting ctxpipe.
- [MCP](https://docs.ctxpipe.ai/docs/self-hosting/mcp.mdx): Point MCP clients at a self-hosted ctxpipe origin, then diagnose routing and OAuth with ctxpipe doctor mcp and MCPJam.
- [Production readiness](https://docs.ctxpipe.ai/docs/self-hosting/production-readiness.mdx): Checklist for running ctxpipe behind a real public origin.
- [Operations](https://docs.ctxpipe.ai/docs/self-hosting/operations.mdx): Health checks, logs, migrations, backups, and recovery for self-hosted ctxpipe.
- [Upgrades](https://docs.ctxpipe.ai/docs/self-hosting/upgrades.mdx): Upgrade and rollback process for self-hosted ctxpipe deployments.
- [GitHub](https://docs.ctxpipe.ai/docs/self-hosting/github.mdx): Create and connect the deployment-owned GitHub App used for repository access and Git-backed connector writes.
- [Linear](https://docs.ctxpipe.ai/docs/self-hosting/linear.mdx): Register a Linear OAuth application in the product UI, or optionally set a deployment-wide app with LINEAR_* environment variables.
- [Notion](https://docs.ctxpipe.ai/docs/self-hosting/notion.mdx): Register a private Notion OAuth app in the product UI, or optionally set env as an operator shortcut.
- [Confluence & Atlassian](https://docs.ctxpipe.ai/docs/self-hosting/confluence-atlassian.mdx): Configure Atlassian OAuth, Forge provisioning, and Confluence sync for self-hosted ctxpipe.
- [Slack](https://docs.ctxpipe.ai/docs/self-hosting/slack.mdx): Configure a deployment-owned Slack app for OAuth, Events API, and intent-based thread capture.
- [PagerDuty](https://docs.ctxpipe.ai/docs/self-hosting/pagerduty.mdx): Register a PagerDuty OAuth app in the UI, or optionally via deployment env, for self-hosted ctxpipe.
- [Buildkite](https://docs.ctxpipe.ai/docs/self-hosting/buildkite.mdx): Use the Buildkite connector on a self-hosted ctxpipe. It needs no environment variables.
- [Plain](https://docs.ctxpipe.ai/docs/self-hosting/plain.mdx): Use the Plain connector on a self-hosted ctxpipe. It needs no environment variables.

## Optional

- [All docs in one file](https://docs.ctxpipe.ai/llms-full.txt)
- [ctxpipe overview](https://www.ctxpipe.ai/llms.txt): what ctxpipe is, who it is for, and how it compares
- [Source code (MIT)](https://github.com/ctxpipe-ai/ctxpipe)