mcpField
D
DotNetSearch

DotNetSearch

Local
github.com/puneethdc99Developer Tools0Updated 1d ago

About DotNetSearch

DotNetSearch is an MCP server for developers and coding agents, combining codebase search, .NET package decompilation, and detailed PDF inspection. Its targeted results and code compression reduce the context used for searches and file reads.

Key features

  1. 01Search code by keyword or natural-language query
  2. 02Find structurally related code
  3. 03Decompile types from NuGet assemblies
  4. 04Compress C# code whitespace
  5. 05Read PDF text, metadata, images, and structure

Use cases

  1. 01Locate definitions and matching lines in a repository
  2. 02Trace related implementations and callers
  3. 03Inspect types from referenced NuGet packages
  4. 04Extract targeted text or visuals from technical PDFs

MCP support

Exposes code search, file reading, NuGet decompilation, code compression, and PDF inspection tools to MCP clients over stdio.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository
Packages
nugetPuneethDC.DotNetSearch1.0.3

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

DotNetSearch — MCP Search & PDF Server

MCP Registry NuGet GitHub Release CI Build

MCP Server Identifier: mcp-name: io.github.puneethdc99/dotnetsearch
(Proof of package ownership for GitHub MCP Registry inclusion)

DotNetSearch is a self-contained MCP (Model Context Protocol) server that empowers GitHub Copilot, Claude, Cursor, and other AI agents with high-performance codebase search, NuGet package decompilation, whitespace token reduction, and deep PDF document reading and analysis:

Key Tools Overview
CategoryToolPurpose
Code SearchsearchFind files and lines matching a keyword or natural-language query — returns only matching lines (~110 tokens vs ~2500 for a full file read)
Code Searchsearch_relatedFind code chunks structurally similar to a known location — ideal for discovering callers, implementations, or patterns
Decompilationdecompile_typeDecompile any .NET type from referenced NuGet package assemblies — returns the full C# class definition without needing the source code
Optimizationcompress_codeReduce C# code indentation from 4-space to 1-space per indent level and remove blank lines — saves 10–20% tokens with zero semantic change
File Readingread_fileRead a file from disk and optionally return a specific line range — useful after search when you need full file context
PDF Readingread_pdf_textExtract clean, structured text page-by-page or across targeted page ranges from any PDF document
PDF Readingget_pdf_infoInspect PDF metadata, total page count, per-page dimensions, author, subject, creation date, and structure
PDF Visualsrender_pdf_page_as_imageRasterize any PDF page into a high-resolution PNG image at custom DPI — ideal for inspecting charts, diagrams, tables, and scanned documents
PDF Visualsextract_pdf_imagesExtract embedded raster images from PDF pages and save to disk with pixel coordinates
PDF Structureget_pdf_bookmarksExtract the hierarchical table of contents, bookmarks, and document outline with target page links
PDF Formsget_pdf_form_fieldsRead interactive AcroForm form fields (text boxes, checkboxes, radio buttons, dropdowns) and their values
PDF Assetsextract_pdf_attachmentsExtract embedded file attachments from PDF documents and save them to disk
PDF Linksget_pdf_hyperlinksExtract all clickable web URLs, internal page jumps, and external document links with bounding boxes

Instead of reading full files (~2500 tokens each), the agent gets back only the matching lines (~110 tokens) — saving up to 98% of context window per query. For files that must be read in full, use compress_code first to strip whitespace overhead and save an additional 10–20% of tokens. For PDF documentation, technical manuals, and specifications, dedicated tools extract targeted text, images, and tables without overwhelming the model context window.


Step 1 — Installation

Option A: Install via .NET CLI (NuGet Tool)

If you have the .NET SDK installed (recommended for .NET developers):

dotnet tool install -g PuneethDC.DotNetSearch

Once installed, the command dotnetsearch is available globally from any terminal.

To update to the latest version in the future:

dotnet tool update -g PuneethDC.DotNetSearch
Option B: Download Standalone Executable (No .NET required)

Go to the latest release and download the self-contained executable for your platform:

PlatformFile to download
Windows x64DotNetSearch-win-x64.exe
Linux x64DotNetSearch-linux-x64
macOS ARM64DotNetSearch-osx-arm64

No .NET installation required. The runtime is bundled inside the executable.

