@aws/nx-plugin-mcp 1.0.0-rc.7 → 1.0.0-rc.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bin/aws-nx-mcp.js +977 -243
- package/docs/guides/py-mcp-server.mdx +5 -1
- package/docs/guides/ts-mcp-server.mdx +5 -1
- package/package.json +1 -1
|
@@ -117,12 +117,16 @@ def dynamic_resource(item_id: str) -> str:
|
|
|
117
117
|
|
|
118
118
|
### Inspector
|
|
119
119
|
|
|
120
|
-
The generator configures a target named `<your-server-name>-inspect`, which starts the [MCP Inspector](https://github.com/modelcontextprotocol/inspector)
|
|
120
|
+
The generator configures a target named `<your-server-name>-inspect`, which starts your MCP server locally (via the `<your-server-name>-serve-local` target, including any connected dependencies such as a local database) and launches the [MCP Inspector](https://github.com/modelcontextprotocol/inspector) pre-configured to connect to it over Streamable HTTP transport.
|
|
121
121
|
|
|
122
122
|
<NxCommands commands={['your-server-name-inspect your-project']} />
|
|
123
123
|
|
|
124
124
|
This will start the inspector at `http://localhost:6274`. Get started by clicking on the "Connect" button.
|
|
125
125
|
|
|
126
|
+
:::tip
|
|
127
|
+
To inspect the server using STDIO transport instead, use the `<your-server-name>-inspect-stdio` target, which launches the inspector against a STDIO instance of your server.
|
|
128
|
+
:::
|
|
129
|
+
|
|
126
130
|
### STDIO
|
|
127
131
|
|
|
128
132
|
The easiest way to test and use an MCP server is by using the inspector or configuring it with an AI assistant (as above).
|
|
@@ -122,12 +122,16 @@ server.registerResource('dynamic-resource', 'dynamic://resource', {}, async (uri
|
|
|
122
122
|
|
|
123
123
|
### Inspector
|
|
124
124
|
|
|
125
|
-
The generator configures a target named `<your-server-name>-inspect`, which starts the [MCP Inspector](https://github.com/modelcontextprotocol/inspector)
|
|
125
|
+
The generator configures a target named `<your-server-name>-inspect`, which starts your MCP server locally (via the `<your-server-name>-serve-local` target, including any connected dependencies such as a local database) and launches the [MCP Inspector](https://github.com/modelcontextprotocol/inspector) pre-configured to connect to it over Streamable HTTP transport.
|
|
126
126
|
|
|
127
127
|
<NxCommands commands={['your-server-name-inspect your-project']} />
|
|
128
128
|
|
|
129
129
|
This will start the inspector at `http://localhost:6274`. Get started by clicking on the "Connect" button.
|
|
130
130
|
|
|
131
|
+
:::tip
|
|
132
|
+
To inspect the server using STDIO transport instead, use the `<your-server-name>-inspect-stdio` target, which launches the inspector against a STDIO instance of your server.
|
|
133
|
+
:::
|
|
134
|
+
|
|
131
135
|
### STDIO
|
|
132
136
|
|
|
133
137
|
The easiest way to test and use an MCP server is by using the inspector or configuring it with an AI assistant (as above).
|