⚡Config Installation
Add this to your claude_desktop_config.json:
{
"mcpServers": {
"dealx": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-dealx"
]
}
}
}* Note: Requires restart of Claude Desktop app.
Deployment Infrastructure
Adoption Framework for DealX
Before installing any skill, define a clear objective and measurable outcome. A useful implementation question is: what workflow becomes faster, safer, or more reliable after this skill is active? If that answer is vague, delay rollout and tighten scope first.
For most teams, a low-risk pattern is preview-first rollout with one owner, one test scenario, and one rollback plan. Capture failures in a structured log so quality decisions are evidence-based. This is especially important for skills that touch file systems, external APIs, or automation chains with downstream side effects.
- Define success metrics before installation.
- Validate permission scope against policy boundaries.
- Run one controlled pilot and document failure categories.
- Promote only after acceptance checks pass consistently.
Pre-Deployment Review Questions
Use these questions before enabling the skill in shared environments. They reduce surprise incidents and make approval decisions consistent across teams.
- What data can this skill read, write, or transmit by default?
- Which failures are recoverable automatically and which require manual stop?
- Do we have verifiable logs that prove safe behavior under load?
- Is rollback tested, documented, and assigned to a clear owner?
If any answer is unclear, keep rollout in preview and close the gap before production use.
Editorial Review Snapshot
This listing includes an editorial QA layer in addition to automated rendering. Review status is based on documentation depth, content uniqueness, and operational safety signals from the upstream repository.
- Last scan date: 2026-01-18
- README depth: 1105 words
- Content diversity score: 0.48 (higher is better)
- Template signal count: 0
- Index status: Index eligible
Recommendation: Pilot in a bounded environment first. Confirm observability and ownership before promoting to shared workflows.
Skill Implementation Board
Actionable utility module for rollout decisions. Use the inputs below to choose a deployment path, then execute the checklist and record an output note.
Input: Security Grade
B
Input: Findings
0
Input: README Depth
1105 words
Input: Index State
Eligible
| Decision Trigger | Action | Expected Output |
|---|---|---|
| Input: risk band moderate, docs partial, findings 0 | Run a preview pilot with fixed ownership and observability checkpoints. | Pilot can start with rollback checklist attached. |
| Input: page is index-eligible | Proceed with external documentation and team onboarding draft. | Reusable rollout runbook ready for team adoption. |
| Input: context tags/scenarios are missing | Define two concrete scenarios before broad rollout. | Clear scope definition before further deployment. |
Execution Steps
- Capture objective, owner, and rollback contact.
- Run one preview pilot with fixed test scenario.
- Record warning behavior and recovery evidence.
- Promote only if pilot output matches expected threshold.
Output Template
skill=dealx mode=B pilot_result=pass|fail warning_count=0 next_step=rollout|patch|hold
🛡️ Security Analysis
Clean Scan Report
Our static analysis engine detected no common vulnerabilities (RCE, API Leaks, Unbounded FS).
DocumentationREADME.md
@dealx/mcp-server
This is a Model Context Protocol (MCP) server for the DealX platform. It allows LLMs to interact with the DealX platform, specifically to search for ads.
Table of Contents
Overview
The DealX MCP Server implements the Model Context Protocol to provide a standardized way for LLMs to interact with the DealX platform. Currently, it supports searching for ads, with plans to add more functionality in the future.
What is MCP?
The Model Context Protocol (MCP) is a standardized way for LLMs to interact with external systems. It provides a structured interface for LLMs to access data and perform actions in the real world. This server implements the MCP specification to allow LLMs to interact with the DealX platform.
Installation
Prerequisites
- Node.js (v20 or later)
- npm (v11 or later)
MCP Configuration
To use this server with an LLM like Claude, you need to add it to your LLM's MCP configuration:
-
Open your LLM's MCP configuration file:
- Claude Desktop App:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
- macOS:
- Cline (VS Code Extension):
~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Claude Desktop App:
-
Add the DealX MCP server to the
mcpServerssection:{ "mcpServers": { "dealx": { "command": "npx", "args": ["-y", "@dealx/mcp-server"], "env": { "DEALX_API_URL": "https://dealx.com.ua" }, "disabled": false, "autoApprove": [] } } }
Installation via npm
The easiest way to install the DealX MCP Server is via npm:
npm install -g @dealx/mcp-server
Installation for Development
If you want to modify the server or contribute to its development:
-
Clone the repository:
git clone <repository-url> cd dealx/mcp -
Install dependencies:
npm install -
Create a
.envfile based on the.env.examplefile:cp .env.example .env -
Edit the
.envfile to set the appropriate values:# DealX API URL DEALX_API_URL=http://localhost:3001 # Optional: Specify the port for the MCP server MCP_SERVER_PORT=3100 # Optional: Log level (debug, info, warn, error) LOG_LEVEL=info -
Build the server:
npm run build
Usage
Starting the Server
You can run the server in several ways:
-
If installed globally:
node node_modules/@dealx/mcp-server/build/index.js -
Using npx without installation:
npx -y @dealx/mcp-server -
With environment variables:
DEALX_API_URL=https://dealx.com.ua npx -y @dealx/mcp-server -
For development:
npm start
Using with an LLM
Once configured in your LLM's MCP settings, you can use natural language to interact with the DealX platform.
Example prompts:
- "Search for ads on DealX with the query 'laptop'"
- "Find the newest 5 ads for 'iPhone' on DealX"
- "Search DealX for apartments in Kyiv"
Available Tools
search_ads
Search for ads on the DealX platform.
Parameters:
query(string, optional): Search query stringsort(string, optional): Sort order (e.g., "-created" for newest first)offset(number, optional): Pagination offset (starts at 1, default: 1)limit(number, optional): Number of results per page (max 100, default: 30)
Example Usage:
{
"query": "laptop",
"sort": "-created",
"offset": 1,
"limit": 10
}
Extending the Server
The server is designed to be easily extended with additional tools. Here's how to add a new tool:
-
Define the tool in the
TOOLSobject insrc/index.ts:const TOOLS = { SEARCH_ADS: "search_ads", NEW_TOOL: "new_tool", // Add your new tool here }; -
Create a new file in the
src/toolsdirectory for your tool implementation:// src/tools/new-tool.ts import { ErrorCode, McpError } from "@modelcontextprotocol/sdk/types.js"; interface NewToolParams { // Define your tool parameters here } export async function newTool(params: NewToolParams) { try { // Implement your tool logic here return { content: [ { type: "text", text: JSON.stringify(result, null, 2), }, ], }; } catch (error) { // Handle errors // ... } } -
Add the tool to the
ListToolsRequestSchemahandler insrc/index.ts:this.server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: [ // Existing tools... { name: TOOLS.NEW_TOOL, description: "Description of your new tool", inputSchema: { type: "object", properties: { // Define your tool parameters here }, required: [], // List required parameters }, }, ], })); -
Add the tool to the
CallToolRequestSchemahandler insrc/index.ts:this.server.setRequestHandler(CallToolRequestSchema, async (request) => { const { name, arguments: args } = request.params; switch (name) { // Existing cases... case TOOLS.NEW_TOOL: return await newTool(args); default: throw new McpError(ErrorCode.MethodNotFound, `Unknown tool: ${name}`); } }); -
Import your new tool in
src/index.ts:import { newTool } from "./tools/new-tool.js";
Planned Future Tools
The following tools are planned for future implementation:
create_ad: Create a new ad on the DealX platformedit_ad: Edit an existing addelete_ad: Delete an adget_threads: Get discussion threads for an adcreate_thread: Create a new discussion thread
Development
Project Structure
mcp/
├── build/ # Compiled JavaScript files
├── src/ # TypeScript source files
│ ├── tools/ # Tool implementations
│ │ └── search-ads.ts
│ └── index.ts # Main server implementation
├── .env # Environment variables (not in git)
├── .env.example # Example environment variables
├── package.json # Project dependencies and scripts
├── tsconfig.json # TypeScript configuration
└── README.md # This file
npm Scripts
npm run build- Compile TypeScript to JavaScriptnpm start- Start the server using the compiled JavaScriptnpm run dev- Start the server in development mode with hot reloadingnpm run lint- Lint the code using ESLintnpm run format- Format the code using Prettiernpm test- Run tests
Troubleshooting
Common Issues
Server Not Starting
If the server fails to start, check the following:
- Make sure you have the correct Node.js version installed
- Check that all dependencies are installed
- Verify that the
.envfile exists and has the correct values - Check the console output for error messages
Connection Issues
If the LLM can't connect to the server:
- Make sure the server is running
- Check that the MCP configuration in the LLM's settings is correct
- Verify that the path to the server executable is correct
- Check that the environment variables are set correctly
API Connection Issues
If the server can't connect to the DealX API:
- Make sure the DealX API is running
- Check that the
DEALX_API_URLenvironment variable is set correctly - Verify that the API endpoint is accessible from the server
Getting Help
If you encounter issues not covered here, please open an issue against this GitHub repository.