MCP/mcilspy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: remove AI buzzwords from docs copy

Browse Source 
Replace "AI assistant" with "assistant", remove "AI assistance"
from taglines. Describe what it does, not how it works.
This commit is contained in:
Ryan Malloy 2026-03-03 13:49:23 -07:00
parent 3877ac68e2
commit 0c0648b6ac
5 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs-site/src/content/docs/getting-started/installation.mdx
View File

@ -41,7 +41,7 @@ Install the MCP server, then let it install `ilspycmd` for you. The `install_ils
pip install mcilspy pip install mcilspy
``` ```
Then ask your AI assistant: Then ask your assistant:
> *"Install ilspycmd for me"* > *"Install ilspycmd for me"*
@ -113,7 +113,7 @@ Install the .NET SDK and `ilspycmd` yourself:
## Verify Installation ## Verify Installation
Ask your AI assistant to run the installation check: Ask your assistant to run the installation check:
> *"Check if ilspycmd is installed correctly"* > *"Check if ilspycmd is installed correctly"*

6
docs-site/src/content/docs/getting-started/overview.mdx
View File

@ -5,7 +5,7 @@ description: What mcilspy is, how it works, and who it's for.
import { Aside } from "@astrojs/starlight/components"; import { Aside } from "@astrojs/starlight/components";
mcilspy is a [Model Context Protocol](https://modelcontextprotocol.io/) server that gives AI assistants the power to reverse-engineer .NET binaries. It wraps the [ILSpy](https://github.com/icsharpcode/ILSpy) decompiler and [dnfile](https://github.com/malwarefrank/dnfile) metadata parser behind a clean tool interface, letting Claude (or any MCP client) decompile assemblies, search for hardcoded secrets, explore type hierarchies, and recover lost source code. mcilspy is a [Model Context Protocol](https://modelcontextprotocol.io/) server for reverse-engineering .NET binaries. It wraps the [ILSpy](https://github.com/icsharpcode/ILSpy) decompiler and [dnfile](https://github.com/malwarefrank/dnfile) metadata parser behind a clean tool interface, letting Claude (or any MCP client) decompile assemblies, search for hardcoded secrets, explore type hierarchies, and recover lost source code.
## Two Engines, One Interface ## Two Engines, One Interface
@ -24,13 +24,13 @@ mcilspy operates with two complementary backends:
## What Is MCP? ## What Is MCP?
The [Model Context Protocol](https://modelcontextprotocol.io/) is an open standard for connecting AI assistants to external tools and data sources. Instead of copying output between terminals, you describe what you want in natural language and the AI calls the right tools automatically. The [Model Context Protocol](https://modelcontextprotocol.io/) is an open standard for connecting language models to external tools and data sources. Instead of copying output between terminals, you describe what you want in natural language and the right tools are called automatically.
mcilspy exposes 16 tools and 2 prompts through MCP, making .NET reverse engineering a conversational workflow: mcilspy exposes 16 tools and 2 prompts through MCP, making .NET reverse engineering a conversational workflow:
> *"Search for any hardcoded API keys in MyApp.dll"* > *"Search for any hardcoded API keys in MyApp.dll"*
The AI calls `search_strings` and `search_fields` with the right parameters, aggregates the results, and explains what it found — no manual CLI invocation needed. The assistant calls `search_strings` and `search_fields` with the right parameters, aggregates the results, and explains what it found — no manual CLI invocation needed.
## Supported Formats ## Supported Formats

2
docs-site/src/content/docs/getting-started/quick-start.mdx
View File

@ -12,7 +12,7 @@ Once mcilspy is installed and configured with your MCP client, you're ready to a
<Steps> <Steps>
1. **Point at an assembly** 1. **Point at an assembly**
Give your AI assistant a path to any `.dll` or `.exe`: Give your assistant a path to any `.dll` or `.exe`:
> *"Analyze the assembly at /path/to/MyApp.dll"* > *"Analyze the assembly at /path/to/MyApp.dll"*

6
docs-site/src/content/docs/index.mdx
View File

@ -1,9 +1,9 @@
--- ---
title: mcilspy title: mcilspy
description: Decompile, search, and analyze .NET assemblies with AI assistance via the Model Context Protocol. description: Decompile, search, and analyze .NET assemblies through the Model Context Protocol.
template: splash template: splash
hero: hero:
tagline: Decompile, search, and analyze .NET assemblies with AI assistance. tagline: Decompile, search, and analyze .NET assemblies through natural language.
image: image:
file: ../../assets/hero-decompiler.svg file: ../../assets/hero-decompiler.svg
actions: actions:
@ -74,7 +74,7 @@ import { Card, CardGrid, Tabs, TabItem } from "@astrojs/starlight/components";
</TabItem> </TabItem>
</Tabs> </Tabs>
Then ask your AI assistant: Then ask your assistant:
> *"Decompile the LoginService class from this assembly and explain what it does"* > *"Decompile the LoginService class from this assembly and explain what it does"*

2
docs-site/src/content/docs/reference/prompts.mdx
View File

@ -5,7 +5,7 @@ description: Two MCP prompts for structured assembly analysis workflows.
import { Aside, Tabs, TabItem } from "@astrojs/starlight/components"; import { Aside, Tabs, TabItem } from "@astrojs/starlight/components";
mcilspy includes two [MCP prompts](https://modelcontextprotocol.io/docs/concepts/prompts) that provide structured analysis workflows. Prompts are templates that MCP clients can invoke to guide multi-step analysis -- they tell the AI assistant what tools to call and in what order. mcilspy includes two [MCP prompts](https://modelcontextprotocol.io/docs/concepts/prompts) that provide structured analysis workflows. Prompts are templates that MCP clients can invoke to guide multi-step analysis -- they tell the assistant what tools to call and in what order.
## analyze_assembly ## analyze_assembly