Skip to main content
Connect your coding assistant to the hosted workspace from MCP in Graphify. This lets the assistant use your Graphify context while you work in its editor or terminal.

​
Connect a coding assistant

  1. Open the workspace’s MCP page or choose Connect agent from Overview.
  2. Choose your client and follow its setup instructions.
  3. Complete the Graphify sign-in and select the intended workspace when prompted.
  4. Return to the assistant and confirm that its Graphify connection is available.
The website’s MCP client guide includes instructions for Claude Code, Codex, Cursor, GitHub Copilot, and other clients.

​
Shared knowledge alongside your own memory

Your agent can keep its own preferences and session memory. Graphify adds shared knowledge connected to your repositories, with sources and history that authorized agents and teammates can inspect. It does not automatically synchronize with another memory store. After connecting, try one source-linked question about a repository you work on. For implementation tasks, include the files you are changing so supported contextual guidance can point to relevant reusable code. When available, graphify_patterns lets you inspect examples explicitly. Follow the tools and readiness returned by your authenticated connection. Personal suggestion settings apply only when Graphify can identify the current human member reliably. Service and shared credentials use workspace controls and neutral personalization.

​
Hosted and local MCP

The hosted connection uses your Graphify identity and workspace access. A local graphify-mcp process reads a graph on your machine. Follow Local MCP server when you want that local workflow. To search this documentation from an assistant, use the separate docs search MCP.

​
Other workspace integrations

Integrations lists the connections available to the workspace. The console currently labels that area Early access; follow the status and setup flow displayed for each provider. Repository-provider connections begin in Repositories. Google Drive is connected from Connectors. Follow Connect Google Drive. Account and organization controls live in the user menu, including Settings, Billing, and Members where available.

​
Buildkite test selection

Connect BuildKite (Test Impact) from Integrations to run tests affected by a pull request. A workspace owner or admin creates a CI token; your Buildkite pipeline sends the commit range and uploads the returned test steps. Follow the Buildkite integration guide for token setup, a working pipeline example, full-suite fallback, and troubleshooting. The optional Show test selection on pull requests switch adds advisory review context; it does not run or gate tests.

​
Connection troubleshooting

Check that you signed in to the intended workspace and that the repository has finished indexing. If the assistant reports an authorization problem, refresh its Graphify sign-in. For client-specific configuration, return to the MCP guide.

​
Next steps

Trace who calls this

Ask your agent what a change affects.

Agent memory

Memory your agents share.

When something fails

Fix sign-in and connection problems.