MCP server · Developer tools
Vex code search MCP server
by tenatarika
Lets your AI look up symbols, find usages, and trace call graphs in your local codebase.
Vex is a tool that searches through the code on your computer. It builds an index once, then answers questions about your code very quickly. It is handy if you (or your AI assistant) need to find where something is defined, who uses it, or how functions connect.
What is an MCP server? The 30-second version
On its own, your AI can only chat with you. It does not know what is inside the files on your computer. An MCP server is a small helper program that gives your AI a new skill, here the ability to search your local codebase. Once it is connected, your AI can ask Vex things like 'where is this function defined?' and get real answers back.
What this MCP server does
You ask your AI a question about your code, like where a certain class lives or who calls a function. Your AI passes that question to the Vex helper. Vex looks it up in its pre-built index of your code. Then it sends the answer back to your AI, and your AI tells you what it found. You never have to leave the chat.
What you can do with it
- Check whether a symbol exists and where it is defined
- Show the body of a class or function without reading the whole file
- Find all the places a symbol is used
- Trace who calls a function and what it calls
- Find implementations of an interface or trait
- Search for code by meaning, not just exact name
- Compare which symbols changed between branches
- See the history of a symbol across commits
Try asking your AI
- “Where is PaymentService defined?”
- “Show me the body of the process_event function”
- “Who calls process_event?”
- “Find all usages of the IndexReader class”
- “Which tests cover process_event?”
What it gives back to you
You get back short, clear answers in the chat. That could be a list of file paths and line numbers, a snippet of code, or a yes/no answer. If you asked about callers, you see a list of function names. If you asked about history, you see commits.
Before you start
What you need
- The Vex tool installed on your computer (a single program, no extra setup)
- Your code project indexed once with the vex index command
- The Vex MCP server running (installed alongside Vex)
- A code editor or terminal to run the indexing command
Good to know
It reads your local code files, so only point it at folders you are comfortable sharing with your AI.
Install it with your AI
Add Vex code search MCP server to your AI, no technical skills needed
You don't install anything by hand. You copy one prompt, paste it into an AI that can work on your computer, and it checks, installs and connects the server for you, asking you when it needs something.
Sign in to get the install prompt
Members get a ready-made prompt that lets the Claude desktop app check Vex code search MCP server, install it and connect it for them, step by step. You don't need any technical skills: you copy, paste and answer a few questions. Your connected AI can also find and install any of the 4,609 MCP servers here for you.
Who it's for
Developers and anyone who works with a codebase and wants their AI to help them understand it faster.
