Skip to main content
Graphify, the hosted product, builds and stores the graph of your repositories and serves it over MCP at https://api.graphify.com/mcp. Point your coding agent at that URL, sign in once in the browser, and the agent asks the graph instead of re-reading files every session. There’s nothing to install or run.

​
What you’ll build

  • An indexed repository in Graphify.
  • An agent connected to the hosted MCP server over Streamable HTTP with OAuth.
  • A working first query, and prompts for everyday use.

​
Setup

  • An account at app.graphify.com. It’s free for up to 3 repositories, no card required.
  • At least one repository with the status Indexed. The quickstart walks through connecting GitHub and switching on Indexing from a repository’s … menu.

​
Step 1: Open the MCP connector

In the console, go to Connectors → MCP. Setup has three steps: Choose agent, Connect and Try a query. Pick your agent, or open Browse all agents. To let the agent do the setup, choose Copy quick-start prompt and paste it into your agent.

​
Step 2: Add the server to your agent

Claude Code (run in a terminal, not inside a session):
Cursor, Claude Desktop and other mcpServers clients:
VS Code (.vscode/mcp.json):
The server is also listed in the MCP registry as io.github.Graphify-Labs/graphify. Per-agent details are on Cloud MCP.

​
Step 3: Sign in

On first use the agent opens a browser window. In Claude Code, run /mcp, pick graphify and choose to authenticate. Sign in to Graphify and approve access. There’s no API key to paste or store.

​
Step 4: Check the connection

Paste the test prompt from Try a query, or ask:
The list should match your workspace. If you belong to more than one, ask the agent to use list_workspaces and set_workspace first.

​
Step 5: Ask about your code

Name the symbol, file or area you care about:
  • Who calls the function that validates a session token?
  • What would break if I changed this module's public interface?
  • Which tests cover the billing webhook handler?
  • Trace how a request reaches the billing service.
The agent picks tools such as graphify_find, graphify_callers, graphify_impact, graphify_tests_for and graphify_trace. You don’t call them by hand.

​
Step 6: Give the agent memory

Ask the agent to record decisions as it works:
The agent stores this with remember and finds it later with recall. Inspect and remove entries on the Memory page.

​
When it goes wrong

No browser window opens. Some agents need a restart after you add a server. Restart it, then run a tool again. list_repositories returns nothing. The repository isn’t indexed yet, or the agent is in another workspace. Check the status in Repositories, then use set_workspace. The agent answers without Graphify. Name the tool or say “use Graphify” in the prompt. Some agents only call MCP tools when asked.

​
Production patterns

  • Add the server at project scope (.mcp.json or .vscode/mcp.json) and commit it, so teammates connect with one sign-in.
  • Check pull requests your agent opens on the Reviews page.
  • Open the Graphs and Wiki pages when an answer needs a closer look.
  • To keep everything on your own machine, use the open-source CLI instead: Give Claude Code a graph of your monorepo.

​
Complete example

​
What you built

Your agent queries a graph we build and host. It answers questions about callers, impact and tests from indexed repositories, and remembers decisions across sessions.

​
Next steps

Cloud MCP

Per-agent setup for the hosted MCP server.

Plan a refactor

Ask your agent what a change will reach.

Try it in Graphify

We build and host the graph for you. Start with a 14-day Pro trial, then keep up to 3 repositories on Free. No card required.