Tag: mcp
All the articles with the tag "mcp".
-
Two Ways to Authorize an Agent Tool: IAM or OAuth on Amazon Bedrock AgentCore Gateway
When you expose a tool to agents through an AgentCore Gateway, the real decision is who is allowed to call it — SigV4/IAM for callers inside your AWS boundary, or a JWT authorizer for everyone else. Here are the three patterns and when each fits.
-
How AgentCore Gateway Turns Any API Into an Agent Tool
AgentCore Gateway is a managed front door between agents and tools. It handles inbound auth, outbound auth, and protocol translation once, so any API or Lambda becomes an MCP tool that every connected agent can call. Here is how the wiring actually works.
-
The Enterprise MCP Pattern: Proxy, Aggregate, Host
There are 58 public MCP servers in the awslabs catalog covering cloud infrastructure, databases, AI/ML, and ops tooling. Here's the enterprise pattern: proxy them locally, then host the proxy behind a gateway so every developer in your org gets them without setup.
-
The Website Is Not the Product
AI crawlers are extracting content at 60,000 pages per visitor sent back. The website is becoming a fallback UI. The real distribution layer is structured, machine-readable context — and nobody is building for it yet.
-
The Meta-Tool Pattern: Teaching Your Agent to Discover Its Own Tools
The MCP token tax has a fix. The solution isn't fewer tools — it's a smarter way to load them. Here's the pattern.
-
Building the MCP Proxy: What Broke and What I Changed
The proxy pattern from part two, built and debugged. Two things broke: a missing dependency that crashed startup silently, and a response format that made the model do unnecessary work.
-
The MCP Token Tax
MCP won the read path. The token tax is what happened next. And the write path still doesn't have an answer.
-
Build vs. Buy for AI Knowledge Infrastructure: Capability First, Cost Second
SaaS platforms auto-generate MCP servers. But auto-generated MCP does text search. If your use case requires metadata-filtered retrieval, you're comparing different architectures — not different feature sets. Capability first, cost second.