MCP examples for files, CRMs, spreadsheets, browsers, and internal systems

Design the capability you need

MCP integrations can expose capabilities from files, business systems, or other tools, depending on the server and host. The following examples are proposed designs, not promises that a particular product supplies these features. Always inspect the actual capabilities before planning a workflow around them.

For files, a narrow server could read documents in one approved folder. For a customer relationship management system, or CRM, it could retrieve the status of one fictional customer record. Neither design needs unrestricted access to all files or every customer.

Walk across several systems carefully

Imagine preparing a weekly stock note. A spreadsheet capability reads named cells containing product counts. A browser capability opens a supplier's public notice. An internal-system capability retrieves the latest approved reorder threshold. The assistant compares these inputs and drafts a note for review.

Use stable record identifiers, named ranges, or exact document references rather than relying only on display names. Two sheets might both contain a 'Total' row. Confirm units and timestamps too: a stock count in boxes should not be compared directly with a threshold in individual items.

Separate observation from changing records

Reading a count and updating an order are different operations. Keep the practice design read-only until the draft is reliable. If you later add a write, show the exact target, proposed value, and original value before the user approves it.

A useful result should explain where each important value came from and mark missing inputs. If a server fails, stop the dependent comparison rather than guessing. Inspect which data crosses each connection, and avoid copying private records into logs unnecessarily.

Explore the source

• MCP: server features and examples