Credentials and permissions
Each MCP server holds its own credentials; the host approves tool calls.
Difficulty 2/5
Short
Plain English
Each MCP server holds its own credentials; the host approves tool calls. Picture it like this: Each USB device knows its own driver. In the apps you ship (Agentify, wedding portals, CRM), you will bump into this on almost every screen — name it clearly when you prompt your coding agent.
Analogy
Each USB device knows its own driver.
Go deeper
Each MCP server holds its own credentials; the host approves tool calls.
Common mistakes
- Letting the AI rename this concept three different ways in one PR.
- Building UI before you can say what is stored and who can change it.
AI-agent trap
Agents may invent jargon here. Ask them to explain the concept in plain English first, then map it to your schema and one real screen.
Summary
Each MCP server holds its own credentials; the host approves tool calls. Each USB device knows its own driver. Ask yourself: where does this live in the database, which function changes it, and which screen shows it?
Confidence: