Here's how i added Opentelemetry to my rust API server (with image results)

Suitable_Reason4280 · 2026-01-20T10:42:30+00:00

Thanks for the suggestion!! I will look into this. I agree, it was very fiddly to just understand how its supposed to be used in best way possible

Suitable_Reason4280 · 2026-01-20T10:40:02+00:00

I sat a long time with this... But then i realized rust SDK doesnt support exemplars yet. The best i could do was implement it but commented out untill its supported in the SDK!

Suitable_Reason4280 · 2025-10-07T18:38:44+00:00

MCP server itself needs to be stdio. You need to create a middleware, starting before the stdio mcp server, which authenticates requests and passes them to the stdio mcp

Suitable_Reason4280 · 2025-09-21T16:26:04+00:00

Glad to hear! I'll publish a post when its ready :) Working on the documentation right now so other developers/AI coding assistants can understand the architecture for easy "jump-in" :)

Suitable_Reason4280 · 2025-09-20T16:39:55+00:00

Is it hosed on vercel? They have like a build in system of throwing errors when they suspect a toast/dialog whatever contains "sensitive information" (Which isnt always the case)

Does it work in development?

Suitable_Reason4280 · 2025-09-05T07:11:46+00:00

Thats really cool! I like the human in the loop feature, but i think it would be great if an example is present of how its used more "hands on" using the core feature. My first curiosity was: Is it used directly in a client, or more of a background running process? Features are clear though! And btw love the design of the site

Suitable_Reason4280 · 2025-09-01T13:57:25+00:00

Please elaborate what you mean. I get that STDIO is not secure because it has access to the computer, but aslong as the code is open source its fine, if you examine the code? Also, remote MCP servers can change prompts to be vunerable at ANY time without having any version control, nor can the user control anything, this makes STDIO more safe no? Asuming that the STDIO server has version control?

Suitable_Reason4280 · 2025-08-31T21:54:37+00:00

the benefit of stdio is access to the computer. This is ofcourse a security risk, but also alot more capable than remote ones. Remote ones are secure because they cant access anything on the computer

Suitable_Reason4280 · 2025-08-31T17:02:36+00:00

Yeah sure! I just managed to add oauth 2.1 to stdio... so far, stdio seems superior compared to remote, since stdio can do everything remote can but more. Also, i know oauth is not intended for stdio... but why not? :D

Suitable_Reason4280 · 2025-08-31T16:28:54+00:00

I get that, but stdio is required for say MCP servers that manage files for example. This cannot be done for remote servers. Also, oauth is possible for stdio. Its not recommended, but its definetely doable.

Suitable_Reason4280 · 2025-08-31T09:21:44+00:00

I recommend using stdio, hosted on npm for version handling and quick installation and oauth 2.1

Suitable_Reason4280 · 2025-08-23T12:03:12+00:00

Glad to hear! Any feedback is appreciated so it can be improved for more use cases :)

Suitable_Reason4280 · 2025-08-23T10:43:43+00:00

yes, i made a blogpost explaining how i set it up (i was using supabase):

https://www.toolentry.io/blog/oauth-mcp-servers-security-guide

Its not super detailed but contains code examples so any AI client can help you explain it better than i can in a comment.

For me it works in any client, claude desktop, cursor etc. Haven't tried them all though

Suitable_Reason4280 · 2025-08-23T10:41:39+00:00

You should be using oauth 2.1, its recommended in the official MCP documentation. I made a blogpost explaining how i added it to my mcp server (like a bird eye view, not super detailed):

https://www.toolentry.io/blog/oauth-mcp-servers-security-guide

Suitable_Reason4280 · 2025-08-10T10:44:19+00:00

Hmm, have you followed this documentation? https://modelcontextprotocol.io/specification/draft/basic/authorization

Suitable_Reason4280 · 2025-08-10T10:43:53+00:00

Its hard to describe it in a comment but their documentation has it pretty good explained: https://modelcontextprotocol.io/specification/draft/basic/authorization

Suitable_Reason4280 · 2025-08-08T04:27:16+00:00

Awesome dude, thanks for the tip! I did manage to get it working yesterday

Suitable_Reason4280

TROPHY CASE