Skip to main content
Use this page after you connect your agent. It takes about two minutes. You check three things in order: the server is connected, the agent can call Graphify’s tools, and the agent picks them for code questions.

In Graphify: connection status and starter tasks

On Connectors → MCP, the Try a query step shows a live connection status: When the status is Connected, Graphify hides My agent returned repositories and unlocks Try a repository task. The same page has a Connect your agent card with install steps for your client, a rules block you can copy into AGENTS.md / CLAUDE.md / your client’s rules file, and (once a repository is indexed) Try it on your repository starter tasks drawn from your code. Starter tasks are one-click handoffs; after a task finishes you can Run again for a fresh receipt instead of replaying a consumed one.

Step 1: Check the server is connected

Your client should list a server named graphify at https://api.graphify.com/mcp, signed in, with its tools showing. Other clients have their own MCP panel. See Integrations for each one.
A listed server isn’t proof the agent can read your repositories. Step 2 checks that.

Step 2: Run three test prompts

Open a new agent chat and paste each prompt. Your client shows each tool call in the chat, usually with its name and arguments. Check that a Graphify tool ran, not a file search. Replace <function> with a function you know in a repository from the first answer. If you belong to several workspaces and the list looks wrong, ask the agent to run list_workspaces, then set_workspace. Then ask a code question without naming Graphify, such as What calls <function>?. If the agent searches files instead, add the always-on rule in Setup for AI agents, step 5.

Step 3: Fix what’s wrong

More fixes are in Graphify MCP and Troubleshooting.

Prove it after a session

At the end of a task, ask:
The calls it names should match the tool calls in the chat. To count calls across Claude Code sessions, see Make agents use the graph.