Before you connect a new connector or MCP server to your AI, check where it comes from, what it can do, what permissions you give, what information it receives, and how to remove it. Connecting is one click. Deciding takes five checks.
When you want to connect a new connector or MCP server to your AI. When a teammate asks, “Can I connect this?”.
Before you start
The name of what you want to connect, and its official page or URL. Your team’s generative AI usage guidelines, if you have them (Community Playbooks No.002).
Steps
Check where it comes from. See whether the provider’s official site or documents list that URL or name. Don’t connect URLs handed out by strangers, or anything whose origin you can’t tell.
List what it can do. For each tool, check whether it only reads, or also writes, sends or deletes.
Ask your AI
Using only official documents, list the following for this MCP server (connector) [name, URL].
Provider / each tool and whether it only reads or also writes, sends or deletes / whether it needs a login or API key / pricing and free limits / how what you send is handled (how long it is kept, whether it is used for training).
Write “unknown” for anything you can’t confirm in the documents.
Decide the scope. Give only what the work needs. If reading is enough, don’t grant write or send permissions. If you can pick folders or calendars, narrow them down.
Decide what information goes out. See what is sent to the server (search terms, file contents, etc.). If client or personal information would be sent, check your guidelines first.
Try it on your own first, without work information. Check that a confirmation appears before sending, deleting and other hard-to-undo actions.
Record who connected what and when, and how to remove it (where in the AI’s settings), in the agreed place.
✓ Done when
The provider, what it can do, the permissions given and the information sent are on one page.
The connection record and how to remove it are kept where the team can see them.
House rules
Grant write, send and delete permissions only when needed.
If the AI tries to send, forward or delete something you didn’t ask for, don’t approve it. Stop it and tell the contact.
This playbook publishes steps the CLUBS team actually uses. Under CC BY 4.0, you may adapt and redistribute it with attribution. If you change it, please say so.
This playbook is one example, provided for general information. We do not guarantee that it is accurate or up to date. Please check the content before you use it, and use it at your own risk.See the Terms of Service (Japanese) for details.