> ## Documentation Index > Fetch the complete documentation index at: https://docs.graphify.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > The PyPI package is graphifyy, with two y's. The command is graphify. > /graphify . is typed in an assistant chat, not in a shell. > Use only commands, flags, and endpoints shown on these pages. Do not invent one. > Choose the surface before you open a page. Local (Graphify Local) is the graphifyy package on the machine: the skill, the CLI, and the ten-tool MCP. Its pages are the Open Source tab (/open-source/) and the Graphify Local tab on each Integrations page. Graphify is the hosted workspace and https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key). Its pages are the Graphify tab (/platform/, /concepts/) and the Graphify (hosted) tab on each Integrations page. Prefer Graphify unless the user asks for a local or offline setup. Cookbooks (/cookbooks/) and /mcp/docs-search apply to both. Each page's source frontmatter records this as surface: local, cloud, or both. Buildkite is the CI integration. > In llms.txt, tell the surface from the page path. Graphify: /platform/ and /concepts/. Local: /open-source/. Most /integrations/ pages cover both, with a Graphify (hosted) tab and a Graphify Local tab. Everything else applies to both. > graphifyy release notes are published at https://github.com/Graphify-Labs/graphify/releases and https://graphify.com/changelog. The current package version is on PyPI (https://pypi.org/project/graphifyy/). > The official site is https://graphify.com. These docs are https://docs.graphify.com. > The local MCP server is the ten tools in the MCP tool reference and reads a graph on the machine. The hosted server is https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key). The JetBrains, ChatGPT, Codex, and Dots, and Vercel pages use the hosted server, not the ten-tool list. On pages with tabs, the Graphify (hosted) tab uses the hosted server and the Graphify Local tab uses the local skill or the ten-tool server. > Read https://docs.graphify.com/llms.txt, then open one page's .md link. Use https://docs.graphify.com/llms-full.txt only when one page is not enough. # Connectors > Connect coding agents over MCP and connect source providers, docs, issue trackers, and CI to Graphify from the Connectors page in the Console. **Connectors** is where you connect Graphify to the rest of your tools. It has two tabs: **MCP**, for coding agents, and **Integrations**, for source providers, knowledge sources, issue trackers, and CI. Connected sources give reviews and answers more context; none of them gives a verdict on their own. > [!NOTE] > > **Use Connectors when** you're setting up an agent, connecting a code provider, or creating a token for a pipeline. ## Before you start * A Graphify account at [app.graphify.com](https://app.graphify.com). * For workspace tokens, owner or admin rights. Other members need to ask an owner or admin. ## The MCP tab Pick your coding agent and follow its setup. The tab fills in your endpoint and shows the config file to edit. See [Hosted MCP](https://docs.graphify.com/platform/hosted-mcp.md) for each client. ## The Integrations tab Integrations are grouped by category. Use **Filter integrations** to find one. | Category | Examples on the page | | - | - | | Source control | GitHub and GitLab connections clone for indexing, receive review events, and post results. | | Knowledge | Documents from Google Drive and other team doc stores. | | Project management | Issue context for pull requests. | | Communication | Sharing reviews and questions in channels. | | Developer tools | Workspace API tokens, error tracking, and CI test selection. | Which integrations you can connect depends on your workspace. Tiles that aren't available yet are marked as coming. ## Create a workspace token Some integrations, such as a CI pipeline, authenticate with a workspace token instead of a sign-in. **1. Open API Token** In **Integrations**, open **API Token** and select **Generate a token**. **2. Copy it now** The token is shown once. Copy it straight into your secret store. **3. Rotate when needed** Replacing a token revokes the current one. Update your pipeline secret afterwards. > [!WARNING] > > Never commit a token to a repository or paste it into a chat. Store it as a CI secret. ## Connect a code provider The top of **Integrations** lists your code providers: | Provider | Tile text | What it does | | - | - | - | | GitHub | Sync repositories and pull requests. | Installs the Graphify GitHub App. After that, **Manage installation on GitHub** chooses which repositories Graphify can see. | | GitLab | Sync repositories and merge requests. | Connects your gitlab.com account. Self-managed GitLab isn't supported. | Once a provider is connected, its tile shows **Connected** and the button changes to **Manage**. Graphify clones the repositories you grant, indexes them, gets review events, and posts results back. ## Connect Google Drive **1. Open the Google Drive tile** In **Integrations**, find **Google Workspace · Google Drive** ("Search documents from Google Drive.") and select **Connect Google Drive**. **2. Sign in with Google** Select **Continue to Google**. Access is read-only: Graphify never edits your files. **3. Choose a folder** Select **Choose a Drive folder**, then **Add this folder**. Its documents become searchable in Graphify, and the tile shows **Connected · Syncs automatically**. Supported files: Google Docs, Sheets and Slides, plus PDF, Word, Excel, PowerPoint, CSV, Markdown, text and image files. Files that can't be read are listed in the folder details. Adding folders needs a paid plan, and only an owner or admin can connect Drive. If you switch to a different Google account, the folders from the old account stop syncing and you need to add them again. ## Connect Vercel The Vercel integration connects an existing Graphify workspace to your Vercel projects. Your plan, usage and billing stay with Graphify. **1. Install from Vercel** Add the Graphify integration in Vercel. You're sent to **Connect your codebase context**. **2. Choose your Graphify workspace** Pick a workspace where you're an owner or admin. If you don't have one, select **Create a workspace**. **3. Choose projects to connect** Select the projects. Production deployments receive the connection. Turn on **Also allow preview deployments** only for projects whose preview code you trust. Each connected project gets two environment variables: | Variable | Value | | - | - | | `GRAPHIFY_MCP_URL` | The hosted Graphify MCP endpoint for this project. | | `GRAPHIFY_MCP_TOKEN` | A project token. Send it as a Bearer token from server-side code only. | Disconnecting a project revokes its token right away. Removing the integration in Vercel revokes all of its project tokens. ## Coming soon Microsoft Workspace, Confluence and Linear show as **Coming soon**. Jira, Sentry, Slack and Buildkite (Test Impact) also show **Coming soon** until they're turned on for your workspace. ## Verify and troubleshoot | Symptom | Fix | | - | - | | **Reconnect needed** | The provider's access expired. Reconnect it from the tile. | | You can't create a token | Ask your team owner or an admin. | | Repositories missing after connecting GitHub | Use **Manage installation on GitHub** to grant the repositories. | | A draft fix can't be opened | Grant GitHub write access, then select **I've granted access. Re-check**. | | **Google access expired. Reconnect to keep folders in sync.** | Select **Reconnect Google Drive**. Existing graphs stay available. | | **Add Google Drive folders with a paid plan.** | Folders need a paid plan. Check **Billing**. | | **No admin workspaces are available.** (Vercel) | You need to be an owner or admin of a workspace. Create one or ask to be made admin. | | **No projects are available.** (Vercel) | Update the integration's project access in Vercel, then reopen **Configure**. | | **Access revoked. Vercel variable cleanup is pending** | Retry cleanup, or remove the Graphify variables in Vercel by hand. | > **Where is Google Drive set up?** > > See [Google Drive](https://docs.graphify.com/integrations/google-drive.md). > **Where do I manage connected repositories?** > > In **Repositories**. See [Repositories](https://docs.graphify.com/platform/repositories.md). > **Does GitLab self-managed work?** > > Not yet. Only gitlab.com is supported. > **Can Graphify change my Drive files?** > > No. Drive access is read-only. ## What's next > **[Hosted MCP](https://docs.graphify.com/platform/hosted-mcp.md)** > > Connect a coding agent. > **[Pull request reviews](https://docs.graphify.com/platform/reviews.md)** > > What connected providers make possible. > **[Connect your agent](https://docs.graphify.com/platform/connections.md)** > > Add the hosted MCP at `api.graphify.com/mcp`. Sign in with OAuth, no API key. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.