# Graphify MCP server > Search indexed code, trace callers and dependencies, assess change impact, and recall repository memory. - Listing: https://mcp.tc/i/graphify - Connect: use the server's own URL `https://api.graphify.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Developer Tools](https://mcp.tc/c/developer-tools) - Vendor: Graphify Labs - Homepage: ## About Graphify exposes hosted code graphs of your indexed repositories as MCP tools. An assistant can search entities and relationships, look up a symbol with its neighbors, trace callers, callees and paths, get a first-pass impact scope for a change, and rank files relevant to a question. It can also read and save repository memory notes. It runs as a hosted Streamable HTTP endpoint at https://api.graphify.com/mcp with OAuth sign-in on first connect. No API key is needed, but you need a Graphify account, a workspace, and at least one repository whose indexing has finished. Source files are not edited. ## What it can do - Search entities and relationships across an indexed code graph - Look up a symbol definition and its graph neighbors - Trace callers, callees and shortest paths between symbols - Assess the immediate impact scope around a change target - Rank files relevant to a plain-English question - List workspaces and indexed repositories, and switch workspace - Recall and save durable repository memory notes ## Example prompts - "List my indexed repositories and show which are ready to query." - "In my API repo, find the code that handles authentication." - "Show the callers of parseConfig and explain any gaps in the indexed evidence." - "What is the impact of changing the UserSession class?" ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http graphify https://api.graphify.com/mcp ``` 2. Start Claude Code, type `/mcp`, pick **graphify** and choose **Authenticate**. A browser window opens for the Graphify Labs sign-in. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Settings → Connectors** and click **Add custom connector**. 2. Name it **Graphify** and paste this URL: ```url https://api.graphify.com/mcp ``` 3. Click **Add**, then **Connect**, and sign in when Graphify Labs asks. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://api.graphify.com/mcp` and click **Add**. 3. Click **Connect** and sign in when Graphify Labs asks. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://api.graphify.com/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Graphify Labs to sign in. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "graphify": { "url": "https://api.graphify.com/mcp" } } } ``` Cursor shows **Needs login** next to the server. Click it to sign in. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"graphify","type":"http","url":"https://api.graphify.com/mcp"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "graphify": { "type": "http", "url": "https://api.graphify.com/mcp" } } } ``` VS Code asks you to sign in the first time the server starts. ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "graphify": { "serverUrl": "https://api.graphify.com/mcp" } } } ``` 2. Refresh the MCP server list in Cascade and sign in when asked. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add graphify --url https://api.graphify.com/mcp codex mcp login graphify ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.graphify] url = "https://api.graphify.com/mcp" ``` ### Gemini CLI ```bash gemini mcp add --transport http graphify https://api.graphify.com/mcp ``` Then, inside Gemini CLI, run `/mcp auth graphify` to sign in. This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "graphify": { "type": "http", "url": "https://api.graphify.com/mcp" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://api.graphify.com/mcp`. ## Details - Server version: 0.1.0 - Last checked: 2026-10-04 (reachable, asks for credentials) - Listed: 2026-10-04 - Updated: 2026-10-04 --- Source: https://mcp.tc/i/graphify (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report