Periphery Code Audit

Swift code analysis with Periphery - detect unused code and improve code quality

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "periphery-code-audit": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

Periphery MCP Server

A Model Context Protocol (MCP) server that wraps the Periphery tool, enabling AI assistants to perform Swift code audits and detect unused code in iOS/macOS projects.

Features

7 MCP Tools for comprehensive code analysis
CLI Integration - Uses Periphery CLI for stability and version flexibility
JSON Output - Structured, parseable results perfect for AI interpretation
Flexible Scanning - Support for Xcode projects and Swift Packages
Advanced Options - Full control over Periphery scan configurations

Quick Start

Using Homebrew (Recommended):

bash

# 1. Install Periphery
brew install peripheryapp/periphery/periphery

# 2. Install Periphery MCP Server
brew tap zyntx-lab/tap
brew install periphery-mcp-server

# 3. Configure Claude Desktop
# Edit: ~/Library/Application Support/Claude/claude_desktop_config.json
# Add:
#   "periphery": {
#     "command": "/opt/homebrew/bin/periphery-mcp-server"
#   }

# 4. Restart Claude Desktop (Cmd+Q then reopen)

# 5. Test it
# In Claude Desktop: "Check if Periphery is installed"

From Source:

bash

# 1. Install Periphery
brew install peripheryapp/periphery/periphery

# 2. Clone and build this server
git clone https://github.com/zyntx-lab/periphery-mcp-server.git
cd periphery-mcp-server
swift build -c release

# 3. Install to system path
sudo cp .build/release/periphery-mcp-server /usr/local/bin/
sudo chmod +x /usr/local/bin/periphery-mcp-server

# 4. Configure Claude Desktop
# Edit: ~/Library/Application Support/Claude/claude_desktop_config.json
# Add:
#   "periphery": {
#     "command": "/usr/local/bin/periphery-mcp-server"
#   }

# 5. Restart Claude Desktop (Cmd+Q then reopen)

# 6. Test it
# In Claude Desktop: "Check if Periphery is installed"

Prerequisites

macOS 13.0 or later
Swift 6.0 or later
Periphery installed

Installing Periphery

bash

brew install peripheryapp/periphery/periphery

Or download from Periphery releases.

Installation

Option 1: Homebrew (Recommended)

bash

# Add the tap
brew tap zyntx-lab/tap

# Install the server
brew install periphery-mcp-server

# Verify installation
which periphery-mcp-server
# Should output: /opt/homebrew/bin/periphery-mcp-server

Option 2: Download from GitHub Releases

Download the latest binary from Releases:

bash

# Download and install
curl -L https://github.com/zyntx-lab/periphery-mcp-server/releases/download/v1.0.0/periphery-mcp-server \
  -o /usr/local/bin/periphery-mcp-server
chmod +x /usr/local/bin/periphery-mcp-server

# Verify installation
which periphery-mcp-server
# Should output: /usr/local/bin/periphery-mcp-server

Option 3: Build from Source

bash

# Clone the repository
git clone https://github.com/zyntx-lab/periphery-mcp-server.git
cd periphery-mcp-server

# Build release version
swift build -c release

# Install to system path (requires password)
sudo cp .build/release/periphery-mcp-server /usr/local/bin/
sudo chmod +x /usr/local/bin/periphery-mcp-server

# Verify installation
which periphery-mcp-server
# Should output: /usr/local/bin/periphery-mcp-server

Option 4: Install from MCP Registry

The server is also available on the MCP Registry. Use your MCP-compatible client to install it directly.

Configuration

Claude Desktop

Step 1: Locate Your Config File

The config file is at: ~/Library/Application Support/Claude/claude_desktop_config.json

Step 2: Edit the Configuration

If you installed via Homebrew:

config.json

{
  "mcpServers": {
    "periphery": {
      "command": "/opt/homebrew/bin/periphery-mcp-server"
    }
  }
}

If you installed to /usr/local/bin:

config.json

{
  "mcpServers": {
    "periphery": {
      "command": "/usr/local/bin/periphery-mcp-server"
    }
  }
}

If you're using the build directory directly:

config.json

{
  "mcpServers": {
    "periphery": {
      "command": "/FULL/PATH/TO/periphery-mcp-server/.build/release/periphery-mcp-server"
    }
  }
}

If you already have other MCP servers configured:

config.json

{
  "mcpServers": {
    "xcode": {
      "command": "node",
      "args": ["/path/to/xcode-mcp-server/dist/index.js"]
    },
    "periphery": {
      "command": "/usr/local/bin/periphery-mcp-server"
    }
  }
}

