Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

MCP Node ConnectionString support

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, node.js, sql
Domain
backend, databases

Research direction

Locate the Node MCP connection configuration and its existing Azure-only path, then compare it with the dotnet sample’s connection-string handling. Use the linked SQL-AI issue to verify the READONLY requirement and confirm that both regular connection-string input and restricted tool access work consistently.

Written by the indexing model from the issue text.

Description

dotnet supports a regular connection string, but Node seems to only support Azure connections. I could just use dotnet, but it doesn't appear to support the READONLY to restrict tool access per https://github.com/Azure-Samples/SQL-AI-samples/issues/56 would just be nice for both to have feature parity?

Dominant language
HTML
Stars
331
Forks
208
PR merge metrics
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 Azure-Samples/SQL-AI-samples

All issues in Azure-Samples/SQL-AI-samples

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.