"Description": "Capability matrix for ABP Studio AI Agent modes, built-in tools, Studio automation tools, subagents, and hidden tool boundaries."
"Description": "Capability matrix for ABP Studio AI Agent modes, built-in tools, Studio automation tools, connected MCP tools, subagents, and hidden tool boundaries."
}
```
@ -17,7 +17,7 @@
}
````
ABP Studio exposes tools to the AI Agent based on the selected mode, run context, tool settings, and permissions. The tool list is locked per running Agent-mode session to keep prompt caching and execution stable while other sessions run in parallel.
ABP Studio exposes tools to the AI Agent based on the selected mode, run context, tool settings, permissions, and connected MCP server tools. The tool list is locked per running Agent-mode session to keep prompt caching and execution stable while other sessions run in parallel.
## Mode Capability Matrix
@ -41,6 +41,7 @@ ABP Studio exposes tools to the AI Agent based on the selected mode, run context
| Update active plan steps | Yes | No | No |
| Search/read ABP docs directly | No | No | Yes |
| Studio automation tools | Yes | No | No |
| Connected MCP tools | Yes | No | No |
| Spawn subagents | Yes | Yes | Yes |
ABP documentation tools are available to Ask mode and ABP documentation subagents. The main Agent-mode tool list does not include direct ABP docs search/read tools; Agent mode can use the ABP documentation subagent when documentation research is needed.
@ -137,6 +138,18 @@ The `spawn_subagent` tool delegates bounded research work to read-only specialis
Subagents are read-only. They are intended for parallel research and return summarized findings to the main agent.
## MCP Tools
Configured MCP server tools can be added to Agent mode when:
- The MCP server is configured and enabled.
- The server connection is successful.
- The individual MCP tool is not disabled in settings.
MCP resources are visible in settings and can be opened for inspection, but the Agent-mode callable surface is composed from MCP tools. Plan and Ask modes do not receive MCP tools.
This capability lets the AI Agent consume tools from external MCP servers. It does not make ABP Studio AI Agent an MCP server for external clients.
## Tool Execution Gates
ABP Studio serializes selected operations to reduce parallel-session conflicts.
"Description": "Configuration reference for ABP Studio AI Agent models, reasoning, context limits, parallel sessions, permissions, AI rules, and learned lessons."
"Description": "Configuration reference for ABP Studio AI Agent models, reasoning, context limits, parallel sessions, permissions, MCP tool connections, AI rules, and learned lessons."
}
```
@ -17,7 +17,7 @@
}
````
AI Agent configuration controls model selection, execution limits, enabled tools, tool permissions, AI rules, and learned lessons.
AI Agent configuration controls model selection, execution limits, enabled tools, tool permissions, MCP tool connections, AI rules, and learned lessons.
## Model Provider
@ -100,6 +100,25 @@ Some tools require explicit permission before execution.
Permission choices include allow once, allow always, and skip. "Allow always" persists in the AI Agent settings and is reused by future sessions.
## MCP Tool Connections
ABP Studio can connect to user-configured Model Context Protocol (MCP) servers and expose their tools to Agent mode. This is an MCP client integration for the AI Agent. ABP Studio AI Agent does not expose itself as an MCP server for external AI clients.
MCP server connections can be configured with:
| Transport | Configuration |
| --- | --- |
| Stdio | Command, arguments, and environment variables. |
| HTTP | URL and headers. |
Studio imports MCP server configuration from Cursor, Claude, VS Code, Windsurf, and bare MCP server JSON formats. Studio exports MCP server configuration in the standard `mcpServers` JSON shape.
Connected MCP servers show their connection status, tool count, tools, and resources. Individual MCP tools can be disabled. Disabled MCP tools are omitted from Agent mode. MCP resources can be opened from settings for inspection.
MCP tools are added only for connected and enabled servers. Plan and Ask modes do not receive MCP tools.
The `.abpignore` file is placed in the solution root and uses `.gitignore` syntax. Files matched by `.abpignore` are inaccessible to the agent even when they are under the active AI scope.
@ -29,7 +29,7 @@ The selected mode determines the agent's effective permission boundary.
| Mode | Purpose | Tool boundary |
| --- | --- | --- |
| Agent | Coding and execution | Can read and write files, run shell commands, add migrations, run enabled Studio tools, and update active plan steps. |
| Agent | Coding and execution | Can read and write files, run shell commands, add migrations, run enabled Studio tools, call connected MCP tools, and update active plan steps. |
| Plan | Read-only planning | Can inspect code and documentation, create or update plan files, and use read-only subagents. It cannot modify solution files or run shell/write tools. |
| Ask | Read-only question answering | Can inspect code, search/read ABP documentation, fetch relevant AI skills, and use read-only subagents. It cannot create plans or modify files. |
@ -94,4 +94,4 @@ When a run profile is active, the system prompt includes information about runna
## Privacy Boundary
The agent uses the files, prompts, Studio tool outputs, attachments, and URLs supplied to a session. Sensitive files can be excluded with `.abpignore`; tool permissions restrict shell commands, domain fetches, and downloads.
The agent uses the files, prompts, Studio tool outputs, connected MCP tool outputs, attachments, and URLs supplied to a session. Sensitive files can be excluded with `.abpignore`; tool permissions restrict shell commands, domain fetches, and downloads.
"Description": "Technical guidance for coding with ABP Studio AI Agent, including mode selection, scopes, prompting, verification, Git review handoff, Studio tools, and parallel sessions."
"Description": "Technical guidance for coding with ABP Studio AI Agent, including mode selection, scopes, prompting, verification, Git review handoff, Studio tools, MCP tools, and parallel sessions."
}
```
@ -25,7 +25,7 @@ Use the mode that matches the expected side effect.
| Work type | Mode |
| --- | --- |
| Code changes, migrations, builds, proxy generation, app/container control, or Studio tool execution | Agent |
| Code changes, migrations, builds, proxy generation, app/container control, Studio tool execution, or MCP tool execution | Agent |
| Technical implementation design before coding | Plan |
@ -106,6 +106,14 @@ Workflow actions can configure:
- C# target package.
- Whether C# contract classes are generated.
## MCP Tools
Use configured MCP tools when the agent must work with an external system that is not covered by built-in ABP Studio tools. MCP tools are available only in Agent mode, only when the MCP server is connected, and only when the individual tool is enabled.
Because MCP tools can have side effects defined by the connected server, keep MCP connections limited to trusted servers and disable tools that should not be callable by the AI Agent.
MCP tool configuration is for adding external tools to the AI Agent. It does not expose ABP Studio AI Agent as an MCP server for other AI clients.
## AI Rules And Lessons
Use always-apply AI rules for standards that should affect every run, such as architecture rules, naming conventions, security requirements, or team-specific ABP patterns.
@ -128,6 +136,6 @@ Common boundaries:
- Files matched by `.abpignore` are inaccessible.
- Image attachments require a model with image support.
- Shell, URL fetch, and download operations can wait for permission.
- Disabled Studio tools are omitted from the tool list.
- Disabled Studio tools and disabled MCP tools are omitted from the tool list.
- Plan and Ask modes cannot modify files.
- Hidden internal Studio tools are not exposed to the agent.
@ -101,7 +101,7 @@ This pane is dedicated to managing Kubernetes services. It simplifies the proces
### AI Agent
The AI Agent is an integrated coding agent in ABP Studio. It can answer ABP-related questions, create implementation plans, and work on the current solution with controlled access to files, Studio tools, workflows, and Git context.
The AI Agent is an integrated coding agent in ABP Studio. It can answer ABP-related questions, create implementation plans, and work on the current solution with controlled access to files, Studio tools, workflows, Git context, and configured MCP tools.
enisn
4 months ago
