Improve discoverability and guidance for the MCP/Studio CLI. Added a note in the CLI docs that the mcp-studio bridge is invoked automatically by AI tools (no manual run required) and that `abp help mcp-studio` shows options and IDE config snippets. Also added a Quick Reference entry to the Model Context Protocol doc pointing users to `abp help mcp-studio` for example configurations.
Starts an MCP stdio bridge for AI tools (Cursor, Claude Desktop, VS Code, etc.) that connects to the local ABP Studio instance. ABP Studio must be running for this command to work.
> You do not need to run this command manually. It is invoked automatically by your AI tool once you add the MCP configuration to your IDE. See the [Configuration](#configuration) examples below.
> This command connects to the **local ABP Studio** instance. It is separate from the `abp mcp` command, which connects to the ABP.IO cloud MCP service and requires an active license.
For detailed configuration examples (Cursor, Claude Desktop, VS Code) and the full list of available MCP tools, see the [Model Context Protocol (MCP)](../studio/model-context-protocol.md) documentation.
> You can also run `abp help mcp-studio` to see available options and example IDE configuration snippets directly in your terminal.
### generate-razor-page
`generate-razor-page` command to generate a page class and then use it in the ASP NET Core pipeline to return an HTML page.
@ -81,6 +81,10 @@ Claude Desktop config file locations:
}
```
### Quick Reference
You can run `abp help mcp-studio` at any time to see the available options and example configuration snippets for each supported IDE directly in your terminal.
### Generating Config Files from ABP Studio
When creating a new solution, ABP Studio can generate MCP configuration files for Cursor and VS Code automatically.