DoneThat
Back to AI Adoption Guide

MCP

MCP gives AI assistants controlled access to tools, documents, repositories, and work history, turning repeated copy paste context into scoped integrations.

Overview

MCP gives AI assistants controlled access to tools, documents, repositories, and work history, turning repeated copy-paste context into scoped integrations.

What it is, how it works

  • A standard way for AI assistants to use external tools and context sources.
  • Useful for search, repository context, internal docs, task systems, and structured actions.
  • Turns AI from a blank chat box into a context-aware work surface.

When not to use it

  • Do not use when copy-paste is enough.
  • Do not use before permissions, scopes, and auditability are clear.
  • Do use when repeated tasks need the same trusted data sources or tools.

How to get started

  • Pick one high-value context source.
  • Define read-only access before adding write actions.
  • Scope tools to the smallest useful permission set.
  • Test with realistic questions and failure cases.

Best practices / further reading