Base Application MCP Server Pattern
The foundational MCP server pattern: exposes the core business actions for a single enterprise application as a governed, reusable tool set.
What Is the Base Application Server Pattern?
The Base Application Server pattern exposes the core business actions for a single enterprise application — Salesforce, ServiceNow, Workday, SAP — as a governed MCP tool set. It is the foundational pattern for enterprise MCP and the right starting point for most organizations.
A Base Application MCP server answers the question: "What should every AI agent be able to do with this system?" The tools it exposes are the atomic building blocks from which more complex patterns are assembled.
Design Guidelines
A well-designed Base Application server has:
- 10–25 tools — enough to cover the core business actions, few enough that the LLM can reliably select the right one
- Consistent naming — verb_noun format:
get_account,create_opportunity,update_contact,close_case - Business-action scope — no raw CRUD, no mirrored API endpoints
- Structured responses — every tool returns a consistent response object with status, data, and error fields
Enterprise Example: Salesforce Base Application Server
A Salesforce Base Application MCP server might include: get_account, search_accounts, get_contact, get_opportunity, create_opportunity, advance_opportunity_stage, close_opportunity, log_activity, create_case, update_case_status. This is 10 tools covering the core Salesforce business actions an agent might need.
Notice what's not in this list: raw SOQL queries, direct record updates by field name, bulk operations. Those are developer tools, not agent tools.
When to Use This Pattern
- You're starting your MCP implementation and building the first server for a key enterprise application
- You want a stable, reusable foundation that multiple agents can share
- The use cases are single-application: the agent primarily interacts with one system