NeoCoder: Neo4j-Guided AI Coding Workflow

Created By
angrysky56a year ago
An MCP server allowing AI assistants to use a Neo4j knowledge graph as their primary, dynamic instruction manual and long term project memory with adaptive templating and autonomous tool development tools.
Overview

What is NeoCoder?

NeoCoder is an MCP server implementation that allows AI assistants like Claude to utilize a Neo4j knowledge graph as a dynamic instruction manual and project memory for standardized coding workflows.

How to use NeoCoder?

To use NeoCoder, set up a Neo4j database and run the MCP server with Python. Integrate it with Claude AI by configuring the necessary parameters in the claude-app-config.json file.

Key features of NeoCoder?

  • Utilizes Neo4j for standardized coding workflows.
  • Provides templates for common coding tasks (e.g., FIX, REFACTOR).
  • Maintains an audit trail of changes in the graph.
  • Enforces critical steps like testing before logging success.

Use cases of NeoCoder?

  1. Assisting AI in fixing bugs with guided workflows.
  2. Refactoring code while ensuring functionality.
  3. Deploying code with safety checks.
  4. Implementing new features with proper documentation.

FAQ from NeoCoder?

  • What is required to run NeoCoder?

You need a running Neo4j instance, Python 3.10+, and Claude Desktop for integration.

  • Can I customize the templates?

Yes! Templates can be edited or created in the templates directory.

  • How does NeoCoder ensure coding standards?

NeoCoder uses a knowledge graph to define standard procedures and tracks project changes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
angrysky56
Star
3
Language
Python
License
MIT 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)

a day ago