npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@next-analyzer/mcp

v0.1.0

Published

Next.js project analyzer MCP server for AI assistants

Readme

Next Analyzer MCP

A Model Context Protocol (MCP) server for analyzing Next.js projects with TypeScript. This tool helps AI assistants quickly understand and work with Next.js projects by providing detailed analysis of project structure, TypeScript definitions, and routing patterns.

Features

  • Project Structure Analysis: Automatically maps out your Next.js project structure including pages, components, and API routes
  • TypeScript Definition Extraction: Extracts and categorizes TypeScript interfaces and types used throughout the project
  • Route Analysis: Comprehensive analysis of static and dynamic routes, including API endpoints
  • Data Fetching Pattern Detection: Identifies and analyzes data fetching methods (getStaticProps, getServerSideProps, etc.)
  • Component Relationship Mapping: Visualizes component dependencies and relationships

Installation

# Install globally
npm install -g @next-analyzer/mcp

# Or use with npx
npx @next-analyzer/mcp

Integration with Cline

Add the following configuration to your Cline MCP settings:

{
  "mcpServers": {
    "next-analyzer": {
      "command": "npx",
      "args": ["@next-analyzer/mcp"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

Available Tools

analyze_project_structure

Analyzes the structure of a Next.js project and returns a comprehensive overview.

interface ProjectStructure {
  pages: RouteNode[];
  components: ComponentInfo[];
  apiRoutes: APIRouteInfo[];
  dataFetching: DataFetchingInfo[];
  envVariables: string[];
}

extract_typescript_definitions

Extracts and categorizes TypeScript interfaces and types used in the project.

interface TypeScriptDefinitions {
  interfaces: TypeInfo[];
  types: TypeInfo[];
  props: PropTypeInfo[];
  apiTypes: APITypeInfo[];
}

analyze_routes

Provides detailed analysis of the project's routing structure.

interface RouteAnalysis {
  staticRoutes: RouteInfo[];
  dynamicRoutes: DynamicRouteInfo[];
  apiEndpoints: APIEndpointInfo[];
  middleware: MiddlewareInfo[];
}

Example Usage

// Example of using the MCP server with Cline
const result = await use_mcp_tool({
  server_name: "next-analyzer",
  tool_name: "analyze_project_structure",
  arguments: {
    path: "./my-next-project"
  }
});

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

License

This project is licensed under the MIT License - see the LICENSE file for details.

Requirements

  • Node.js >= 16.0.0
  • Next.js project with TypeScript