AutoFixture MCP Server
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., "@AutoFixture MCP Server Show me the quick start guide for AutoFixture"
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.
AutoFixture MCP Server
A Model Context Protocol (MCP) server that provides comprehensive documentation and usage examples for the AutoFixture testing library. This server runs in a Docker container and can be easily integrated with VSCode, Cursor, or Claude Desktop.
Features
Quick Start Guide: Get up and running with AutoFixture basics
Method Search: Search for specific AutoFixture methods and their usage
Class Information: Detailed documentation for core AutoFixture classes
Package Information: NuGet package details for all AutoFixture extensions
Usage Patterns: Common patterns and code examples
Best Practices: Recommended approaches for using AutoFixture
GitHub Documentation: Fetch latest docs directly from the repository
Related MCP server: MCP Reference Server
Available Tools
get_quick_start: Get AutoFixture quick start guide and basic usage examples
search_methods: Search for AutoFixture methods (e.g., 'Create', 'Build', 'Freeze')
get_class_info: Get detailed information about classes like 'Fixture' or 'IFixture'
get_packages: List AutoFixture NuGet packages by category (core/mocking/testing/all)
get_usage_pattern: Get common usage patterns (e.g., 'customizing', 'automaq', 'xunit')
get_best_practices: Get AutoFixture best practices and recommendations
fetch_github_docs: Fetch latest documentation from GitHub (README, cheatsheet, FAQ)
Prerequisites
Docker installed on your system
Node.js 20+ (for local development)
VSCode, Cursor, or Claude Desktop
Quick Setup
Option 1: Using Docker (Recommended)
Build the Docker image:
docker build -t autofixture-mcp-server:latest .Test the server:
docker run --rm -i autofixture-mcp-server:latest
Option 2: Using Docker Compose
docker-compose up -dIntegration with Cursor/VSCode
Cursor Setup
Open Cursor settings (Cmd+Shift+P → "Preferences: Open User Settings (JSON)")
Add the MCP server configuration:
{
"mcp": {
"servers": {
"autofixture": {
"command": "/Users/admin/dev/mcp/mcp-wrapper.sh"
}
}
}
}Or use the provided config file:
# Copy the configuration
cat cursor-mcp-config.json
# Add to your Cursor settingsVSCode with Claude Code
Install the Claude Code extension
Open your MCP configuration file:
On macOS:
~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.jsonOn Linux:
~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.jsonOn Windows:
%APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json
Add the server configuration:
{
"mcpServers": {
"autofixture": {
"command": "/Users/admin/dev/mcp/mcp-wrapper.sh",
"args": [],
"env": {}
}
}
}Claude Desktop Setup
Open Claude Desktop settings:
On macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonOn Windows:
%APPDATA%\Claude\claude_desktop_config.jsonOn Linux:
~/.config/Claude/claude_desktop_config.json
Add the server configuration:
{
"mcpServers": {
"autofixture": {
"command": "/Users/admin/dev/mcp/mcp-wrapper.sh",
"args": [],
"env": {}
}
}
}Restart Claude Desktop
Local Development Setup
If you want to develop or modify the server locally:
Install dependencies:
npm installBuild the project:
npm run buildRun locally (without Docker):
npm startDevelopment mode with auto-rebuild:
npm run dev
Usage Examples
Once integrated, you can use the MCP server in your conversations:
Example 1: Getting Started
User: "Use the autofixture MCP to show me how to get started with AutoFixture"
AI: [Calls get_quick_start tool and provides quick start guide]Example 2: Searching for Methods
User: "Search for methods related to creating objects in AutoFixture"
AI: [Calls search_methods with query "create" and shows available methods]Example 3: Getting Usage Patterns
User: "Show me how to use AutoFixture with xUnit"
AI: [Calls get_usage_pattern with pattern "xunit" and provides examples]Example 4: Package Information
User: "What AutoFixture packages are available for mocking?"
AI: [Calls get_packages with category "mocking" and lists all mocking packages]Configuration Files
mcp-config.json: Generic MCP configurationcursor-mcp-config.json: Cursor-specific configurationclaude_desktop_config.json: Claude Desktop configurationdocker-compose.yml: Docker Compose configurationmcp-wrapper.sh: Shell script wrapper for Docker integration
Troubleshooting
Server not starting
Ensure Docker is running:
docker psCheck Docker logs:
docker logs autofixture-mcp-serverRebuild the image:
docker build -t autofixture-mcp-server:latest .
Permission issues with wrapper script
chmod +x mcp-wrapper.shCursor/VSCode not detecting the server
Restart the editor after adding configuration
Check that the wrapper script path is absolute
Verify Docker is installed:
docker --version
Testing the server manually
# Run the wrapper script directly
./mcp-wrapper.sh
# Or use Docker directly
docker run --rm -i autofixture-mcp-server:latestProject Structure
.
├── src/
│ └── index.ts # Main MCP server implementation
├── dist/ # Compiled JavaScript (generated)
├── Dockerfile # Docker image configuration
├── docker-compose.yml # Docker Compose setup
├── mcp-wrapper.sh # Shell wrapper for Docker
├── package.json # Node.js dependencies
├── tsconfig.json # TypeScript configuration
├── mcp-config.json # Generic MCP config
├── cursor-mcp-config.json # Cursor-specific config
├── claude_desktop_config.json # Claude Desktop config
└── README.md # This fileArchitecture
The server is built using:
TypeScript: Type-safe server implementation
@modelcontextprotocol/sdk: Official MCP SDK
axios: HTTP client for fetching GitHub documentation
cheerio: HTML parsing (for future enhancements)
Docker: Containerization for easy deployment
Contributing
Feel free to extend the server with additional tools:
Add new tool definitions in the
ListToolsRequestSchemahandlerImplement the tool logic in the
CallToolRequestSchemahandlerRebuild the Docker image
License
MIT
Resources
Version
1.0.0
Built with MCP for enhanced AI-assisted development with AutoFixture.
Available Tools
7 toolsfetch_github_docsC
Fetch latest documentation from AutoFixture GitHub repository
Inputs: topic.
get_best_practicesB
Get AutoFixture best practices and recommendations
Inputs: no named parameters.
get_class_infoA
Get detailed information about a specific AutoFixture class
Inputs: className (required).
get_packagesB
Get list of AutoFixture NuGet packages and their purposes
Inputs: category.
get_quick_startA
Get AutoFixture quick start guide and basic usage examples
Inputs: no named parameters.
get_usage_patternC
Get common usage patterns and code examples
Inputs: pattern.
search_methodsC
Search for AutoFixture methods and their usage
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool targets a distinct aspect of AutoFixture documentation (e.g., fetching full docs, best practices, specific class info, packages, quick start, usage patterns, method search). Descriptions clearly differentiate them, leaving no ambiguity.
All tool names follow a consistent verb_noun pattern using underscores (fetch_github_docs, get_best_practices, etc.). The verbs 'fetch', 'get', and 'search' are all appropriate and uniform.
With 7 tools, the server is well-scoped for a documentation-focused AutoFixture helper. Each tool earns its place, covering the main information needs without overwhelming the user.
The tool set covers nearly all common documentation requests: full docs, best practices, classes, packages, quick start, patterns, and method search. A minor gap is the lack of version-specific changelogs or troubleshooting, but core coverage is solid.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
An MCP server that automatically collects feedback on your MCP server.
MCP server for autoxingtech documentation, generated by doc2mcp.
MCP server for opencode documentation, generated by doc2mcp.
Related MCP Servers
AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that generates and runs mock API servers from API documentation like OpenAPI/Swagger specs, enabling developers and AI assistants to quickly spin up mock backends for development and testing.17MIT- AlicenseNot gradedqualityDmaintenanceA comprehensive reference implementation demonstrating all features of the Model Context Protocol (MCP) specification, serving as documentation, learning resource, and testing tool for MCP implementations.1MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for LLM fuzzing and testing, providing secure access to multiple AI providers through a standardized interface.-
- AlicenseAqualityDmaintenanceA learning-focused MCP server that provides tools for current time, arithmetic, random quotes, mock weather, and UUID generation, demonstrating the Model Context Protocol end-to-end.5MIT