Production MCPを読んで考えたこと
papoo.work
September 24, 2026 at 6:25 AM
Man I love these TUI debuggers 😍
🔌 jsonrpc-debugger — A JSON-RPC debugger for the terminal.
💯 Inspect, modify, and debug JSON-RPC requests and responses in real-time.
🦀 Written in Rust & built with @ratatui.rs
⭐ GitHub: github.com/shanejonas/j...
#rustlang #ratatui #tui #jsonrpc #debugger
🔌 jsonrpc-debugger — A JSON-RPC debugger for the terminal.
💯 Inspect, modify, and debug JSON-RPC requests and responses in real-time.
🦀 Written in Rust & built with @ratatui.rs
⭐ GitHub: github.com/shanejonas/j...
#rustlang #ratatui #tui #jsonrpc #debugger
July 31, 2025 at 1:43 PM
Man I love these TUI debuggers 😍
🔌 jsonrpc-debugger — A JSON-RPC debugger for the terminal.
💯 Inspect, modify, and debug JSON-RPC requests and responses in real-time.
🦀 Written in Rust & built with @ratatui.rs
⭐ GitHub: github.com/shanejonas/j...
#rustlang #ratatui #tui #jsonrpc #debugger
🔌 jsonrpc-debugger — A JSON-RPC debugger for the terminal.
💯 Inspect, modify, and debug JSON-RPC requests and responses in real-time.
🦀 Written in Rust & built with @ratatui.rs
⭐ GitHub: github.com/shanejonas/j...
#rustlang #ratatui #tui #jsonrpc #debugger
Slowly replacing most of my chrome extension by tweety scripts. Ex: Extracting RSS feeds from the @piccalil.li website using a deno script!
![#!/usr/bin/env -S deno run -A
import { DOMParser } from "npm:linkedom"
const { TWEETY_SOCKET } = Deno.env.toObject();
async function tweety(client: Deno.HttpClient, method: string, params: unknown[] = []) {
const resp = await fetch("http://localhost/jsonrpc", {
client,
method: "POST",
body: JSON.stringify({
jsonrpc: "2.0",
id: crypto.randomUUID(),
method,
params,
})
})
if (!resp.ok) {
throw new Error(`Failed to fetch: ${resp.status} ${resp.statusText}`);
}
return resp.json();
}
const client = Deno.createHttpClient({
proxy: {
transport: "unix",
path: TWEETY_SOCKET,
}
})
const { result: tab } = await tweety(client, "tabs.get", []);
const { result: html } = await tweety(client, "tabs.print", [tab.id]);
const doc = new DOMParser().parseFromString(html, "text/html")
const links = doc.querySelectorAll("link[rel='alternate'][type='application/rss+xml'], link[rel='alternate'][type='application/atom+xml']");
if (links.length === 0) {
console.error("No RSS or Atom feed found in the document.");
Deno.exit(1);
}
for (const link of links) {
console.log(new URL(link.getAttribute("href"), tab.url).toString())
}](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:ovreo3dlfroo4ztkep3kjlle/bafkreiesiv3dai253zkb47qe2zvftgh7yzons5p3xtq4a3oqnfcjhqzibu)
June 3, 2025 at 9:21 AM
Slowly replacing most of my chrome extension by tweety scripts. Ex: Extracting RSS feeds from the @piccalil.li website using a deno script!
Are there any transport-agnostic jsonrpc clients in rust where I can feed in an openrpc schema or rust trait and get our a typed client?
January 28, 2026 at 12:50 AM
Are there any transport-agnostic jsonrpc clients in rust where I can feed in an openrpc schema or rust trait and get our a typed client?
JSONRPC is a smart protocol EXCEPT that you must send "jsonrpc": "2.0" in every single request
October 22, 2024 at 2:14 AM
JSONRPC is a smart protocol EXCEPT that you must send "jsonrpc": "2.0" in every single request
I feel this way about the rapid proliferation of MCPs. Friends we had OpenAPI specs for REST APIs, you did not need to make a shitty JSONRPC endpoint that an LLM can mess up calling.
November 23, 2025 at 3:56 AM
I feel this way about the rapid proliferation of MCPs. Friends we had OpenAPI specs for REST APIs, you did not need to make a shitty JSONRPC endpoint that an LLM can mess up calling.
My JSONRPC server in Java now actually allows for remote procedures to be called
April 22, 2025 at 4:54 PM
My JSONRPC server in Java now actually allows for remote procedures to be called
I wanted a jsonrpc library that worked as nicely on workers as capnweb so Claude and I built one: github.com/jmorrell/jso...
GitHub - jmorrell/jsonrpc: Lightweight JSON-RPC 2.0 library for TypeScript
Lightweight JSON-RPC 2.0 library for TypeScript. Contribute to jmorrell/jsonrpc development by creating an account on GitHub.
github.com
February 17, 2026 at 6:03 AM
I wanted a jsonrpc library that worked as nicely on workers as capnweb so Claude and I built one: github.com/jmorrell/jso...
Gotcha..the oauth part is also fully optional for tmcp and even the transports are optional, you could use just the core package that gives you a JSONRpc server and create your own adapter around it to make it work with http
But the JSONRpc part is backed-in, so maybe not what you are looking for 🥲
But the JSONRpc part is backed-in, so maybe not what you are looking for 🥲
July 30, 2026 at 2:02 PM
Gotcha..the oauth part is also fully optional for tmcp and even the transports are optional, you could use just the core package that gives you a JSONRpc server and create your own adapter around it to make it work with http
But the JSONRpc part is backed-in, so maybe not what you are looking for 🥲
But the JSONRpc part is backed-in, so maybe not what you are looking for 🥲
mcp standardizes patterns for advertising tools to llms for use & for the llms to call into those tools. (or, put another way, it’s a specific application interface on top of jsonrpc encoding)
February 28, 2025 at 4:28 AM
mcp standardizes patterns for advertising tools to llms for use & for the llms to call into those tools. (or, put another way, it’s a specific application interface on top of jsonrpc encoding)
TIL: You can easily test your MCP servers using stdio transport by piping a JSON-RPC call directly into the server.
e.g. piping {"jsonrpc":"2.0","method":"tools/list","id":1} will list the available tools that can be passed to the LLMs.
e.g. piping {"jsonrpc":"2.0","method":"tools/list","id":1} will list the available tools that can be passed to the LLMs.
March 25, 2025 at 2:15 PM
TIL: You can easily test your MCP servers using stdio transport by piping a JSON-RPC call directly into the server.
e.g. piping {"jsonrpc":"2.0","method":"tools/list","id":1} will list the available tools that can be passed to the LLMs.
e.g. piping {"jsonrpc":"2.0","method":"tools/list","id":1} will list the available tools that can be passed to the LLMs.
It‘s what I‘m thinking for the jsonrpc lib I‘m working on, ahaha. I‘d love to just have a jsonrpc macro that creates an endpoint out of any function. Then generate a trait for it to call that over a client.
September 19, 2024 at 9:21 PM
It‘s what I‘m thinking for the jsonrpc lib I‘m working on, ahaha. I‘d love to just have a jsonrpc macro that creates an endpoint out of any function. Then generate a trait for it to call that over a client.
#Drupal module release: jsonrpc 3.0.0-beta1 (2025-07-21) #PHP. See https://www.drupal.org/project/jsonrpc/releases/3.0.0-beta1
July 21, 2025 at 11:00 AM
#Drupal module release: jsonrpc 3.0.0-beta1 (2025-07-21) #PHP. See https://www.drupal.org/project/jsonrpc/releases/3.0.0-beta1
restful nadinha jsonrpc rainha
December 1, 2025 at 7:18 PM
restful nadinha jsonrpc rainha
i wonder what would happen to one of these scanners if we wrote
{"jsonrpc":"2.0","id":$THEIR_ID,"error":{"code":-666,"data":
and then an infinite stream of alternating `{` and `[` characters
{"jsonrpc":"2.0","id":$THEIR_ID,"error":{"code":-666,"data":
and then an infinite stream of alternating `{` and `[` characters
April 19, 2026 at 12:13 AM
i wonder what would happen to one of these scanners if we wrote
{"jsonrpc":"2.0","id":$THEIR_ID,"error":{"code":-666,"data":
and then an infinite stream of alternating `{` and `[` characters
{"jsonrpc":"2.0","id":$THEIR_ID,"error":{"code":-666,"data":
and then an infinite stream of alternating `{` and `[` characters
jsonrpc is annoying, like being swarmed by gnats
April 18, 2026 at 11:53 PM
jsonrpc is annoying, like being swarmed by gnats
![let mimic = function
| `Assoc
[
("jsonrpc", `String "2.0");
("method", `String "subtract");
("params", `List [ `Int a; `Int b ]);
("id", `Int id);
] ->
`Assoc
[
("jsonrpc", `String "2.0"); ("result", `Int (a - b)); ("id", `Int id);
]
| `Assoc
[
("jsonrpc", `String "2.0");
("method", `String "sum");
("params", `List xs);
("id", `Int id);
] ->
let sum =
List.fold_left
(fun acc x ->
match x with `Int n -> acc + n | _ -> failwith "Only ints allowed")
0 xs
in
`Assoc
[ ("jsonrpc", `String "2.0"); ("result", `Int sum); ("id", `Int id) ]
| _ -> failwith "Unexpected input"](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:qcjmkxk5v4o33pd4z7na6wmw/bafkreienwj3vztohywkddgux4tkmroenoco6lw6it7fvwnhx37j77kyb7e)
Thanks, I know you lib, ahaha. Watched your talk about it recently. That’s what got me into thinking how I‘d implement something similar for jsonrpc :)
September 19, 2024 at 9:22 PM
Thanks, I know you lib, ahaha. Watched your talk about it recently. That’s what got me into thinking how I‘d implement something similar for jsonrpc :)
Most HTTP JSON APIs (RESTful APIs) would be better using jsonrpc over HTTP
March 27, 2025 at 12:52 AM
Most HTTP JSON APIs (RESTful APIs) would be better using jsonrpc over HTTP
📦 yoanm/jsonrpc-params-symfony-validator-sdk v2.1.1
Simple JSON-RPC params validator that use Symfony validator component
🔗 https://github.com/yoanm/php-jsonrpc-params-symfony-validator-sdk
Simple JSON-RPC params validator that use Symfony validator component
🔗 https://github.com/yoanm/php-jsonrpc-params-symfony-validator-sdk
September 2, 2025 at 10:58 PM
📦 yoanm/jsonrpc-params-symfony-validator-sdk v2.1.1
Simple JSON-RPC params validator that use Symfony validator component
🔗 https://github.com/yoanm/php-jsonrpc-params-symfony-validator-sdk
Simple JSON-RPC params validator that use Symfony validator component
🔗 https://github.com/yoanm/php-jsonrpc-params-symfony-validator-sdk
Parla is no longer depending on DeltachatDesktop to work, it's now able to create, transfer profiles and relays by itself. Looking forward distros to help me draw the best way to ship a separate jsonrpc server, maybe even sandboxed separately from the UI app […]
[Original post on infosec.exchange]
[Original post on infosec.exchange]
April 30, 2026 at 12:22 PM
Parla is no longer depending on DeltachatDesktop to work, it's now able to create, transfer profiles and relays by itself. Looking forward distros to help me draw the best way to ship a separate jsonrpc server, maybe even sandboxed separately from the UI app […]
[Original post on infosec.exchange]
[Original post on infosec.exchange]
Ripped connectrpc out of my side project in favor of simple jsonrpc + shared typescript definition between server and client github.com/fgnass/typed...
connectrpc was solid, but too heavy for my needs. "Typescript as service schema" works surprisingly well!
connectrpc was solid, but too heavy for my needs. "Typescript as service schema" works surprisingly well!
GitHub - fgnass/typed-rpc: Lightweight JSON-RPC solution for TypeScript projects
Lightweight JSON-RPC solution for TypeScript projects - fgnass/typed-rpc
github.com
September 30, 2025 at 12:02 AM
Ripped connectrpc out of my side project in favor of simple jsonrpc + shared typescript definition between server and client github.com/fgnass/typed...
connectrpc was solid, but too heavy for my needs. "Typescript as service schema" works surprisingly well!
connectrpc was solid, but too heavy for my needs. "Typescript as service schema" works surprisingly well!
Ok #TrustedDocuments is effectively #jsonrpc but in #GraphQL. 😄 Though, because you know of the query for the client, you can have the query planner in graphql optimized for those type. Helping considerably in speed, but also execution and security.
Little to say, I like it. 😅
Little to say, I like it. 😅
January 15, 2025 at 4:50 PM
Ok #TrustedDocuments is effectively #jsonrpc but in #GraphQL. 😄 Though, because you know of the query for the client, you can have the query planner in graphql optimized for those type. Helping considerably in speed, but also execution and security.
Little to say, I like it. 😅
Little to say, I like it. 😅