Humans & AI

MCP Protocol Studio

Design tools, resources, and auth boundaries for a Model Context Protocol server — the FDE integration surface.

MCP Protocol Studio

FDE · integration surface

Design a minimal Model Context Protocol server for a customer who wants Claude to read and update a behavior policy (think dials / org playbooks). Score is on protocol judgment — schemas, side effects, auth, refuse lines.

Customer brief

“We need Claude Desktop / Code to load our team’s operating rules and let power users adjust verification level. Don’t let random chat rewrite production config. Multi-tenant later.”

Tools

Name (snake_case)Side effect

Description (what the model sees)Input JSON Schema (string)

Resource URIResource description

Auth & tenancy boundaryRefuse / safety line (operational)

Design score: 25/100

Add at least two tools (read + action).
Mix read-only tools with write tools when the product needs actions.
Name the auth boundary (OAuth, token, tenant scope).
Write an operational refuse line for out-of-scope or unsafe tool calls.