trace-mcp code intelligence server
by nikolai-vysotskyiLets your AI understand your codebase structure and answer questions about how files and features connect.
AI Library · 4,066 MCP servers
Lets your AI understand your codebase structure and answer questions about how files and features connect.
Lets your AI scan a Next.js project to find unused files and dead API endpoints.
Lets your AI check your written architecture decisions against your real code and flag what no longer matches.
Lets your AI read and write .aide spec files so it understands your project's intent before touching code.
Let your AI read your API spec, find endpoints, and write TypeScript types for you.
Lets your AI read code by name, make edits, run your tests, and undo changes.
Lets your AI map your codebase so it finds the right files and shows what a change would break.
Checks your API changes for breaking edits and leaked secrets, and keeps a signed record of what ran.
Check whether a claim is supported by the evidence, with a verdict and a confidence score.
Let your AI search a community knowledge base of real fixes for technical errors and problems.
Lets your AI explore your codebase as a map, so it can trace calls, data flow and structure without reading every file.
Lets your AI add login, a database, file storage and small server tasks to an app you are building.
Let your AI create realistic JSON test data from templates, straight from your chat.
Lets your AI look at running Java programs: memory, threads, logs, and class details.
Let your AI reach many MCP tools through one small, tidy connection instead of a huge list.
Check the MCP servers you use for broken tools, risky settings, and changes over time.
Lets your AI look inside a running Android or iOS app and even tap, change values, and take screenshots.
Lets your AI encode, hash, decode, format, and run network checks through onlinecybertools.com for you.
Lets your AI give each copy of a project its own set of ports, so parallel work never clashes.
Lets your AI map your codebase and jump straight to the files that matter instead of reading everything.
Your AI can record why code changed and look up those reasons later, so you stop guessing.
Lets your AI read code errors, jump to definitions, rename things and run language-specific helpers in your project.
Lets your AI search your codebase by meaning, symbols, and callers instead of endless file scans.
Lets your AI call the actions your own app already describes, with checks before anything risky runs.