Skip to main content

Chapter 10 : Agent MCP Packs

What Are Agent MCP Packs​

Generate and Build Docker Containers for Agent MCP Packs mapped to your data sources. They include below.

  • AI Agents
  • MCP Server
  • APIs REST

Agent MCP Pack​

  • Agent MCP Pack Docker Containers

Agent MCP Pack records in EasyManage Builder app are created to re-present Agent MCP Pack docker containers. They help in knowing your containers and Testing.

  • Agent MCP Pack records in EasyManage Builder ← Agent MCP Pack docker containers

Agent MCP Pack Docker Container​

Run Agent MCP Pack In Docker Container​

To Build and Run In Docker Container, After code generate and Download,

Please follow steps given in README at e.g.:

  • Downloads\EmGenDir_MYTEMP01_WS_51247\WS_51247\README-Agent-MCP-Pack.md

e.g. Container created and run output:

EmGenDir_MYTEMP01_WS_51247\WS_51247>docker compose up -d
[+] up 4/4
 ✔ Network ws_51247_default         Created                                 0.0s
 ✔ Container ws_51247-emapi-1       Started                                 0.4s
 ✔ Container ws_51247-emmcp-1       Started                                 0.6s
 ✔ Container ws_51247-agentserver-1 Started                                 0.8s

Primary Agent MCP Pack​

If you have multiple MCP Servers mapped to various data sources, Make first Container's Agent MCP Pack as Primary. Add all your MCP Servers to its AgentServer configuration to get AI-Ready data from across all your data sources.

Use Primary Agent MCP Pack's Agent Server in EasyManage Builder : AI Agents : Agent Server Configuration.

Please see Readme mentioned README-Agent-MCP-Pack.md

- Container Setup Details : You can repeat these steps for next MCP containers.

MCP Tool Groups​

You can group tools from different MCP servers, across hybrid databses, into functional domain groups such as accounts-grp, inventory-grp.

Tool Groups Across Hybrid Databses​

For an e-commerce app, If you have database tables in Postgres and Snowflake, lets see how to formulate MCP Tool Groups.

Agents To MCP Visibility: Agents should get exposed to tools for a specific "Group", rather than all tools from Snowflake and Postgres MCP servers.

Define your groups in application properties to map which tables or tool patterns belong to which group.

  • Add to agent\spring-java\agentserver\src\main\resources\application.properties
## MCP Tool Groups : Tool Groups Across Hybrid Databases

em.mcptools.mcpgroupsEnabled=true

em.mcptools.mcpgroup.accounts-grp=user_profile|lifetime_value|account_master
em.mcptools.mcpgroup.inventory-grp=dailystock|warehouses

  • Optionally, Establish a Tool Naming Convention

    • Format: [group_name]_[db]_[tool]
    • Examples for accounts-grp:
      • accounts_psql_get_user_profile
      • accounts_snowflake_get_lifetime_value

  • Provision Agents with Specific Groups

    • Account Agent: Restrict to accounts-grp. It only sees the filtered list of tools from both databases.
    • Inventory Agent: Restrict to inventory-grp.

How to Use Tool Groups in Agents​

In Agent Project, Use it via Tool Name Incl property. It has dual role to include MCP Tool Groups and then also further filter tools within those groups.

  • Tool Name Incl: accounts-grp|inventory-grp
    • Add all tools from accounts-grp and inventory-grp
  • Tool Name Incl: accounts-grp|user_profile|lifetime_value
    • Add all tools from accounts-grp
    • Keep tools matching user_profile|lifetime_value only
  • Tool Name Incl: accounts-grp|user_profile|lifetime_value|inventory-grp|dailystock
    • Add all tools from accounts-grp
    • Keep tools matching user_profile|lifetime_value only
    • Add all tools from inventory-grp
    • Keep tools matching dailystock only
    • If you want to specify tool name matching, specify tool name conditions for all tool groups included.