Change: switch to official mcp go sdk

[ibakshay]

Summary

• Migrates from unofficial MCP library to official modelcontextprotocol/go-sdk
• Refactors CLI architecture to use Cobra with explicit stdio and http subcommands
• Adds file-based logging capability and improves server lifecycle management with proper signal handling

Tested locally and the implementation works as expected.

closes #54

[Nexucis]

adding few suggestions

[Nexucis]

what is the need to have the same binary built in two different name ?

[Nexucis]

you should avoid using the init function, there are really few cases where you actually needed. And I don't see here the requirement to use it.

[Nexucis]

you could actually create a dedicated package for each resources. Doing that will give you the possibility to remove the name of the resource in the function name. That's how Go has been designed, package oriented.

For example if you have package dashboard, then you can expose the following function:

func List(client apiClient.ClientInterface) (*mcp.Tool, mcp.ToolHandlerFor[ListNewDashboardsInput, any]) { }

func GetByName(client apiClient.ClientInterface) (*mcp.Tool, mcp.ToolHandlerFor[GetDashboardByNameInput, any]) {}

func Create(client apiClient.ClientInterface) (*mcp.Tool, mcp.ToolHandlerFor[CreateDashboardInput, any]) {}

This is more elegant and will give clear indication about the goal of each packages.

[Nexucis]

and if you think about what your package should expose, then you could think it should actually only expose a single function providing the list of associated tools.

So instead of calling individually each function, one by one, you can declare a single function per package New providing the list of function.

package tool

type Tool struct {
  MCPTool: *mcp.Tool
  Handler: mcp.ToolHandlerFor[any, any]
  // IsWriteTool tells you if the current tool will need write access
  IsWriteTool: boolean
}

package dashboard

func New(client apiClient.ClientInterface) []*tool.Tool {
  return []*tool.Tool {
    list(client), getByName(client), create(client)
  }
}

[Nexucis]

Then if you use this way to structure your code, the function
registerTools() will simply be:

func (s *Server) registerTools() {
    	var persesTools []*tool.Tools
    	persesTools = append(persesTools, dashboards.New())
    	persesTools = append(persesTools, globaldatasources.New())
    	persesTools = append(persesTools, roles.New())

    	for _, t := range persesTools {
    	    	if s.cfg.ReadOnly && !t.IsWriteTool {
    	    	     	continue
    	    	}
    	    	mcp.AddTool(s.mcpServer, t.MCPTool, t.Handler)
    	}
}

Which I believe is cleaner than the current code

[Nexucis]

I would rename this file as globaldatasources.go as it does not provide the functions managing the Datasources but the GlobalDatasources

[Nexucis]

in that case, you cannot use the function to create a project which is used above (outside of this condition)

[Nexucis]

since the file main.go has been moved to another package, you need to update the file .goreleaser.base.yaml to change the location of this file.

Otherwise the CI will fail building the binary.