tsai
/
abp
mirror of https://github.com/abpframework/abp.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Browse Source

Update post.md

pull/25627/head
berkansasmaz 4 months ago
parent
77f9423101
commit
158a15658c
1 changed files with 0 additions and 2 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 2
      docs/en/Community-Articles/2026-06-18-deep-dive-5-mcp/post.md

2
docs/en/Community-Articles/2026-06-18-deep-dive-5-mcp/post.md
View File

@ -87,5 +87,3 @@ Put simply: built-in tools handle everything inside the solution, MCP handles th
MCP is the agent's connection to everything that is not in your solution. MCP is the agent's connection to everything that is not in your solution.
You will not need it for most ABP work, because the built-in tools already cover the solution itself. But when a task depends on a ticket, an external system, or knowledge that lives somewhere else, MCP lets the agent reach it through one standard, with you deciding which servers and which tools it is allowed to use. You will not need it for most ABP work, because the built-in tools already cover the solution itself. But when a task depends on a ticket, an external system, or knowledge that lives somewhere else, MCP lets the agent reach it through one standard, with you deciding which servers and which tools it is allowed to use.
That is the balance worth remembering: **built-in tools for the solution, MCP for the world around it, and you in control of the door between them.**

Write Preview
Loading…
Cancel
Save