Save it somewhere permanent, e.g.:

  • Windows: C:\Tools\DotNetSearch.exe
  • Linux/macOS: /usr/local/bin/DotNetSearch

On Linux/macOS, make it executable:

chmod +x /usr/local/bin/DotNetSearch

Step 2 — Add to your MCP config

Open (or create) your global MCP config file:

ClientConfig file location
Visual Studio%USERPROFILE%\.mcp.json
VS Code + Copilot%USERPROFILE%\.mcp.json
Claude Desktop%APPDATA%\Claude\claude_desktop_config.json
Cursor%USERPROFILE%\.cursor\mcp.json
If installed via NuGet (.NET Tool):

Works identically across Windows, Linux, and macOS without path differences:

{
  "servers": {
    "DotNetSearch": {
      "type": "stdio",
      "command": "dotnetsearch"
    }
  }
}
If using Standalone Executable:
Windows:
{
  "servers": {
    "DotNetSearch": {
      "type": "stdio",
      "command": "C:\\Tools\\DotNetSearch.exe"
    }
  }
}
Linux / macOS:
{
  "servers": {
    "DotNetSearch": {
      "type": "stdio",
      "command": "/usr/local/bin/DotNetSearch"
    }
  }
}
Alternative: Run on-demand with dnx (Zero-Install):
{
  "servers": {
    "DotNetSearch": {
      "type": "stdio",
      "command": "dnx",
      "args": ["PuneethDC.DotNetSearch"]
    }
  }
}

If you already have other servers in the file, just add the "DotNetSearch" block inside the existing "servers" object.


Step 3 — Verify it is active

Visual Studio / VS Code:

  1. Open GitHub Copilot Chat
  2. Switch to Agent Mode
  3. Click the wrench / Select Tools icon
  4. Confirm the DotNetSearch tools appear in the list and are enabled:
    • Code & Navigation: search, search_related, decompile_type, compress_code, read_file
    • PDF Document Inspection: read_pdf_text, get_pdf_info, render_pdf_page_as_image, extract_pdf_images, get_pdf_bookmarks, get_pdf_form_fields, extract_pdf_attachments, get_pdf_hyperlinks

Step 4 — Update your Copilot instructions

To make Copilot automatically prefer DotNetSearch over built-in file reading, add the instructions below to your Copilot instructions file. There are two places you can put this — repo-level (affects only that repo) or global (affects all repos).


Option A — Repo-level instructions (recommended)

File location:

<your-repo-root>\.github\copilot-instructions.md

This file is read by GitHub Copilot for every conversation in that repository. It is the recommended place if you want DotNetSearch to be preferred only for a specific project.

How to find or create it:

  • Navigate to your repository root folder
  • Look for a .github subfolder — if it doesn't exist, create it
  • Inside .github, look for copilot-instructions.md — if it doesn't exist, create the file

Option B — Global instructions (applies to all repos)

File location:

ClientGlobal instructions file
Visual Studio%APPDATA%\Microsoft\VisualStudio\Copilot\copilot-instructions.md
VS Code + Copilot%USERPROFILE%\.github\copilot-instructions.md

How to find or create it:

  • Open the path above in File Explorer (paste into the address bar)
  • If the folder doesn't exist, create it
  • If copilot-instructions.md doesn't exist in the folder, create the file

Note: If you add instructions to both files, Copilot merges them — both will be active at the same time.


Instructions to add

Paste the following into whichever file you chose above:

## Search Preference
When searching for code, symbols, or text in this repository, always prefer
the `DotNetSearch` MCP tool (`search` and `search_related`) over reading full
files or using built-in workspace search. DotNetSearch returns only matching
lines and is significantly more token-efficient (~98% fewer tokens per query).
Do not call DotNetSearch tools in parallel — run one search at a time.

## PDF Document Reading
When reading, analyzing, or searching PDF documents:
- Always prefer `read_pdf_text` and `get_pdf_info` over raw file operations.
- First call `get_pdf_info` to inspect total pages and document metadata.
- Call `read_pdf_text` with specific page ranges (`startPage`, `endPage`) to avoid token overflow.
- If the PDF contains visual charts, flowcharts, architectural diagrams, or scanned pages, use `render_pdf_page_as_image` to rasterize the page.
- For interactive PDF forms, use `get_pdf_form_fields` to extract user inputs.

## NuGet Type Inspection
When the user asks about a third-party or NuGet type and the source code is not
available in the workspace, use the `DotNetSearch` MCP tool `decompile_type` to
decompile the type from the project's referenced assemblies. Pass the short or
fully qualified type name and the absolute path to the .csproj file. The project
must have been built at least once before calling this tool.

## Code Compression
When reading source files to minimize context window usage, use the
`DotNetSearch` MCP tool `compress_code` — BUT ONLY for the following fully-safe
languages where indentation is cosmetic and braces/keywords define scope:

  C#, Java, JavaScript, TypeScript, C, C++, Kotlin, Swift, Rust, Scala,
  PHP, Ruby, CSS, SCSS, Less, JSON, XML

NEVER call `compress_code` on any other language. In particular, NEVER use it on
Python, YAML, CoffeeScript, Pug/Jade, HAML, or Makefile — these are
indentation-sensitive and compression WILL silently corrupt the file structure.

Before calling `compress_code`, check the file extension:
- Allowed:  .cs .java .js .ts .jsx .tsx .kt .swift .rs .scala .php .rb .css .scss .less .json .xml .c .cpp .h
- Blocked:  .py .yaml .yml .coffee .pug .jade .haml  (and Makefiles with no extension)

Pass the absolute file path. For JavaScript/TypeScript projects using 2-space
indentation, set `sourceIndentSize=2`.

Step 5 — You're done

No special commands or workflow changes are needed. Just continue your normal coding tasks in Copilot Agent Mode — DotNetSearch will be used automatically whenever Copilot needs to search your codebase or inspect PDF documents.

Over time you will notice a reduction in token usage per conversation. This is because DotNetSearch returns only the matching lines (typically ~110 tokens) instead of full file contents (~2500 tokens), saving up to 98% of context window per search operation.


Tool reference

search

Searches a local directory for files whose content matches a keyword or natural-language query. Uses BM25 ranking with CamelCase and snake_case token expansion.

ParameterTypeDefaultDescription
querystringrequiredKeyword, identifier, or natural-language phrase
repostringrequiredAbsolute or relative path to the directory to search
top_kint5Max results to return (1–100)
context_linesint0Lines of context above/below each match (0–5)

search_related

Finds code chunks structurally similar to a specific location in a file. Use after search to explore related implementations, callers, or patterns.

ParameterTypeDefaultDescription
file_pathstringrequiredPath to the file as returned by a prior search result
lineintrequiredLine number (1-indexed) from a prior search result
repostringrequiredAbsolute or relative path to the directory to search
top_kint5Number of similar chunks to return (1–100)

read_file

Reads a text file from disk and returns its contents. Use it after search when you already know the target file and need the full context. Supports an absolute or relative path plus optional start_line and end_line range arguments.

ParameterTypeDefaultDescription
pathstringrequiredAbsolute or relative path to the file to read
start_lineint11-based line number to start reading from
end_lineint01-based line number to stop reading at (0 = read to end)

read_pdf_text

Extracts clean, formatted text from a PDF file with page markers. Ideal for documentation, technical specifications, papers, and architecture guides. Supports whole-document extraction or targeted page ranges.

ParameterTypeDefaultDescription
pathstringrequiredAbsolute or relative path to the PDF file
startPageint11-based page number to begin extracting text from
endPageint01-based page number to stop extracting text at (0 = read through the last page)

get_pdf_info

Retrieves comprehensive metadata and physical layout information about a PDF file without reading its full text content. Use this first to plan targeted extractions.

ParameterTypeDefaultDescription
pathstringrequiredAbsolute or relative path to the PDF file

Returns: Total page count, dimensions per page (widthPt, heightPt), document title, author, subject, keywords, creator, producer, creation date, and modification date.


render_pdf_page_as_image

Rasterizes a specific PDF page into a high-resolution PNG image on disk. Essential for pages with complex graphical diagrams, architectural flowcharts, schematics, tables, or scanned documents where raw text extraction is insufficient.

ParameterTypeDefaultDescription
pathstringrequiredAbsolute or relative path to the PDF file
pageNumberint11-based index of the page to render
dpiint150Render resolution in DPI (e.g. 72 = draft, 150 = standard, 300 = print/high-res)

Returns: Path to the rendered .png image and image pixel dimensions.


extract_pdf_images

Extracts all embedded raster images (e.g., photos, diagrams, embedded JPEGs/PNGs) from a PDF page and saves them directly to disk.

ParameterTypeDefaultDescription
pathstringrequiredAbsolute or relative path to the PDF file
pageNumberint01-based page number (0 = extract embedded images across all pages)
outputDirectorystringnullFolder to save images into (defaults to <pdf-folder>/<pdf-name>_images/)

get_pdf_bookmarks

Extracts the hierarchical bookmark outline (Table of Contents tree) from a PDF. Helps agents understand the complete document structure before requesting specific chapters or pages.

ParameterTypeDefaultDescription
pathstringrequiredAbsolute or relative path to the PDF file

Returns: Recursive tree of bookmarks with titles and target destination page numbers.


get_pdf_form_fields

Reads all interactive AcroForm form fields embedded in a PDF document.

ParameterTypeDefaultDescription
pathstringrequiredAbsolute or relative path to the PDF file

Returns: List of form fields with field names, field types (textbox, checkbox, combobox, radio button), and current values.


extract_pdf_attachments

Extracts files embedded directly inside the PDF catalog (e.g., attached source code, sample data, schemas, or companion files) and writes them to disk.

ParameterTypeDefaultDescription
pathstringrequiredAbsolute or relative path to the PDF file
outputDirectorystringnullDirectory to save extracted attachments into

get_pdf_hyperlinks

Extracts all hyperlinks and clickable annotations present on PDF pages.

ParameterTypeDefaultDescription
pathstringrequiredAbsolute or relative path to the PDF file
pageNumberint01-based page number (0 = extract links from all pages)

Returns: URL targets, destination page jumps, and bounding coordinates for each hyperlink.


decompile_type

Decompiles a .NET type (class, interface, enum, struct, or delegate) from NuGet package assemblies referenced by a .NET project. Useful when you need to understand third-party APIs without source code.

ParameterTypeDefaultDescription
typeNamestringrequiredShort name (Session) or fully qualified name (Opc.Ua.Client.Session)
projectPathstringrequiredAbsolute path to the .csproj that references the NuGet package
maxResultsint1Max matches to return when the name is ambiguous across assemblies

Note: The project must be built at least once so the bin\ output folder is populated with NuGet assemblies.


compress_code

Reduces code indentation from 4-space (or configurable) to 1-space per indent level and removes blank lines. Saves 10–20% tokens with zero semantic change — safe because brace-scoped and keyword-scoped languages treat indentation as cosmetic. Accepts either an absolute file path or a raw code string. Returns compressed code plus metrics: originalLength, compressedLength, savingsPercent, and line counts.

✅ Safe for (brace-scoped / keyword-scoped): C#, Java, JavaScript, TypeScript, C, C++, Kotlin, Swift, Rust, Scala, PHP, Ruby, CSS, SCSS, Less, JSON, XML

❌ Do NOT use on (indentation-sensitive — will corrupt code): Python, YAML, CoffeeScript, Pug/Jade, HAML, Makefile

⚠️ Conditional:

  • Go — safe for LLM reading; uses tabs natively so set sourceIndentSize=4 (tab width). Round-trip compilation would need gofmt.
  • Markdown — avoid; 4-space indent = code block in Markdown spec.
  • JavaScript/TypeScript — set sourceIndentSize=2 for 2-space projects.
  • Multi-line string literals (C# verbatim strings, Java """, JS template literals) — internal whitespace is also reduced. Code is still readable by an LLM but not round-trip safe for strings that depend on exact internal indentation.
ParameterTypeDefaultDescription
filePathstringnullAbsolute path to the source file to compress. Provide either this or code.
codestringnullRaw source code string to compress. Used when filePath is not provided.
sourceIndentSizeint4Number of spaces that represent one indent level in the source. Set to 2 for JS/TS/Ruby/Scala projects.
targetIndentSizeint1Number of spaces to use per indent level in the output.

Supported file types

.pdf .cs .ts .js .jsx .tsx .json .md .txt .xml .yaml .yml .html .css .py .java .cpp .c .h .go .rs .sh .ps1 .psm1 .psd1 .toml .ini .env .config .csproj .props .targets .razor .vue .svelte


License

MIT — see LICENSE for details.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.