Add trace-mcp MCP server (devtools)

[nikolai-vysotskyi]

Summary

Adds trace-mcp — a framework-aware code intelligence MCP server — under cli-tool/components/mcps/devtools/.

trace-mcp gives Claude Code semantic navigation, impact analysis, and refactoring tools (search, get_outline, get_symbol, find_usages, get_change_impact, apply_codemod, change_signature, etc.) across 60 framework integrations and 81 languages, with up to 99% token reduction vs. raw Read/Grep workflows.

• npm: https://www.npmjs.com/package/trace-mcp
• repo: https://github.com/nikolai-vysotskyi/trace-mcp

File added

cli-tool/components/mcps/devtools/trace-mcp.json:

{
  "mcpServers": {
    "trace-mcp": {
      "description": "Framework-aware code intelligence — semantic navigation, impact analysis, and refactoring across 60 framework integrations and 81 languages with up to 99% token reduction.",
      "command": "npx",
      "args": ["-y", "trace-mcp@latest"]
    }
  }
}

serve is the default CLI command, so no extra args are needed.

Test plan

• JSON validates against the schema used by other MCPs in devtools/ (e.g. serena.json, context7.json)
• npx -y trace-mcp@latest starts the MCP server over stdio (published on npm, no auth required)
• Placed under devtools/ alongside other code-intelligence servers (serena)

---

Summary by cubic

Adds trace-mcp MCP server to devtools to provide framework‑aware code intelligence. Enables semantic navigation, impact analysis, and refactors via npx with no extra setup.

• Area: components (cli-tool/components/)
• New component: cli-tool/components/mcps/devtools/trace-mcp.json (runs npx -y trace-mcp@latest)
• Catalog: regenerate docs/components.json
• Env/Secrets: none

^{Written for commit 89ef5d7. Summary will update on new commits. Review in cubic}

[vercel]

@nikolai-vysotskyi is attempting to deploy a commit to the Daniel Avila's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

👋 Thanks for contributing, @nikolai-vysotskyi!

This PR touches cli-tool/components/** and has been marked review-pending.

What happens next

1. 🤖 Automated security audit runs and posts results on this PR.
2. 👀 Maintainer review — a human reviewer validates the component with the component-reviewer agent (format, naming, security, clarity).
3. ✅ Merge — once approved, your PR is merged to main.
4. 📦 Catalog regeneration — the component catalog is rebuilt automatically.
5. 🚀 Live on aitmpl.com — your component appears on the website after deploy.

While you wait

• Check the Security Audit comment below for any issues to fix.
• Make sure your component follows the contribution guide.

This is an automated message. No action is required from you right now — a maintainer will review soon.

[cubic-dev-ai]

No issues found across 1 file