Step 3: Restart Claude Desktop

Important: You must completely quit and restart Claude Desktop for changes to take effect.

Quit Claude Desktop: Press Cmd+Q or use Claude Desktop → Quit
Wait a few seconds
Reopen Claude Desktop

Step 4: Verify It's Working

Open a new conversation in Claude Desktop and try:

Code

"Check if Periphery is installed"

If configured correctly, Claude will use the check_periphery_installed tool and respond with installation status.

Testing with MCP Inspector

Before configuring Claude Desktop, you can test the server with the MCP Inspector:

bash

# Install MCP Inspector (if not already installed)
npm install -g @modelcontextprotocol/inspector

# Test your server
npx @modelcontextprotocol/inspector /usr/local/bin/periphery-mcp-server

# Or if using build directory
npx @modelcontextprotocol/inspector /path/to/periphery-mcp-server/.build/release/periphery-mcp-server

The Inspector will open in your browser where you can test all tools interactively.

Other Editors

VS Code

Add to .vscode/mcp.json:

config.json

{
  "mcpServers": {
    "periphery": {
      "type": "stdio",
      "command": "/usr/local/bin/periphery-mcp-server"
    }
  }
}

Cursor

Add to .cursor/mcp.json:

config.json

{
  "mcpServers": {
    "periphery": {
      "type": "stdio",
      "command": "/usr/local/bin/periphery-mcp-server"
    }
  }
}

Available Tools

1. `check_periphery_installed`

Verify that Periphery CLI is installed and accessible.

Parameters: None

Example Response:

config.json

{
  "installed": true,
  "path": "/usr/local/bin/periphery",
  "message": "Periphery is installed and ready"
}

2. `get_periphery_version`

Get the installed version of Periphery.

Parameters: None

Example Response:

config.json

{
  "version": "2.18.0",
  "raw_output": "2.18.0"
}

3. `scan_project`

Run a basic Periphery scan on a project.

Parameters:

project_path (required): Path to .xcodeproj or Package.swift
schemes (optional): Build schemes to scan (Xcode only)
targets (optional): Specific targets to analyze
format (optional): Output format: json, xcode, csv, checkstyle (default: json)

Example Response:

config.json

{
  "success": true,
  "results": [
    {
      "kind": "class",
      "name": "UnusedClass",
      "modifiers": ["public"],
      "location": "Sources/MyApp/UnusedClass.swift:10:7"
    }
  ],
  "summary": {
    "total_unused": 5,
    "by_kind": {"class": 2, "function": 3}
  }
}

4. `scan_with_config`

Run Periphery scan using a YAML configuration file.

Parameters:

config_path (required): Path to .periphery.yml config file

5. `analyze_unused_imports`

Focus specifically on detecting unused imports.

Parameters:

project_path (required): Path to .xcodeproj or Package.swift
schemes (optional): Build schemes to scan
targets (optional): Specific targets to analyze

6. `find_redundant_public`

Identify public declarations that could be internal.

Parameters:

project_path (required): Path to .xcodeproj or Package.swift
schemes (optional): Build schemes to scan
targets (optional): Specific targets to analyze

7. `scan_with_options`

Advanced scanning with custom Periphery flags.

Parameters:

project_path (required): Path to .xcodeproj or Package.swift
schemes (optional): Build schemes to scan
targets (optional): Specific targets to analyze
format (optional): Output format
retain_public (optional): Retain all public declarations
retain_objc_accessible (optional): Retain @objc declarations
disable_unused_import_analysis (optional): Disable unused import analysis
index_store_path (optional): Custom index store location
verbose (optional): Enable verbose output

Usage Examples

With Claude Desktop

Once configured, you can have natural conversations with Claude about your code:

Check Installation:

Code

You: "Check if Periphery is installed"

Claude: [Uses check_periphery_installed]
"Yes, Periphery is installed at /usr/local/bin/periphery
Version: 2.18.0"

Scan a Project:

Code

You: "Scan my iOS project at ~/Projects/MyApp/MyApp.xcodeproj for unused code"

Claude: [Uses scan_project]
"I found 15 unused declarations in your project:

Classes (5):
- UnusedViewController at MyApp/UnusedViewController.swift:10
- OldDataManager at MyApp/Models/OldDataManager.swift:25
...

Functions (8):
- helperFunction at Utils/Helpers.swift:42
...

Imports (2):
- UIKit in DataModel.swift:1
..."

Find Redundant Public:

Code

You: "Check which public declarations could be made internal in ~/Projects/MyFramework"

