Get the best of Think Different in your inbox

One email a month: new articles, reviews and the upcoming live webinar + free recording. No spam, unsubscribe anytime.

Tag: mcp

More posts tagged mcp

  1. MCP servers: Exposing read-only resources before you expose write actions
  2. MCP servers: Smallest MCP server that earns its keep
  3. MCP servers: Where the protocol ends and your product begins
  4. MCP servers: Sandboxing MCP tool calls so one bad prompt cannot ruin a week
  5. MCP servers: Versioning MCP servers like APIs, not like scripts
  6. MCP servers: Why your wiki should probably be an MCP resource
  7. MCP servers: Composing agents over a catalogue of shared MCP tools
  8. MCP servers: Least-privilege auth for MCP in a real enterprise
  9. MCP servers: Testing MCP servers with a plain JSON-RPC client first
  10. MCP servers: Treating MCP servers as a supply chain, not a side project
  11. MCP servers: Exposing read-only resources before you expose write actions
  12. MCP servers: Smallest MCP server that earns its keep
  13. MCP servers: First comparison between MCP and home-grown tool plumbing
  14. MCP servers: Testing MCP servers with the same rigor as customer-facing APIs
  15. MCP servers: Teaching the team MCP through a single example server
  16. MCP servers: What the protocol gave us and what our product still had to
  17. MCP servers: First MCP server a security review actually approved
  18. MCP servers: Observability gaps that bit us exactly once
  19. MCP servers: Versioning MCP servers like APIs, a first-year habit
  20. MCP servers: First sandboxing policy we wished we had started with
  21. MCP servers: Why we promoted an internal wiki to an MCP resource
  22. MCP servers: Composing agents over a tiny catalogue of shared tools
  23. MCP servers: First auth model we picked, and later regretted
  24. MCP servers: Early protocol tour, done with a plain JSON-RPC client
  25. MCP servers: Exposing read-only resources before we dared expose actions
  26. MCP servers: First MCP server that earned its keep
  27. MCP servers: First comparison between MCP and home-grown tool plumbing
  28. MCP servers: Testing MCP servers with the same rigor as customer-facing APIs
  29. MCP servers: Teaching the team MCP through a single example server
  30. MCP servers: What the protocol gave us and what our product still had to
  31. MCP servers: First MCP server a security review actually approved
  32. MCP servers: Observability gaps that bit us exactly once
  33. MCP servers: Versioning MCP servers like APIs, a first-year habit
  34. MCP servers: First sandboxing policy we wished we had started with
  35. MCP servers: Why we promoted an internal wiki to an MCP resource
  36. MCP servers: Composing agents over a tiny catalogue of shared tools
  37. MCP servers: First auth model we picked, and later regretted
  38. MCP servers: Early protocol tour, done with a plain JSON-RPC client
  39. MCP servers: Exposing read-only resources before we dared expose actions
  40. MCP servers: First MCP server that earned its keep