stackql / stackql/stackql-devel
[FEATURE] Create MCP package for stackql
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Feature Description
Create a package inside the pkg directory, called mcp_server. This will have zero dependencies on stackql itself and it will contain:
- An interface abstraction for the backend that will run queries arising from client requests to a backend, in the first instance this backend will be
stackql, but we will do the implementation later in core code. This interface should be equally amenable to passing queries in memory or over TCP or other sockets. - Some config structure with json and yaml attribute definnitions to configure
mcp_sefver. - An MCP server, probably using the golang mcp sdk. This should depend on the interface described in (1) and the config described in (2) and expose all conventional MCP transports, configurably.
The goal is for LLMS to consume stackql as a first class information source.
Example(s)
- I don't really want to go into examples at this stage. At the risk of being repetitive, the goal is for LLMs to consume
stackqlas a first class information source.
Possible Approaches or Libraries to Consider
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing pkg directory and the linked Model Context Protocol Go SDK. Define the boundaries for pkg/mcp_server: a transport-independent backend interface, JSON/YAML configuration, and an MCP server exposing the conventional configurable transports without depending on stackql. Done means the package builds with those abstractions and has no dependency on stackql itself.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100