[FEATURE] Create MCP package for stackql

Open
#110 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
api, backend

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.

Description

enhancement

Feature Description

Create a package inside the pkg directory, called mcp_server. This will have zero dependencies on stackql itself and it will contain:

  1. 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.
  2. Some config structure with json and yaml attribute definnitions to configure mcp_sefver.
  3. 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 stackql as a first class information source.

Possible Approaches or Libraries to Consider

Additional context

Dominant language
Go
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackql/stackql-devel

All issues in stackql/stackql-devel

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.