Gortex MCP Server: Setup for Claude Code, Cursor and Other Apps

• Finds the code that matters for a task in your indexed project

  Takes a task or question and returns the files, symbols and surrounding context an assistant needs, built from the code graph. It can also outline a repo or plan the next steps.

  Try: “Find where login sessions are created and what code depends on it.”

  Read · explore

• Searches code by symbol name, text, file name or syntax pattern

  Looks up functions and classes by name, runs literal or regex text search, finds files by name and matches syntax patterns, all against the index of your project.

  Try: “Find every function named parseConfig.”

  Read · search

• Reads a file, a single function or several symbols at once

  Returns file contents, one symbol with its signature and source, a file summary, or the context needed before an edit. Reads one target per call.

  Try: “Show me the source of the handleRequest function.”

  Files · read

• Shows who calls a function, what it depends on and what implements it

  Answers fixed questions about how code connects: usages, callers, dependencies, dependents, implementations, overrides and class hierarchies.

  Try: “Who calls validateToken, and what would break if I change it?”

  Read · relations

• Follows call chains and data flow through the code

  Walks forward call chains, finds paths between two symbols, and follows data flow or tainted input through the graph for deeper investigations.

  Try: “Trace how user input reaches the SQL query in the orders handler.”

  Read · trace

• Runs checks like hotspots, dead code, TODOs and architecture summaries

  Runs read-only graph analyses over your project, such as heavily changed hotspots, unused code, API contracts and architecture layers. Analyses that save results are kept out of this tool.

  Try: “Which parts of this repo are dead code?”

  Read · analyze

• Asks a research agent that uses the code graph to answer an open question

  Hands an open-ended question to an agent that drives Gortex's own search and graph tools and returns one answer. It needs an AI provider set up in Gortex first, and is off until you do.

  Try: “Explain how requests move from the API layer to the database.”

  Network · ask

• Checks the impact of a change before and after you make it

  Detects what changed, shows diagnostics and blast radius, previews and simulates an edit, and picks the tests to run. It does not apply changes.

  Try: “What is the impact of renaming UserService, and which tests should I run?”

  Read · change

• Edits files and symbols, and can move or delete whole files

  Applies text edits to files or symbols, writes new files, batches several edits, and can move or delete whole files. It also generates docs, wiki and graph exports. Output paths are limited to indexed repositories when an assistant calls it.

  Try: “Replace the old timeout value in server.go with 30 seconds.”

  Delete · edit

• Renames, moves, inlines or deletes code with language-aware changes

  Applies refactors that follow the code structure, including rename, move, inline and delete, and applies editor code actions and fix-alls across files.

  Try: “Rename the function fetchUser to loadUser everywhere it is used.”

  Delete · refactor

• Builds a code review with findings and context for a diff

  Produces review packs and critiques from your diff, with surrounding code, sibling files and questions to answer. It does not post anything.

  Try: “Review my current changes and list risks.”

  Network · review

• Posts review comments to GitHub or another code host

  Publishes a prepared review to a pull request on your code host. This is the one tool that writes outside your machine.

  Try: “Post the review findings to pull request 42.”

  Write · publish_review

• Lists, scores and triages open pull requests

  Reads pull requests from your code host and works out blast radius, risk, merge conflicts between PRs and suggested reviewers.

  Try: “Which open pull requests are riskiest to merge?”

  Network · pr

• Reads saved notes, memories and notebooks about the project

  Looks up durable notes the assistant or you saved earlier, including memories, notes and notebooks, and onboarding summaries.

  Try: “What did we note earlier about the payments module?”

  Read · recall

• Saves notes and memories so later sessions can use them

  Stores or edits memories, notes and notebooks, and records acknowledged risks or suppressed findings, which Gortex keeps on your machine.

  Try: “Remember that the billing module must not call the legacy API.”

  Write · remember

• Shows which repositories, projects and index state Gortex has

  Reports tracked repositories, active project, scopes and index status, and the state of the daemon proxy. Read only.

  Try: “Which repos is Gortex tracking right now?”

  Read · workspace

• Tracks or untracks repos, re-indexes and changes saved scopes

  Changes durable workspace state: add or remove repositories, rebuild the index, save or delete scopes, and run enrichment passes such as blame and coverage that store results.

  Try: “Track my ~/projects/api repo and reindex it.”

  Delete · workspace_admin

• Tries edits in a temporary copy without touching files on disk

  Creates in-memory overlay sessions so the assistant can test changes against the graph before anything is written. Nothing reaches disk from this tool.

  Try: “Open a temporary overlay with my proposed change and check what breaks.”

  Write · overlay

• Changes settings for the current chat session

  Adjusts connection-lifetime state such as planning mode, workflows, navigation cursor and event subscriptions.

  Try: “Subscribe to diagnostics for this session.”

  Write · session

• Searches or slices large earlier tool outputs

  Lets the assistant grep, slice or export a big response that Gortex buffered, instead of re-running the query.

  Try: “Show lines 200 to 260 of that last result.”

  Read · response

• Used by the assistant behind the scenes

  Lists the operations each Gortex tool supports

  Returns the available tools and operations, or the exact input format of one operation, so the assistant calls the others correctly.

  Try: “Which operations does the search tool support?”

  Read · capabilities

Watch out for

• It can edit, rename and delete your code

  The edit and refactor tools write files, and can move or delete whole files or symbols. Run it on a clean git branch, or start it read-only. github.com

• The review tool can post to GitHub

  The publish_review tool writes review comments to a pull request on your code host. Review the text before the assistant sends it. github.com

• The installer changes your whole machine

  gortex install edits your assistants' configs, adds hooks and skills under folders like ~/.claude, and the curl script puts a program on your PATH. Read what it writes first, or add the server by hand. github.com

• A background program keeps running

  The daemon holds the index of your tracked repositories in memory and on disk. Its optional HTTP port binds to 127.0.0.1 by default, and the program refuses a non-local address without an auth token. github.com

• Research tool can send code to an AI provider

  If you configure an AI provider, the ask tool sends your questions and code snippets to it. It is off until you set one up. github.com

• Tool output is screened for prompt injection

  Gortex scans arguments and results for injection patterns and adds a warning note; it never blocks the call. github.com

• Telemetry is off by default

  Anonymous tool counts are sent only if you turn them on with gortex telemetry on. github.com

Security advisories