Kevin Aubrée

AI Coding /

Useful MCP for AI coding: logs, issues, and docs only when it removes copy-paste

MCP is not magic. It becomes useful when it replaces repetitive manual transfer between a real tool and your coding agent.

Duration

9 min

Level

Intermediate

Tools

MCP · Claude Code · Codex

Useful MCP for AI coding: logs, issues, and docs only when it removes copy-paste

MCP is easy to oversell.

Connecting ten servers does not make your agent better. Sometimes it only gives the agent more ways to be wrong, more permissions to watch, and more context to sort.

The useful criterion is simpler: does MCP remove real copy-paste?

1. Good candidates

An MCP server is worth it when you often:

  • copy a GitHub issue into the prompt;
  • paste production logs;
  • search internal docs;
  • retrieve ticket state;
  • check a metric before fixing code.

If the tool is rarely used, keep a link or manual excerpt. Integration is not free: installation, permissions, maintenance, debugging.

2. Three integrations that matter

Issues: the agent reads context, comments, and acceptance criteria. Good for avoiding incomplete prompts.

Logs: the agent inspects the real error instead of reasoning from an approximate description. Good for debugging.

Docs: the agent checks the current API or convention instead of working from memory. Good for frameworks and products that change fast.

The common point: the external source changes the code decision.

3. What not to connect

Avoid MCP for:

  • tools you do not use;
  • noisy sources;
  • broad access;
  • sensitive data without a precise need;
  • integrations nobody maintains.

An agent with access to everything is not productive. It is hard to audit.

4. Write the workflow before the integration

Before adding a server, write:

  • what question the agent should ask the tool;
  • when in the workflow;
  • what output is expected;
  • what it must not do;
  • how you verify the action.

Example:

For a production bug, the agent may read logs from the last 30 minutes.
It must not modify production config.
It returns hypothesis, suspicious file, evidence, then local patch.

That rule is better than broad integration without a clear use.

5. Value test

After a week, ask:

  • how much copy-paste disappeared?
  • how often did the agent use the source?
  • how many answers improved because of it?
  • how many permissions did I have to watch?

If you cannot answer, remove the integration.

Sources

Keep learning

Back to tutorials