MCP Server Tooling
Relevant source files
The following files were used as context for generating this wiki page:
Introduction
MCP (Model Context Protocol) Server Tooling within this project refers to the configuration and rulesets defined to guide AI agents and development tools in navigating a specialized Next.js environment. These tools ensure that automated agents adhere to project-specific conventions, especially where they deviate from standard framework patterns.
The tooling serves as a bridge between the codebase's structural requirements and the external agents (such as Claude or other LLM-based assistants) that interact with it. It emphasizes adherence to breaking changes in APIs and file structures that might not align with general training data.
Sources: .claude/mcp.md, .agent/mcp.md, CLAUDE.md, AGENTS.md
Agent Rule System
The project utilizes specific Markdown-based rule files to instruct AI agents. The AGENTS.md file contains a critical block tagged with nextjs-agent-rules, which explicitly warns that the project uses a non-standard version of Next.js with breaking changes.
Rule Execution Flow
When an agent interacts with the repository, it is directed through a chain of references starting from CLAUDE.md to the specific rules in AGENTS.md.
The flow ensures that any code generation or analysis performed by the agent accounts for project-specific overrides.
Sources: CLAUDE.md:1, AGENTS.md:1-7
Development Infrastructure
The tooling is supported by a specific suite of development dependencies and configurations that enforce code quality and protocol adherence.
Tooling Configuration
| Tool | Purpose | Configuration File |
|---|---|---|
| Biome | Linting and formatting with strict rules | biome.json |
| Next.js | Core framework (v16.2.9) | package.json |
| Vitest | Test execution and environment | package.json |
| TypeScript | Static typing and path mapping | tsconfig.json |
Sources: package.json:7-21, biome.json:1-32
Linting and Formatting Logic
The project uses Biome for high-performance linting and formatting. The configuration enables recommended rules for both React and Next.js while allowing for specific overrides in UI components.
Biome is configured to ignore unknown files and strictly include specific patterns while excluding node_modules and build directories.
Sources: biome.json:7-27, package.json:8-9
Project Scripts
MCP Server Tooling utilizes standard npm scripts to interface with the development environment. These scripts provide entry points for tools to build, test, and verify the application.
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "biome check",
"format": "biome format --write",
"test": "vitest run",
"test:watch": "vitest"
}
Sources: package.json:7-15
Conclusion
The MCP Server Tooling in this portfolio project is designed to enforce a strict development environment that accounts for non-standard Next.js implementations. By combining explicit agent instructions in AGENTS.md with rigid linting via Biome, the system ensures that both human developers and AI agents maintain code integrity and follow specialized project protocols.