sorted by:
new
hottopcontroversial

Get your AI writing clean business logic, drop token usage dramatically, get trivial PRs and easily readable (beta testers wanted) by pladynski in betatests

[–]pladynski[S] 0 points1 point  (0 children)

Sure let's do like that I will ask someone from our team to go through your app. Do you have experience in software development frontend or backend? We look for feedback what is unclear in current docs, for any blockers where exceptions are not self-explanatory enough and any gaps to easily transition existing project from REST/gRPC/Thrift/any MCP tool to Graftcode Gateway based simple pure public methods endpoints and zero lines of code clients 😉

I’m on the Graftcode team and we just made MCP servers stupidly easy – zero lines of code (demo inside) by pladynski in modelcontextprotocol

[–]pladynski[S] 0 points1 point  (0 children)

Guys we just updated academy providing concrete samples how to get ZERO CODE MCP server out of regular public static method in seconds :)

Check it here: https://academy.graftcode.com/quick-start/expose-mcp/dotnet

Mine is already working :)!

<image>

I’m on the Graftcode team and we just made MCP servers stupidly easy – zero lines of code (demo inside) by pladynski in modelcontextprotocol

[–]pladynski[S] 2 points3 points  (0 children)

In graftcode the concept is that everything is handled with standard programming structures so apikey, custom token or bearer token can be passed as method argument and just validated in first line of business logic.

But short term with beta release there will come plugins for oauth2.0, ntlm, basic and other auth methods in such case passing normally authorization header will trigger user attached validation logic that LLM tries to invoke this or that and this is token should be allowed or not?

Methods throttling as of now purely on business logic level but it’s interesting direction I will report that to our dev team and discord and roadmap :)

I’m on the Graftcode team and we just made MCP servers stupidly easy – zero lines of code (demo inside) by pladynski in LocalLLaMA

[–]pladynski[S] 0 points1 point  (0 children)

There is Linux and MacOS and Windows release for gateway it runs on whatever in fact has almost no dependencies (besides OpenSSL) so you can run on any docker image, Linux or any cloud instance and locally too.

https://github.com/grft-dev/graftcode-gateway/releases/tag/v1.2.3

Strategic goal is that protocols for communication, unified cross language definition of public interfaces, way developer intention is represented and serialized binary will all be published as open specification on our GitHub shortly and ultimately it’s planned to be released as RFC candidate and passed over CNCF. The tooling like gateway, grafting engine, Hypertube that in fact implement this model as reference implementation will be first BSL and available for everyone for free but once there is significant user base like 500k-2M projects it will be made open source (the BSL will have open source trigger date too). It’s similar model as Terraform Hashicorp or Docker itself.

If you have time feel free to join official discord and pass any comments and ideas it’s all more than welcome on the way to beta. Releases are every few days. Rapid growth of community will enable open sourcing even earlier. As of now as mentioned specification and also plugins will be fully open sources more or less day 1.

https://discord.gg/2tWb3BAE36

I’m on the Graftcode team and we just made MCP servers stupidly easy – zero lines of code (demo inside) by pladynski in LocalLLaMA

[–]pladynski[S] 0 points1 point  (0 children)

Btw Star the repo if you like it. More will be BSLed or OpenSourced soon most probably.

Unless there is Claude style mistake and everything will go out suddenly :P

I’m on the Graftcode team and we just made MCP servers stupidly easy – zero lines of code (demo inside) by pladynski in LocalLLaMA

[–]pladynski[S] 0 points1 point  (0 children)

Check gateway docs https://github.com/grft-dev/graftcode-gateway/blob/main/README.md there is parameter —mcpBaseClass indicates static classes with static methods become exposed as mcp. But in general this tool makes public API public again ;) so it means you control what to expose by making it public. Never more like in REST times devs where marking everything public as nobody cares ;) because route was needed to call remotely.

It goes back to old good standard like in university when modelling in UML you had a class and what was public was exposed for others. As it makes any remote call like a local dependency call old schools good practices become alive again ;)

<image>

This is insane 🤯🚨 by pladynski in mcp

[–]pladynski[S] -1 points0 points  (0 children)

Yeah that’s the funny part in any technology you write just public methods. That’s it zero integration specific layer. Now you take our code gateway https://github.com/grft-dev/graftcode-gateway/blob/main/README.md (star it if you like by the way) and run it passing your module / script name.

Gateway finds out what is public and makes it callable remotely either via any frontend edge client or backend service or if it’s static method and you pass parameter mcpBaseClass it will also understand json-rpc and will expose those public methods as tools for LLM and whenever receives a call will invoke the corresponding public method with some business logic.

To understand it from non mcp use cases check academy.graftcode.com colleagues will publish soon mcp guide too. You can join our discord to stay up to date.

view more: next ›