Connect a tool to Claude Code with MCP

Name a tool and the data you need; Claude Code finds a trustworthy MCP server, shows the add command first, connects it and checks it with one read.

Task: Connect a tool to Claude Code with MCP · Other tasks

Fill in the details

Tool to connect (required)

What Claude should read from it (required)

Who gets the connection

Setup details you have

Optional. A server URL or package name from the vendor. Never paste tokens or passwords here.

Copy your prompt

This site doesn't run Claude or show model output. Results depend on your input and the model you use.

Your prompt (you can edit it)

Connect [fill in: Tool to connect] via MCP so you can read its [fill in: What Claude should read from it] directly. Add it with local scope, only for me in this project.

Steps:
1. Find the MCP server for this tool. Prefer one published by the tool's vendor or listed in the Anthropic Directory, and tell me where it comes from before adding it. If you cannot find one you can trust, stop and tell me.
2. Show me the exact claude mcp add command and wait for my go-ahead before running it.
3. Never put a token or password in a command, a file or this chat. If the server needs one, tell me how to supply it myself, for example by signing in through /mcp.
4. Prefer read-only access. If the server also has tools that write or delete, list them.
5. Check the connection: run claude mcp list, or ask me to check /mcp, then make one small read of [fill in: What Claude should read from it] to show it works.

Report: the command used, where the configuration was saved, the tools the server offers, the result of the test read, and anything I still have to do, such as signing in or approving the server.

2 required fields are empty.

What you type is kept in this tab's session storage so a reload doesn't lose it. Use "Clear this task" to remove it. Browsers can restore session data when they reopen tabs, so closing a tab isn't a guaranteed way to erase it.

When to use this template

You keep copying data from one tool into Claude Code, such as stack traces from an error tracker or tickets from an issue tracker, and want Claude to read it directly.
The tool offers an MCP server, or you know where to find one, and you can sign in to it or create an access token yourself.
You want the team to share the same connection, through a project-scoped .mcp.json file committed to the repository.

When not to use it

You already use the tool as a claude.ai connector. If you sign in to Claude Code with that claude.ai account, connectors appear in /mcp without extra setup.
You need the data once. Paste it or export a file; a permanent connection is not worth setting up for one question.
The server fetches content from outside your organization and you have not checked who publishes it. Untrusted servers can expose you to prompt injection, so verify the source first.

Why this structure

Naming the tool and the data you need gives Claude a concrete test at the end: one read of that data proves the connection works for your purpose.
The scope choice maps onto the documented installation scopes: local and user stay private to you, project is shared through .mcp.json.
Asking where the server comes from before adding it, and preferring a vendor or Directory source, lets you judge the source before anything is connected.
Showing the add command first and keeping tokens out of commands, files and chat means credentials are handled by you, not written into the repository.
The report lists the tools the server offers and any write or delete tools, so you know what Claude can now do in that system.

Example input (fictional)

Tool to connect

our error tracker

What Claude should read from it

stack traces

Who gets the connection

local scope, only for me in this project

Setup details you have

The vendor documents a remote MCP URL that uses OAuth sign-in.

Follow-ups to send Claude

Using the new connection, show me the three most frequent errors from the last day with their stack traces.
Add a line to CLAUDE.md saying when to use this server and which tools to avoid.
Require my approval before any tool on this server that writes or deletes. How do I set that up?

Common mistakes

Pasting an API token into the chat or the command. Sign in through /mcp, or supply it yourself, so it does not end up in history or a committed file.
Committing a project-scoped server that needs a personal credential. Teammates then get a failing server, or you share your access.
Skipping the test read. A server can be added without being connected; check that it shows as connected and returns real data.

Query logs in plain English: Ask Claude Code a question about your logs; it writes a read-only query, runs it, and shows the query, the results and what stands out.
Investigate a production incident: Give Claude Code the symptom and when it started; it checks logs, recent deploys and config changes, then names the most likely cause with evidence.
Turn a repeated task into a skill: Describe a workflow you repeat and have Claude Code save it as a skill, so you or your team can run it later as a slash command.

See all templates

Sources

Claude Code docs: Prompt library (Anthropic documentation)
Claude Code docs: Connect Claude Code to tools via MCP (Anthropic documentation)
Claude Code docs: MCP installation scopes (Anthropic documentation)
Claude Code docs: Use MCP servers from claude.ai (Anthropic documentation)