agent-intel-mcp

agent-intel-mcp

An OpenAI-powered developer intelligence MCP server that scans GitHub repositories, extracts and clusters agent engineering patterns, analyzes local codebases, and proposes safe AGENTS.md improvements.

Category
Visit Server

README

agent-intel-mcp

agent-intel-mcp is an OpenAI-powered developer intelligence MCP server. It scans high-signal GitHub repositories, extracts reusable agent-engineering patterns, clusters them, compares them against a local codebase, and proposes safe AGENTS.md improvements.

This version moves beyond a thin MVP:

  • Deep local codebase scanning with conventions and gap detection
  • OpenAI Responses API for suggestion synthesis
  • OpenAI embeddings for pattern clustering with heuristic fallback
  • MCP stdio server with tools, resources, and prompts
  • GitHub repository scanning with relevance scoring
  • AGENTS.md patch preview generation
  • SQLite-backed local memory for scans, clusters, suggestions, and dashboard history
  • CI, release, and deploy scaffolding for portfolio-ready delivery

What This Project Proves

  • OpenAI integration beyond chat wrappers
  • MCP server design for agent clients
  • GitHub mining and local repo analysis in one workflow
  • safe patch generation instead of blind repository mutation
  • TypeScript developer tooling with tests, CI, and release scaffolding

Demo Preview

Agent Intel Console desktop

Agent Intel Console walkthrough

Architecture

+---------------------------------------------------------------+
| agent-intel-mcp                                               |
|                                                               |
|  MCP Server (stdio)                                           |
|  |- Tools: scan, extract, cluster, analyze, suggest, patch    |
|  |- Resources: scans, patterns, clusters, local profile, patch|
|  `- Prompts: summary, AGENTS rewrite                          |
|                                                               |
|  Core Engine                                                  |
|  |- GithubScanner          -> Octokit search + README fetch   |
|  |- PatternExtractor       -> heuristic pattern mining        |
|  |- PatternClusterer       -> embeddings / cosine clustering  |
|  |- LocalRepoProfiler      -> codebase conventions + gaps     |
|  |- OpenAiSuggestionEngine -> Responses API / heuristic mode  |
|  |- PatchBuilder           -> non-destructive AGENTS diff     |
|  `- SqliteStore            -> scans, patterns, clusters       |
+---------------------------------------------------------------+

More detail: docs/ARCHITECTURE.md Case study: docs/CASE_STUDY.md

Tools

  • scan_github_repos
  • extract_patterns
  • cluster_patterns
  • analyze_local_repo
  • generate_suggestions
  • generate_agents_patch

Quick Start

npm install
cp .env.example .env
npm run build
npm test
npm run demo:seed
npm run demo

Open http://localhost:4321.

Run With .env

Create a local .env in the project root:

OPENAI_API_KEY=sk-...
GITHUB_TOKEN=ghp_...
LOCAL_REPO_PATH=C:\Users\syfsy\projekty\agent-intel-mcp

Then run:

npm install
npm run build
npm run demo

Use .env when you want real OpenAI-backed suggestions or a different local repository target.

Run Demo Against Another Repo

PowerShell example:

$env:LOCAL_REPO_PATH="C:\Users\syfsy\projekty\some-other-repo"
npm run demo

Or put that path into .env:

LOCAL_REPO_PATH=C:\Users\syfsy\projekty\some-other-repo

What changes in this mode:

  • local stack analysis points at the other repo
  • detected gaps and conventions come from the other repo
  • generated AGENTS.md patch is tailored to the other repo

Connect As An MCP Server

Build first:

npm install
npm run build

Then add it to your MCP client config:

{
  "mcpServers": {
    "agent-intel": {
      "command": "node",
      "args": ["C:/Users/syfsy/projekty/agent-intel-mcp/dist/index.js"],
      "env": {
        "OPENAI_API_KEY": "sk-...",
        "GITHUB_TOKEN": "ghp_...",
        "LOCAL_REPO_PATH": "C:/Users/syfsy/projekty/agent-intel-mcp"
      }
    }
  }
}

After restart, the MCP client will see these tools:

  • scan_github_repos
  • extract_patterns
  • cluster_patterns
  • analyze_local_repo
  • generate_suggestions
  • generate_agents_patch

Environment

Variable Default Description
OPENAI_API_KEY unset Enables model-backed suggestions and embeddings
OPENAI_MODEL gpt-5-mini OpenAI model used for suggestion generation
OPENAI_EMBEDDING_MODEL text-embedding-3-small Model used for pattern clustering
GITHUB_TOKEN unset Raises GitHub API limits and private-org access
CLUSTER_SIMILARITY_THRESHOLD 0.82 Cosine threshold for embedding-based clusters
LOCAL_REPO_PATH process.cwd() Repository profiled for AGENTS.md suggestions
AGENT_INTEL_DATA_DIR .agent-intel SQLite and cached outputs

Demo UX

  • Local dashboard served from http://localhost:4321
  • Real pipeline trigger: fresh scan, clustering, local gap analysis, patch preview, and history charts
  • Seeded portfolio state via npm run demo:seed
  • Safe patch preview keeps suggested AGENTS.md changes reviewable before any adoption
  • Frontend files: public/index.html, public/styles.css, public/app.js

Release Readiness

  • CI: ci.yml
  • Tagged release publishing: release.yml
  • Package validation: npm run release:check

Deploy Preview

The repo ships with Docker and Render scaffolding:

Recommended path:

  1. Push the repo to GitHub.
  2. Create a Render web service from the repo.
  3. Add OPENAI_API_KEY and GITHUB_TOKEN if you want live model-backed scans.
  4. Use /healthz as the health check.
  5. Deploy and open the generated public URL as the portfolio preview.

Why OpenAI Here

This implementation uses the OpenAI Responses API for suggestion synthesis and the embeddings API for semantic clustering. Current official docs also describe tool-driven workflows and remote MCP support: Using tools and Developer quickstart.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured