Open Issues Need Help
View All on GitHubAI Summary: Test the integration of the ebpf-mcp server with the VSCode MCP extension. Document any errors encountered during testing and, if successful, create a tutorial for using ebpf-mcp with VSCode and add it to the project's documentation.
AI Summary: Test the `ebpf-mcp` server using the MCP Inspector tool to ensure compatibility with the Model Context Protocol. This involves running the inspector against the server and identifying any critical errors reported. These errors will then need to be addressed in the `ebpf-mcp` codebase.
AI Summary: Implement a robust authentication and authorization system for the ebpf-mcp project, replacing the current single-token approach with JWT-based authentication, RBAC, resource quotas, rate limiting, and comprehensive audit logging. This involves several phases: JWT implementation, RBAC integration, resource control mechanisms, and audit logging, requiring thorough testing and documentation updates.
AI Summary: Implement a `--port` or `-p` command-line flag for the `ebpf-mcp-server` to allow users to specify a custom port, while maintaining backward compatibility with older versions that don't support this flag. The default port should remain 8080 if the flag is not provided.
AI Summary: Test the `ebpf-mcp` server's stdio support with the Claude-CLI, create a tutorial documenting both HTTP and stdio usage (including remote server scenarios), and add tests for the stdio functionality.
AI Summary: Implement MCP Resource support in the ebpf-mcp project, focusing on providing information like the project's README or a dynamically generated schema, to allow clients to interact with the system's resources via the MCP protocol. This involves designing a modular system for managing resources and deciding which resources to expose.
AI Summary: Implement MCP Resource support in the ebpf-mcp project. This involves extending the existing MCP server to handle the Resources section of the MCP protocol, likely by adding a mechanism to expose project resources (potentially the README.md or a dynamically generated schema) to clients. Consideration should be given to modular design and efficient resource management.