MCP Neurolora

Created By
aindreywaya year ago
An intelligent MCP server that provides tools for collecting and documenting code from directories
Overview

What is MCP Neurolora?

MCP Neurolora is an intelligent MCP server designed to provide tools for collecting and documenting code from directories, utilizing the OpenAI API for code analysis.

How to use MCP Neurolora?

To use MCP Neurolora, follow the installation guide to set up Node.js and the necessary tools, then configure the MCP server with your settings file and use the provided commands to analyze code or generate documentation.

Key features of MCP Neurolora?

  • Code analysis using OpenAI API with detailed feedback and improvement suggestions.
  • Code collection from directories into markdown files with syntax highlighting.
  • Automatic installation and configuration of base MCP servers for enhanced functionality.

Use cases of MCP Neurolora?

  1. Analyzing code for best practices and improvement suggestions.
  2. Collecting all code from a project directory into a single markdown file.
  3. Generating documentation for codebases automatically.

FAQ from MCP Neurolora?

  • Can MCP Neurolora analyze any programming language?

Yes! MCP Neurolora can analyze various programming languages as long as the code is accessible in the specified directory.

  • Is there a cost associated with using MCP Neurolora?

No! MCP Neurolora is free to use under the MIT License.

  • How does the code analysis work?

The server uses the OpenAI API to analyze the code and provide structured feedback, including best practices and recommendations.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aindreyway
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago