You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/TALXIS.CLI.MCP/README.md
+34-13Lines changed: 34 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,25 +4,46 @@ This project hosts a ModelContextProtocol (MCP) server for the TALXIS CLI, adver
4
4
5
5
## Features
6
6
- Dynamic discovery of CLI commands and subcommands using reflection
7
-
- Implements MCP ListTools and CallTool handlers
7
+
- Implements MCP ListTools and CallTool handlers
8
8
9
-
## Usage
9
+
## Debugging and Testing Locally
10
10
11
-
Build and run the server:
11
+
You can debug and test the MCP server locally in two main ways:
12
12
13
-
```sh
14
-
dotnet run --project src/TALXIS.CLI.MCP
15
-
```
16
-
17
-
The server will listen for MCP stdio requests and advertise available CLI tools.
18
-
19
-
20
-
## Debugging Locally
13
+
### 1. Using the Model Context Protocol Inspector
21
14
22
-
You can debug the MCP server locally using the [Model Context Protocol Inspector](https://www.npmjs.com/package/@modelcontextprotocol/inspector):
15
+
You can use the [Model Context Protocol Inspector](https://www.npmjs.com/package/@modelcontextprotocol/inspector) for interactive inspection and debugging:
23
16
24
17
```sh
25
18
npx @modelcontextprotocol/inspector dotnet run --project src/TALXIS.CLI.MCP
26
19
```
27
20
28
-
This will launch the MCP Inspector and connect it to the running server for interactive inspection and debugging.
21
+
This will launch the MCP Inspector and connect it to the running server.
22
+
23
+
### 2. Using VS Code with `.vscode/mcp`
24
+
25
+
You can also test the MCP server integration with VS Code by opening another window and adding a `.vscode/mcp` file to your project with the following content:
0 commit comments