datahub-project / datahub-project/analytics-agent
Migrate the SQLAlchemy Query Engine to an MCP Connector
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 51
- Forks
- 23
- Avg merge
- 14d 12h
- Merged PRs (30d)
- 2
Description
Could we migrate the current SQLAlchemy query engine to an MCP connector?
This would allow the SQLAlchemy connector to be reused independently by MCP clients such as Cursor and Codex, rather than being available only inside Analytics Agent.
For example, I sometimes use Cursor or Codex together with a Hive MCP connector and the DataHub MCP server for data analysis.
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 locating the current SQLAlchemy query engine and the existing Analytics Agent integration. Then investigate how an MCP connector is exposed to clients such as Cursor and Codex. Done means the SQLAlchemy connector can be reused independently by MCP clients rather than only inside Analytics Agent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlalchemy
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100