Claude: [Uses find_redundant_public]
"Found 12 public declarations that are only used internally and could be made internal:
- public class InternalHelper (only used within the framework)
- public func formatDate() (only called from within the module)
..."

Analyze Unused Imports:

Code

You: "Find unused imports in my Swift package"

Claude: [Uses analyze_unused_imports]
"Found 8 unused imports that can be safely removed:
- Foundation in Models/User.swift (not using any Foundation APIs)
- Combine in ViewModels/ProfileViewModel.swift (Combine is imported but not used)
..."

With Custom Configuration

Create .periphery.yml in your project:

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Periphery Code Audit

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "periphery-code-audit": { "command": "npx", "args": ["-y", "Periphery Code Audit"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Periphery Code Audit AllMCPs Directory Badge

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/periphery-code-audit?style=directory)](https://allmcps.com/mcp/periphery-code-audit)

HTML Embed

<a href="https://allmcps.com/mcp/periphery-code-audit"><img src="https://allmcps.com/api/badge/periphery-code-audit?style=directory" alt="Periphery Code Audit on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

36Quality signal: Fair · 36/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools15/30

Adoption & activity2/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Periphery Code Audit →Install in Claude Desktop Install in Cursor Install in VS Code

Periphery Code Audit

Swift code analysis with Periphery - detect unused code and improve code quality

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "periphery-code-audit": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

Periphery MCP Server

A Model Context Protocol (MCP) server that wraps the Periphery tool, enabling AI assistants to perform Swift code audits and detect unused code in iOS/macOS projects.

Features

7 MCP Tools for comprehensive code analysis
CLI Integration - Uses Periphery CLI for stability and version flexibility
JSON Output - Structured, parseable results perfect for AI interpretation
Flexible Scanning - Support for Xcode projects and Swift Packages
Advanced Options - Full control over Periphery scan configurations

Quick Start

Using Homebrew (Recommended):

bash

# 1. Install Periphery
brew install peripheryapp/periphery/periphery

# 2. Install Periphery MCP Server
brew tap zyntx-lab/tap
brew install periphery-mcp-server

# 3. Configure Claude Desktop
# Edit: ~/Library/Application Support/Claude/claude_desktop_config.json
# Add:
#   "periphery": {
#     "command": "/opt/homebrew/bin/periphery-mcp-server"
#   }

# 4. Restart Claude Desktop (Cmd+Q then reopen)

# 5. Test it
# In Claude Desktop: "Check if Periphery is installed"

From Source:

bash

# 1. Install Periphery
brew install peripheryapp/periphery/periphery

# 2. Clone and build this server
git clone https://github.com/zyntx-lab/periphery-mcp-server.git
cd periphery-mcp-server
swift build -c release

# 3. Install to system path
sudo cp .build/release/periphery-mcp-server /usr/local/bin/
sudo chmod +x /usr/local/bin/periphery-mcp-server

# 4. Configure Claude Desktop
# Edit: ~/Library/Application Support/Claude/claude_desktop_config.json
# Add:
#   "periphery": {
#     "command": "/usr/local/bin/periphery-mcp-server"
#   }

# 5. Restart Claude Desktop (Cmd+Q then reopen)

# 6. Test it
# In Claude Desktop: "Check if Periphery is installed"

Prerequisites

macOS 13.0 or later
Swift 6.0 or later
Periphery installed

Installing Periphery

bash

brew install peripheryapp/periphery/periphery

Or download from Periphery releases.

Installation

Option 1: Homebrew (Recommended)

bash

# Add the tap
brew tap zyntx-lab/tap

# Install the server
brew install periphery-mcp-server

# Verify installation
which periphery-mcp-server
# Should output: /opt/homebrew/bin/periphery-mcp-server

Option 2: Download from GitHub Releases

Download the latest binary from Releases:

bash

# Download and install
curl -L https://github.com/zyntx-lab/periphery-mcp-server/releases/download/v1.0.0/periphery-mcp-server \
  -o /usr/local/bin/periphery-mcp-server
chmod +x /usr/local/bin/periphery-mcp-server

# Verify installation
which periphery-mcp-server
# Should output: /usr/local/bin/periphery-mcp-server

Option 3: Build from Source

bash

# Clone the repository
git clone https://github.com/zyntx-lab/periphery-mcp-server.git
cd periphery-mcp-server

# Build release version
swift build -c release

# Install to system path (requires password)
sudo cp .build/release/periphery-mcp-server /usr/local/bin/
sudo chmod +x /usr/local/bin/periphery-mcp-server

# Verify installation
which periphery-mcp-server
# Should output: /usr/local/bin/periphery-mcp-server

Option 4: Install from MCP Registry

The server is also available on the MCP Registry. Use your MCP-compatible client to install it directly.

Configuration

Claude Desktop

Step 1: Locate Your Config File

The config file is at: ~/Library/Application Support/Claude/claude_desktop_config.json

Step 2: Edit the Configuration

If you installed via Homebrew:

config.json

{
  "mcpServers": {
    "periphery": {
      "command": "/opt/homebrew/bin/periphery-mcp-server"
    }
  }
}

If you installed to /usr/local/bin:

config.json

{
  "mcpServers": {
    "periphery": {
      "command": "/usr/local/bin/periphery-mcp-server"
    }
  }
}

If you're using the build directory directly:

config.json

{
  "mcpServers": {
    "periphery": {
      "command": "/FULL/PATH/TO/periphery-mcp-server/.build/release/periphery-mcp-server"
    }
  }
}

If you already have other MCP servers configured:

config.json

{
  "mcpServers": {
    "xcode": {
      "command": "node",
      "args": ["/path/to/xcode-mcp-server/dist/index.js"]
    },
    "periphery": {
      "command": "/usr/local/bin/periphery-mcp-server"
    }
  }
}

Step 3: Restart Claude Desktop

Important: You must completely quit and restart Claude Desktop for changes to take effect.

Quit Claude Desktop: Press Cmd+Q or use Claude Desktop → Quit
Wait a few seconds
Reopen Claude Desktop

Step 4: Verify It's Working

Open a new conversation in Claude Desktop and try:

Code

"Check if Periphery is installed"

If configured correctly, Claude will use the check_periphery_installed tool and respond with installation status.

Testing with MCP Inspector

Before configuring Claude Desktop, you can test the server with the MCP Inspector:

bash

# Install MCP Inspector (if not already installed)
npm install -g @modelcontextprotocol/inspector

# Test your server
npx @modelcontextprotocol/inspector /usr/local/bin/periphery-mcp-server

# Or if using build directory
npx @modelcontextprotocol/inspector /path/to/periphery-mcp-server/.build/release/periphery-mcp-server

The Inspector will open in your browser where you can test all tools interactively.

Other Editors

VS Code

Add to .vscode/mcp.json:

config.json

{
  "mcpServers": {
    "periphery": {
      "type": "stdio",
      "command": "/usr/local/bin/periphery-mcp-server"
    }
  }
}

Cursor

Add to .cursor/mcp.json:

config.json

{
  "mcpServers": {
    "periphery": {
      "type": "stdio",
      "command": "/usr/local/bin/periphery-mcp-server"
    }
  }
}

Available Tools

1. `check_periphery_installed`

Verify that Periphery CLI is installed and accessible.

Parameters: None

Example Response:

config.json

{
  "installed": true,
  "path": "/usr/local/bin/periphery",
  "message": "Periphery is installed and ready"
}

2. `get_periphery_version`

Get the installed version of Periphery.

Parameters: None

Example Response:

config.json

{
  "version": "2.18.0",
  "raw_output": "2.18.0"
}

3. `scan_project`

Run a basic Periphery scan on a project.

Parameters:

project_path (required): Path to .xcodeproj or Package.swift
schemes (optional): Build schemes to scan (Xcode only)
targets (optional): Specific targets to analyze
format (optional): Output format: json, xcode, csv, checkstyle (default: json)

Example Response:

config.json

{
  "success": true,
  "results": [
    {
      "kind": "class",
      "name": "UnusedClass",
      "modifiers": ["public"],
      "location": "Sources/MyApp/UnusedClass.swift:10:7"
    }
  ],
  "summary": {
    "total_unused": 5,
    "by_kind": {"class": 2, "function": 3}
  }
}

4. `scan_with_config`

Run Periphery scan using a YAML configuration file.

Parameters:

config_path (required): Path to .periphery.yml config file

5. `analyze_unused_imports`

Focus specifically on detecting unused imports.

Parameters:

project_path (required): Path to .xcodeproj or Package.swift
schemes (optional): Build schemes to scan
targets (optional): Specific targets to analyze

6. `find_redundant_public`

Identify public declarations that could be internal.

Parameters:

project_path (required): Path to .xcodeproj or Package.swift
schemes (optional): Build schemes to scan
targets (optional): Specific targets to analyze

7. `scan_with_options`

Advanced scanning with custom Periphery flags.

Parameters:

project_path (required): Path to .xcodeproj or Package.swift
schemes (optional): Build schemes to scan
targets (optional): Specific targets to analyze
format (optional): Output format
retain_public (optional): Retain all public declarations
retain_objc_accessible (optional): Retain @objc declarations
disable_unused_import_analysis (optional): Disable unused import analysis
index_store_path (optional): Custom index store location
verbose (optional): Enable verbose output

Usage Examples

With Claude Desktop

Once configured, you can have natural conversations with Claude about your code:

Check Installation:

Code

You: "Check if Periphery is installed"

Claude: [Uses check_periphery_installed]
"Yes, Periphery is installed at /usr/local/bin/periphery
Version: 2.18.0"

Scan a Project:

Code

You: "Scan my iOS project at ~/Projects/MyApp/MyApp.xcodeproj for unused code"

Claude: [Uses scan_project]
"I found 15 unused declarations in your project:

Classes (5):
- UnusedViewController at MyApp/UnusedViewController.swift:10
- OldDataManager at MyApp/Models/OldDataManager.swift:25
...

Functions (8):
- helperFunction at Utils/Helpers.swift:42
...

Imports (2):
- UIKit in DataModel.swift:1
..."

Find Redundant Public:

Code

You: "Check which public declarations could be made internal in ~/Projects/MyFramework"

Claude: [Uses find_redundant_public]
"Found 12 public declarations that are only used internally and could be made internal:
- public class InternalHelper (only used within the framework)
- public func formatDate() (only called from within the module)
..."

Analyze Unused Imports:

Code

You: "Find unused imports in my Swift package"

Claude: [Uses analyze_unused_imports]
"Found 8 unused imports that can be safely removed:
- Foundation in Models/User.swift (not using any Foundation APIs)
- Combine in ViewModels/ProfileViewModel.swift (Combine is imported but not used)
..."

With Custom Configuration

Create .periphery.yml in your project:

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Periphery Code Audit

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "periphery-code-audit": { "command": "npx", "args": ["-y", "Periphery Code Audit"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/periphery-code-audit?style=directory)](https://allmcps.com/mcp/periphery-code-audit)

HTML Embed

<a href="https://allmcps.com/mcp/periphery-code-audit"><img src="https://allmcps.com/api/badge/periphery-code-audit?style=directory" alt="Periphery Code Audit on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

36Quality signal: Fair · 36/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools15/30

Adoption & activity2/15

Community engagement0/10

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Periphery Code Audit →Install in Claude Desktop Install in Cursor Install in VS Code

Periphery Code Audit

Quick Install

Client Config & Setup

Documentation Overview

Periphery MCP Server

Features

Quick Start

Prerequisites

Installing Periphery

Installation

Option 1: Homebrew (Recommended)

Option 2: Download from GitHub Releases

Option 3: Build from Source

Option 4: Install from MCP Registry

Configuration

Claude Desktop

Step 1: Locate Your Config File

Step 2: Edit the Configuration

Step 3: Restart Claude Desktop

Step 4: Verify It's Working

Testing with MCP Inspector

Other Editors

VS Code

Cursor

Available Tools

1. check_periphery_installed

2. get_periphery_version

3. scan_project

4. scan_with_config

5. analyze_unused_imports

6. find_redundant_public

7. scan_with_options

Usage Examples

With Claude Desktop

With Custom Configuration

Related MCP Servers

Reviews

Frequently Asked Questions about Periphery Code Audit

AllMCPs Directory Badge

Technical Specs & Signals

Moxie Docs MCP

Own this project?

Share & Embed

Explore more

Periphery Code Audit

Quick Install

Client Config & Setup

Documentation Overview

Periphery MCP Server

Features

Quick Start

Prerequisites

Installing Periphery

Installation

Option 1: Homebrew (Recommended)

Option 2: Download from GitHub Releases

Option 3: Build from Source

Option 4: Install from MCP Registry

Configuration

Claude Desktop

Step 1: Locate Your Config File

Step 2: Edit the Configuration

Step 3: Restart Claude Desktop

Step 4: Verify It's Working

Testing with MCP Inspector

Other Editors

VS Code

Cursor

Available Tools

1. check_periphery_installed

2. get_periphery_version

3. scan_project

4. scan_with_config

5. analyze_unused_imports

6. find_redundant_public

7. scan_with_options

Usage Examples

With Claude Desktop

With Custom Configuration

Related MCP Servers

1. `check_periphery_installed`

2. `get_periphery_version`

3. `scan_project`

4. `scan_with_config`

5. `analyze_unused_imports`

6. `find_redundant_public`

7. `scan_with_options`

1. `check_periphery_installed`

2. `get_periphery_version`

3. `scan_project`

4. `scan_with_config`

5. `analyze_unused_imports`

6. `find_redundant_public`

7. `scan_with_options`