Connect a client
Every client needs the same three things: the command (npx), its arguments (-y @smsfabric/mcp-server) and the SMSFABRIC_API_KEY environment variable. Only the file and its format differ. The examples use a test key; replace it with yours.
Claude Desktop
Section titled “Claude Desktop”-
In Claude Desktop, open Settings → Developer and click Edit Config. This opens
claude_desktop_config.json:- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
-
Add the server under
mcpServers:claude_desktop_config.json {"mcpServers": {"smsfabric": {"command": "npx","args": ["-y", "@smsfabric/mcp-server"],"env": {"SMSFABRIC_API_KEY": "sf_test_xxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"}}}} -
Quit Claude Desktop completely and open it again. The SMSFabric tools appear under the tools icon in the message box.
Claude asks before each tool call. Choose Allow once for anything that sends.
Claude Code
Section titled “Claude Code”Add the server with one command:
claude mcp add smsfabric -e SMSFABRIC_API_KEY=sf_test_xxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx -- npx -y @smsfabric/mcp-serverEverything after -- is the command Claude Code runs. By default the server is added for you in the current project only (--scope local); use --scope user to have it in every project. Check it with claude mcp list, or type /mcp in a session to see its status and tools.
To share the setup with your team without sharing a key, add it with --scope project. Claude Code writes .mcp.json at the project root; change the key to a reference to each person’s own environment variable:
{ "mcpServers": { "smsfabric": { "command": "npx", "args": ["-y", "@smsfabric/mcp-server"], "env": { "SMSFABRIC_API_KEY": "${SMSFABRIC_API_KEY}" } } }}Cursor
Section titled “Cursor”Create .cursor/mcp.json in your project, or ~/.cursor/mcp.json to have the server in every project:
{ "mcpServers": { "smsfabric": { "command": "npx", "args": ["-y", "@smsfabric/mcp-server"], "env": { "SMSFABRIC_API_KEY": "sf_test_xxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" } } }}Open Cursor’s settings, find the MCP section and check that smsfabric is enabled and lists its tools. The tools are available to the agent in chat.
VS Code
Section titled “VS Code”VS Code (with GitHub Copilot in agent mode) reads .vscode/mcp.json. Its top-level key is servers, not mcpServers. Use an input so VS Code asks for the key once and stores it securely, instead of writing it in the file:
{ "inputs": [ { "type": "promptString", "id": "smsfabric-api-key", "description": "SMSFabric API key (sf_test_… or sf_live_…)", "password": true } ], "servers": { "smsfabric": { "type": "stdio", "command": "npx", "args": ["-y", "@smsfabric/mcp-server"], "env": { "SMSFABRIC_API_KEY": "${input:smsfabric-api-key}" } } }}Click Start above the server entry in the file, enter the key when asked, then pick the tools in the chat’s agent mode tool list.
Windsurf
Section titled “Windsurf”Open Windsurf’s MCP settings and edit the raw config, or open ~/.codeium/windsurf/mcp_config.json directly:
{ "mcpServers": { "smsfabric": { "command": "npx", "args": ["-y", "@smsfabric/mcp-server"], "env": { "SMSFABRIC_API_KEY": "sf_test_xxxxxxxxxxxx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" } } }}Refresh the server list in Windsurf’s MCP settings so it starts the server.
Any stdio client
Section titled “Any stdio client”Any client that speaks MCP over stdio can run the server. Give it:
| Setting | Value |
|---|---|
| Transport | stdio |
| Command | npx (or smsfabric-mcp after a global install) |
| Arguments | -y, @smsfabric/mcp-server (none for smsfabric-mcp) |
| Environment | SMSFABRIC_API_KEY, and SMSFABRIC_BASE_URL if you don’t use the default API |
The server writes protocol messages to stdout and its own diagnostics to stderr. It doesn’t support HTTP or SSE transports.