# JSON-RPC Published articles for JSON-RPC. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Patching This Site's MCP Endpoint and Limiting What It Can Do DevFeed: [Patching This Site's MCP Endpoint and Limiting What It Can Do]() Original publisher: [Read original article]() Author: Brent Leekley Published: 2026-09-08T00:00:00Z Content type: tutorial Language: en Sources: [brent.leekley.me blog]() Topics: [Model Context Protocol](), [MCP Server](), [API](), [HTTP](), [JSON]() Tags: [aeo](), [agent-ready-website](), [agentic-ai](), [agents](), [api](), [api-security](), [clients](), [json-rpc](), [logs](), [mcp](), [mcp-server](), [model-context-protocol](), [prompt-injection](), [protocol](), [rate-limiting](), [retry](), [server](), [streamable-http](), [webmcp]() ### AI overview This article explains how to patch a website's public, unauthenticated MCP endpoint. It covers updating to the current protocol revision while retaining compatibility with older clients, and applying limits including read-only tools, per-IP rate limiting, request-size caps, Origin checks, POST-only access, non-reflected strings, and privacy-preserving logs. ### Source excerpt An MCP server on your website is a public, unauthenticated API. Bringing one to the current protocol revision while keeping older clients working, and the seven limits that bound it: read-only tools, a per-IP rate limit that always sends Retry-After, hard caps on body and argument size, an https-only Origin check, POST only, no reflected strings, and logs that store a salted hash instead of an address. ## MCP vs API DevFeed: [MCP vs API]() Original publisher: [Read original article]() Author: Roger Perkin Published: 2026-08-14T07:35:02Z Content type: article Language: en Sources: [Roger Perkin Network Automation Consultant]() Topics: [MCP vs API](), [API](), [Model Context Protocol](), [AI Models](), [Protocol (disambiguation)]() Tags: [ai-models](), [api](), [json-rpc](), [mcp](), [mcp-vs-api](), [rest-apis](), [rpc](), [vs]() ### AI overview This article explains that MCP and APIs serve different purposes. APIs connect software systems through predefined endpoints, while MCP lets AI models discover and use tools dynamically. MCP does not replace APIs; it operates on top of existing APIs as a standardized, AI-friendly translation layer. ### Source excerpt Ever since MCP became popular, I hear people saying "does MCP replace APIs?" Or do they both solve completely different problems? Firstly the facts: APIs connect software systems through predefined endpoints, while MCP enables AI models to discover and use tools dynamically. So, they are two different things, but can MCP replace APIs? More discussions ... ## Bringing Temporal into your AI editor: How Coinbase debugs Workflows with MCP DevFeed: [Bringing Temporal into your AI editor: How Coinbase debugs Workflows with MCP]() Original publisher: [Read original article]() Author: Edward Zhu Published: 2026-05-26T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Model Context Protocol](), [coinbase](), [MCP Server](), [Artificial Intelligence](), [Python](), [API keys](), [Self-hosted](), [JSON](), [Cloud](), [Remote Procedure Call (RPC)]() Tags: [ai](), [api-keys](), [coinbase](), [how-to](), [json-rpc](), [mcp](), [mcp-server](), [python](), [self-hosted]() ### AI overview Coinbase describes a custom, read-only Temporal MCP server that lets engineers investigate workflow failures from an AI editor using natural-language queries. The server provides 10 tools, supports Temporal Cloud and self-hosted clusters, and runs locally over MCP stdio communication. ### Source excerpt How Coinbase engineers debug Temporal Workflows from their AI editor: a custom MCP server, 10 read-only tools, and 14,000+ calls in a couple of months. ## Inside the Google ADK and Temporal integration DevFeed: [Inside the Google ADK and Temporal integration]() Original publisher: [Read original article]() Author: Drew Hoskins Published: 2026-04-20T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Agent Framework](), [Artificial Intelligence](), [Google](), [Development](), [Python](), [Remote Procedure Call (RPC)](), [JSON](), [vercel ai sdk](), [OpenAI]() Tags: [agent-development-kit](), [agent-framework](), [agents](), [ai](), [announcements](), [distributed](), [google-adk](), [http](), [integration](), [json-rpc](), [python]() ### AI overview This article explains Temporal's integration with Google ADK. It describes Temporal as the durable execution layer while Google ADK provides the agent framework, and outlines an initial Python implementation using independent HTTP services and A2A JSON-RPC requests. The article also places the integration alongside Temporal's OpenAI Agents SDK and Vercel AI SDK integrations. ### Source excerpt Google ADK builds the agent and Temporal makes sure it finishes. Here's how our integration works under the hood and all it took to make it happen. ## Building transactional voice agents at Nector DevFeed: [Building transactional voice agents at Nector]() Original publisher: [Read original article]() Author: Pranshu Raj Published: 2026-03-07T13:39:58Z Content type: article Language: en Sources: [Pranshu Raj - blog on backend systems, performance and sidequests]() Topics: [Model Context Protocol](), [Latency](), [Multi-tenancy](), [Back end](), [observability](), [Database]() Tags: [agents](), [api](), [backend](), [database-design](), [json-rpc](), [latency](), [latency-optimization](), [mcp](), [multi-tenancy](), [observability](), [pii](), [production](), [proxy](), [rest-api](), [voice]() ### AI overview An engineer describes building customer-facing transactional voice agents for ecommerce at Nector. The article covers a REST-to-JSON-RPC MCP proxy that improved observability, PII control, context reduction, latency, and correctness, plus experiments that reduced one agent's p90 latency from more than 8 seconds to 2 seconds. ### Source excerpt Building production ready voice agents, latency optimization, multi tenancy, MCP proxies - six months of building customer facing voice agents ## A2A Is For UI DevFeed: [A2A Is For UI]() Original publisher: [Read original article]() Published: 2025-06-14T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [Protocol (disambiguation)](), [Multi Agent Systems](), [ui](), [AI Agent](), [HTTP](), [client](), [JSON](), [Remote Procedure Call (RPC)]() Tags: [agent](), [ai](), [ai-agents](), [http](), [json](), [json-rpc](), [multi-agent](), [multi-agent-systems](), [protocol](), [ui]() ### AI overview This commentary argues that Google's A2A protocol can be understood as a user interface for interactions between humans and agents, and as a bridge to more complex multi-agent systems. It describes A2A as an HTTP endpoint with JSON-RPC methods, message parts, task state, and optional webhooks. ### Source excerpt There's a lot of skepticism around A2A, Google's Agent-to-Agent protocol. A lot of that is well earned. I mean, they launched a protocol with zero implementations. But a lot's changed, and it's worth taking a look again.