Understand the integration roles
The official MCP architecture distinguishes the application host, its clients and the servers that expose capabilities such as tools and resources. MCP defines how context is exchanged. The application still determines business workflows and authorization rules.
List the specific tasks to expose, such as reading an authorized document or querying a particular aggregate. Access to a general-purpose connection does not confer permission for every dataset and action.
Create a tool inventory
| Tool attribute | What to document |
|---|---|
| Purpose | The business task the tool serves and when to use it |
| Input | Structure, constraints, defaults and sensitive fields |
| Identity | The user or service identity under which it runs |
| Type of operation | Read-only, write or other action with an external effect |
| Output | Results, sources, failure states and size limits |
| Audit | How to associate the operation with a specific request |
Validate a read-only tool first
- Confirm the protocol versions, transports and authentication configurations supported by the deployment and client.
- Check the tools actually exposed and enable only those required for the task.
- Use synthetic inputs to test success, insufficient permissions, timeout and no results separately.
- Recheck access to sources and files in the output, then verify behavior after revocation.
Distinguish tool descriptions from permission to execute
Text, documents and web pages returned by a tool may include third-party instructions. Treat them as business content within the user's existing permissions. For writes, external sends and other business actions, follow the application's confirmation and audit rules.
Compatibility varies by MCP client and product release. Validate the published tool definitions, identity mapping and compatibility notes for the integration you are delivering.
