MCP Server Neurolorap
The MCP Server Neurolorap provides tools for code analysis and documentation:
Code Collection Tool: Collect code from projects, directories, or multiple paths into markdown with syntax highlighting and a table of contents. Customize the output title.
Project Structure Reporter: Generate detailed markdown reports with file size, complexity metrics, and tree-based visualization. Customize the output filename.
Developer Mode: Interact via JSON-RPC terminal interface to list tools and execute functions.
File Storage: Store generated files in a structured directory with a symlink for easy access.
Customizable Ignore Patterns: Specify files to exclude using a
.neuroloraignorefile or direct tool input.
The MCP server integrates with Codecov for tracking code coverage metrics, as evidenced by the Codecov badge in the README.
The MCP server integrates with GitHub for version control, repository hosting, and showing build status through badges.
The MCP server uses GitHub Actions for continuous integration and deployment, running tests across Python versions, checking code formatting, performing type checking, security scans, and generating coverage reports.
The MCP server generates documentation in Markdown format, including code collections with syntax highlighting and project structure reports.
The MCP server uses Shields.io for displaying status badges in the README, including the license and test status badges.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Server Neurolorap collect all code from the src directory into a markdown document"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Server Neurolorap
MCP server providing tools for code analysis and documentation.
Features
Code Collection Tool
Collect code from entire project
Collect code from specific directories or files
Collect code from multiple paths
Markdown output with syntax highlighting
Table of contents generation
Support for multiple programming languages
Project Structure Reporter Tool
Analyze project structure and metrics
Generate detailed reports in markdown format
File size and complexity analysis
Tree-based visualization
Recommendations for code organization
Customizable ignore patterns
Related MCP server: Code Snippet Server
Quick Overview
# Using uvx (recommended)
uvx mcp-server-neurolorap
# Or using pip (not recommended)
pip install mcp-server-neurolorapYou don't need to install or configure any dependencies manually. The tool will set up everything you need to analyze and document code.
Installation
You'll need to have UV >= 0.4.10 installed on your machine.
To install and run the server:
# Install using uvx (recommended)
uvx mcp-server-neurolorap
# Or install using pip (not recommended)
pip install mcp-server-neurolorapThis will automatically:
Install all required dependencies
Configure Cline integration
Set up the server for immediate use
The server will be available through the MCP protocol in Cline. You can use it to analyze and document code from any project.
Usage
Developer Mode
The server includes a developer mode with JSON-RPC terminal interface for direct interaction:
# Start the server in developer mode
python -m mcp_server_neurolorap --devAvailable commands:
help: Show available commandslist_tools: List available MCP toolscollect <path>: Collect code from specified pathreport [path]: Generate project structure reportexit: Exit developer mode
Example session:
> help
Available commands:
- help: Show this help message
- list_tools: List available MCP tools
- collect <path>: Collect code from specified path
- report [path]: Generate project structure report
- exit: Exit the terminal
> list_tools
["code_collector", "project_structure_reporter"]
> collect src
Code collection complete!
Output file: code_collection.md
> report
Project structure report generated: PROJECT_STRUCTURE_REPORT.md
> exit
Goodbye!Through MCP Tools
Code Collection
from modelcontextprotocol import use_mcp_tool
# Collect code from entire project
result = use_mcp_tool(
"code_collector",
{
"input": ".",
"title": "My Project"
}
)
# Collect code from specific directory
result = use_mcp_tool(
"code_collector",
{
"input": "./src",
"title": "Source Code"
}
)
# Collect code from multiple paths
result = use_mcp_tool(
"code_collector",
{
"input": ["./src", "./tests"],
"title": "Project Files"
}
)Project Structure Analysis
# Generate project structure report
result = use_mcp_tool(
"project_structure_reporter",
{
"output_filename": "PROJECT_STRUCTURE_REPORT.md"
}
)
# Analyze specific directory with custom ignore patterns
result = use_mcp_tool(
"project_structure_reporter",
{
"output_filename": "src_structure.md",
"ignore_patterns": ["*.pyc", "__pycache__"]
}
)File Storage
The server uses a structured approach to file storage:
All generated files are stored in
~/.mcp-docs/<project-name>/A
.neurolorasymlink is created in your project root pointing to this directory
This ensures:
Clean project structure
Consistent file organization
Easy access to generated files
Support for multiple projects
Reliable file synchronization across different OS environments
Fast file visibility in IDEs and file explorers
Customizing Ignore Patterns
Create a .neuroloraignore file in your project root to customize which files are ignored:
# Dependencies
node_modules/
venv/
# Build
dist/
build/
# Cache
__pycache__/
*.pyc
# IDE
.vscode/
.idea/
# Generated files
.neurolora/If no .neuroloraignore file exists, a default one will be created with common ignore patterns.
Development
Clone the repository
Create and activate virtual environment:
python -m venv .venv
source .venv/bin/activate # On Unix
# or
.venv\Scripts\activate # On WindowsInstall development dependencies:
pip install -e ".[dev]"Run the server:
# Normal mode (MCP server with stdio transport)
python -m mcp_server_neurolorap
# Developer mode (JSON-RPC terminal interface)
python -m mcp_server_neurolorap --devTesting
The project maintains high quality standards through automated testing and continuous integration:
Comprehensive test suite with over 80% code coverage
Automated testing on Python 3.10, 3.11, and 3.12
Continuous integration through GitHub Actions
Regular security scans and dependency checks
For development and testing details, see PROJECT_SUMMARY.md.
Code Quality
The project maintains high code quality standards through various tools:
# Format code
black .
# Sort imports
isort .
# Lint code
flake8 .
# Type check
mypy src tests
# Security check
bandit -r src/
safety checkAll these checks are run automatically on pull requests through GitHub Actions.
CI/CD Pipeline
The project uses GitHub Actions for continuous integration and deployment:
Runs tests on Python 3.10, 3.11, and 3.12
Checks code formatting and style
Performs type checking
Runs security scans
Generates coverage reports
Builds and validates package
Uploads test artifacts
The pipeline must pass before merging any changes.
Contributing
We welcome contributions! Please see CONTRIBUTING.md for guidelines.
License
MIT License. See LICENSE file for details.
Available Tools
2 toolscode_collectorC
Collect code from files into a markdown document
Inputs: input_path, title, subproject_id. Returns: result
project_structure_reporterC
Generate a report of project structure metrics
Inputs: output_filename, ignore_patterns. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: code_collector focuses on extracting code content into a markdown document, while project_structure_reporter generates metrics about the project's structure. There is no overlap in functionality, making it easy for an agent to choose the right tool.
Both tools follow a consistent noun_verb pattern (code_collector and project_structure_reporter), using snake_case throughout. The naming is predictable and readable, with no deviations in style or convention.
With only 2 tools, the server feels thin for a domain like project analysis or code management. This minimal set may not cover essential operations such as code analysis, dependency checking, or file manipulation, limiting its utility for broader tasks.
Inferred domain is project/code analysis, but the tool surface is severely incomplete. It lacks basic CRUD operations (e.g., no tools for creating, updating, or deleting files), code quality checks, or integration with version control, leaving significant gaps that could cause agent failures.
Related MCP Connectors
MCP server for opencode documentation, generated by doc2mcp.
MCP server for accessing curated awesome list documentation
MCP server for innovationlab documentation, generated by doc2mcp.
Repository knowledge graph MCP server for codebase understanding and debugging.
Related MCP Servers
- FlicenseBqualityDmaintenanceA MCP Server used to collect MCP Servers over the internet.320-
- AlicenseBqualityDmaintenanceA MCP server for managing and storing code snippets in various programming languages, allowing users to create, list, and delete snippets via a standardized interface.33 npm7MIT
- AlicenseBqualityDmaintenanceAn MCP server that provides access to project files and their contents, allowing users to retrieve file data from specified project directories with error handling and configuration options.15MIT
- FlicenseBqualityDmaintenanceAn MCP server that enables interaction with Markdown knowledge bases, allowing users to search and retrieve content by tags, text, URL, or date range from their local markdown files.791-