Tag: model-context-protocol
-
MCP servers: Exposing read-only resources before you expose write actions
A field-tested take on exposing read-only resources before you expose write actions with MCP servers: what it rewards, where it breaks, and how to keep the workflow honest.
-
MCP servers: Smallest MCP server that earns its keep
A field-tested take on the smallest MCP server that earns its keep with MCP servers: what it rewards, where it breaks, and how to keep the workflow honest.
-
MCP servers: Where the protocol ends and your product begins
A field-tested take on where the protocol ends and your product begins with MCP servers: what it rewards, where it breaks, and how to keep the workflow honest.
-
MCP servers: Sandboxing MCP tool calls so one bad prompt cannot ruin a week
A field-tested take on sandboxing MCP tool calls so one bad prompt cannot ruin a week with MCP servers: what it rewards, where it breaks, and how to keep the workflow honest.
-
MCP servers: Versioning MCP servers like APIs, not like scripts
A field-tested take on versioning MCP servers like APIs, not like scripts with MCP servers: what it rewards, where it breaks, and how to keep the workflow honest.
-
Why your wiki should probably be an MCP resource, not a tool
Exposing internal documentation over MCP as a search tool means the model guesses when to look. Exposing it as a resource means the human decides. That distinction changes what the integration is good for.
-
MCP servers: Composing agents over a catalogue of shared MCP tools
A field-tested take on composing agents over a catalogue of shared MCP tools with MCP servers: what it rewards, where it breaks, and how to keep the workflow honest.
-
MCP servers: Least-privilege auth for MCP in a real enterprise
A field-tested take on least-privilege auth for MCP in a real enterprise with MCP servers: what it rewards, where it breaks, and how to keep the workflow honest.
-
MCP servers: Testing MCP servers with a plain JSON-RPC client first
A field-tested take on testing MCP servers with a plain JSON-RPC client first with MCP servers: what it rewards, where it breaks, and how to keep the workflow honest.
-
MCP servers: Treating MCP servers as a supply chain, not a side project
A field-tested take on treating MCP servers as a supply chain, not a side project with MCP servers: what it rewards, where it breaks, and how to keep the workflow honest.
-
MCP servers: Exposing read-only resources before you expose write actions
A field-tested take on exposing read-only resources before you expose write actions with MCP servers: what it rewards, where it breaks, and how to keep the workflow honest.
-
MCP servers: Smallest MCP server that earns its keep
A field-tested take on the smallest MCP server that earns its keep with MCP servers: what it rewards, where it breaks, and how to keep the workflow honest.
More posts tagged model-context-protocol
- MCP servers: Where the protocol ends and your product begins
- MCP servers: Sandboxing MCP tool calls so one bad prompt cannot ruin a week
- MCP servers: Versioning MCP servers like APIs, not like scripts
- MCP servers: Why your wiki should probably be an MCP resource
- MCP servers: Composing agents over a catalogue of shared MCP tools
- MCP servers: Least-privilege auth for MCP in a real enterprise
- MCP servers: Testing MCP servers with a plain JSON-RPC client first
- MCP servers: Treating MCP servers as a supply chain, not a side project
- MCP servers: Exposing read-only resources before you expose write actions
- MCP servers: Smallest MCP server that earns its keep
- MCP servers: First comparison between MCP and home-grown tool plumbing
- MCP servers: Testing MCP servers with the same rigor as customer-facing APIs
- MCP servers: Teaching the team MCP through a single example server
- MCP servers: What the protocol gave us and what our product still had to
- MCP servers: First MCP server a security review actually approved
- MCP servers: Observability gaps that bit us exactly once
- MCP servers: Versioning MCP servers like APIs, a first-year habit
- MCP servers: First sandboxing policy we wished we had started with
- MCP servers: Why we promoted an internal wiki to an MCP resource
- MCP servers: Composing agents over a tiny catalogue of shared tools
- MCP servers: First auth model we picked, and later regretted
- MCP servers: Early protocol tour, done with a plain JSON-RPC client
- MCP servers: Exposing read-only resources before we dared expose actions
- MCP servers: First MCP server that earned its keep
- MCP servers: First comparison between MCP and home-grown tool plumbing
- MCP servers: Testing MCP servers with the same rigor as customer-facing APIs
- MCP servers: Teaching the team MCP through a single example server
- MCP servers: What the protocol gave us and what our product still had to
- MCP servers: First MCP server a security review actually approved
- MCP servers: Observability gaps that bit us exactly once
- MCP servers: Versioning MCP servers like APIs, a first-year habit
- MCP servers: First sandboxing policy we wished we had started with
- MCP servers: Why we promoted an internal wiki to an MCP resource
- MCP servers: Composing agents over a tiny catalogue of shared tools
- MCP servers: First auth model we picked, and later regretted
- MCP servers: Early protocol tour, done with a plain JSON-RPC client
- MCP servers: Exposing read-only resources before we dared expose actions
- MCP servers: First MCP server that earned its keep