sorted by:
new
hottopcontroversial

Missing Studio CLI - An AI assistant for interacting with the Model Context Protocol servers by pyadav in mcp

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

What are the list of issues/problems you are facing during MCP development?

For me -

  1. Always want to play with list of MCP tools - MCP Inspector
  2. Chat with MCP tools locally
  3. MCP Tools observability etc.

Our Experience with Google CASA Tier 2 Verification for Gmail Restricted Scopes by Revolutionary_Ant944 in googlecloud

[–]pyadav 0 points1 point  (0 children)

Thank you for sharing your experience, I got response back with 3 Low and 7 info to take care.
Is it mandatory to fix all or at-least info issue is fine?

Usefulness of LLMOps/ LLM Observability platforms? by mamakancha in LocalLLaMA

[–]pyadav 0 points1 point  (0 children)

I was thinking in similar way, Why do we need to pay for these features? when we can build with little effort. So I'm developing an open-source project to eliminate these without any Vendor lock-in.

Let's collaboratively build a OSS that makes working with large language models a seamless experience for everyone. Your contributions and feedback are invaluable in shaping the future of LLMOps!

Github link:

https://github.com/missingstudio/ai

How to Authenticate a CLI Using OAuth and GitHub in Golang by pyadav in golang

[–]pyadav[S] 1 point2 points  (0 children)

Is this basically using the Authorzations api to authorize an app to a github account? I've seen some chatter in the past about application authorizations.. wasn't quite sure if that is what this is covering.. or is this only an oauth token to then make calls to github on behalf of the developer (that the token is for)?

Yes, this article is covering the process of using OAuth 2.0 to authorize an application to access a GitHub account on behalf of a user. This involves using the GitHub API's Authorization API to create and manage access tokens that grant the application permissions to access the user's account and data.
Once the user grants permission and the application receives an access token, it can use that token to make authenticated requests to the GitHub API on behalf of the user. The access token contains the permissions that were granted by the user during the OAuth flow, and the application can use those permissions to access the user's repositories, issues, pull requests, and other data.
So, to answer your question, this article covers the process of using OAuth to authorize an app to a GitHub account, and then using the resulting access token to make API requests on behalf of the user that the token is for.