SG Wireless SDK · MCP server
Ask your own AI agent about the SG Wireless SDK
This is the SG Wireless SDK MCP server. Add it to your agent, sign in with GitHub once, and ask about boards, APIs, examples, Arduino and the build tools.
- Serves sg-sdk v1.5.0
- commit 49c3dead, 2026-09-04
- ESP-IDF v5.5.4
- MicroPython v1.29.0
- arduino-esp32 3.3.11
Server address
https://mcp.sgwireless.com/mcpAdd it to your agent
Claude Code
Add it from a terminal:
claude mcp add --transport http sg-sdk https://mcp.sgwireless.com/mcp- Add
--scope userto have it in every project, not only the current one. - Run
/mcpin Claude Code, selectsg-sdkand choose Authenticate. - Sign in with your GitHub account; any account works. The SG Wireless SDK consent page appears first: approve it, then GitHub asks you to authorize read-only access to your profile (
read:user). - Try:
- “Which SG boards support LoRa in the Arduino package?”
- “Show me the SGW_LoRaWAN example and explain the join flow.”
- “How do I build MicroPython firmware for the SGW3501 StarterKit?”
claude.ai / Desktop
In claude.ai or Claude Desktop, open Customize → Connectors, choose Add custom connector, name it SG Wireless SDK and paste the address (or open the prefilled dialog):
https://mcp.sgwireless.com/mcp- If the dialog asks, keep Sign in now under Authentication (Claude usually detects it) and Use Claude’s published identity under OAuth client. It needs no OAuth client ID or secret: leave them empty if the dialog shows them. Do not choose No sign-in: Claude cannot change that later, and the connector would have to be removed and added again.
- Choose Connect. On a Team or Enterprise plan an Owner adds the connector under Organization settings → Connectors, and each member then chooses Connect.
- The sign-in opens in a new browser window: allow pop-ups for claude.ai if your browser blocks it.
- Sign in with your GitHub account; any account works. The SG Wireless SDK consent page appears first: approve it, then GitHub asks you to authorize read-only access to your profile (
read:user). - Try:
- “Which SG boards support LoRa in the Arduino package?”
- “Show me the SGW_LoRaWAN example and explain the join flow.”
- “How do I build MicroPython firmware for the SGW3501 StarterKit?”
Cursor
Add it to ~/.cursor/mcp.json (or the project’s .cursor/mcp.json):
{
"mcpServers": {
"sg-sdk": {
"url": "https://mcp.sgwireless.com/mcp"
}
}
}- Open Customize in Cursor’s sidebar, check that
sg-sdkis enabled and sign in when Cursor asks; the sign-in opens in your browser. - Sign in with your GitHub account; any account works. The SG Wireless SDK consent page appears first: approve it, then GitHub asks you to authorize read-only access to your profile (
read:user). - Try:
- “Which SG boards support LoRa in the Arduino package?”
- “Show me the SGW_LoRaWAN example and explain the join flow.”
- “How do I build MicroPython firmware for the SGW3501 StarterKit?”
VS Code
Run MCP: Add Server, choose HTTP (HTTP or Server-Sent Events), paste the address, name it sg-sdk, then choose Global → Copilot Global to have it in every workspace. To configure it by hand, add this to the workspace’s .vscode/mcp.json:
{
"servers": {
"sg-sdk": {
"type": "http",
"url": "https://mcp.sgwireless.com/mcp"
}
}
}- If VS Code does not start the server on its own, start it from MCP: List Servers.
- Allow the sign-in when VS Code asks; a browser window opens for the GitHub authorization on the first connection.
- Sign in with your GitHub account; any account works. The SG Wireless SDK consent page appears first: approve it, then GitHub asks you to authorize read-only access to your profile (
read:user). - Try:
- “Which SG boards support LoRa in the Arduino package?”
- “Show me the SGW_LoRaWAN example and explain the join flow.”
- “How do I build MicroPython firmware for the SGW3501 StarterKit?”
Codex
Add it to ~/.codex/config.toml:
[mcp_servers.sg-sdk]
url = "https://mcp.sgwireless.com/mcp"- Run
codex mcp login sg-sdk. - Sign in with your GitHub account; any account works. The SG Wireless SDK consent page appears first: approve it, then GitHub asks you to authorize read-only access to your profile (
read:user). - Try:
- “Which SG boards support LoRa in the Arduino package?”
- “Show me the SGW_LoRaWAN example and explain the join flow.”
- “How do I build MicroPython firmware for the SGW3501 StarterKit?”
Gemini CLI
Add it to ~/.gemini/settings.json:
{
"mcpServers": {
"sg-sdk": {
"httpUrl": "https://mcp.sgwireless.com/mcp"
}
}
}- Run
/mcp auth sg-sdkin Gemini CLI. - Sign in with your GitHub account; any account works. The SG Wireless SDK consent page appears first: approve it, then GitHub asks you to authorize read-only access to your profile (
read:user). - Try:
- “Which SG boards support LoRa in the Arduino package?”
- “Show me the SGW_LoRaWAN example and explain the join flow.”
- “How do I build MicroPython firmware for the SGW3501 StarterKit?”
On the free tier and with Google One, Gemini CLI has been replaced by Antigravity CLI, which uses a different configuration file: see Antigravity’s MCP guide.
opencode
Add it to ~/.config/opencode/opencode.json (or the project’s opencode.json):
{
"mcp": {
"sg-sdk": {
"type": "remote",
"url": "https://mcp.sgwireless.com/mcp"
}
}
}- Run
opencode mcp auth sg-sdk. - Sign in with your GitHub account; any account works. The SG Wireless SDK consent page appears first: approve it, then GitHub asks you to authorize read-only access to your profile (
read:user). - Try:
- “Which SG boards support LoRa in the Arduino package?”
- “Show me the SGW_LoRaWAN example and explain the join flow.”
- “How do I build MicroPython firmware for the SGW3501 StarterKit?”
What it can answer
Your agent picks from 10 read-only tools, each answering from the served SDK release:
- SDK revision and overview
sdk_info - Search the SDK
search_sdk - Read an SDK file
read_sdk_file - List SDK examples
list_examples - Get an example's source
get_example - Board features and pins
get_board - Look up an API symbol
lookup_api - fw_builder.sh reference
builder_reference - Port MicroPython code to native C
port_to_native_guide - Arduino guide for SG Wireless boards
arduino_guide
Privacy
The server is read-only. It sees the arguments of the tool calls your agent makes, never your conversation or your files. Sign-in asks GitHub for read-only access to your profile (read:user), never for your repositories.
Each request is logged with the tool name, your numeric GitHub id and login and your MCP client’s id, but not the tool arguments. The access log records the IP address your requests come from (for Claude’s hosted connectors on claude.ai, Desktop and mobile that is Anthropic’s), the method, path and status.
Your agent gets a token for 30 days and renews it on its own, so you sign in again only after about six months without using the server (GitHub’s limit for an unused sign-in). Sign-in data is stored encrypted. Revoking the app’s access on GitHub ends it within 5 minutes while GitHub answers; while GitHub cannot be reached, a sign-in GitHub confirmed in the last 6 hours keeps working.
Help
Questions about the SDK, the boards or this server: ask in the SG Wireless Community Forum.