SubscriberAPI MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SubscriberAPI MCP ServerCheck the health of the SubscriberAPI log endpoint"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SubscriberAPI MCP Server
An MCP (Model Context Protocol) server that lets GitHub Copilot CLI query SFMC SubscriberAPI execution logs — health checks, email lookups, execution traces, and recent errors.
Who is this for?
SFMC developers and engineers who want to troubleshoot SubscriberViaAPI issues from the terminal using natural language, for example:
"Is the SubscriberAPI log endpoint healthy?"
"Find recent errors for source
MyForm.""Get the execution trace for FormRequestID
abc-123."
Related MCP server: GitHub Copilot CLI MCP Server
Prerequisites
Node.js 18 or later
SFMC log API endpoint URL and API key (from your team's CloudPage / API setup)
Quick start
1. Clone the repo
git clone https://github.com/YOUR-ORG/subscriberapi-mcp.git
cd subscriberapi-mcpTip: Clone to a folder without spaces in the path (e.g.
C:\dev\subscriberapi-mcp) to avoid Windows path issues.
2. Install and build
npm run setup3. Add your credentials
cp .env.example .envEdit .env and set:
SFMC_LOG_ENDPOINT— your SFMC execution log API URLSFMC_LOG_API_KEY— your API key
Never commit .env. It is already in .gitignore.
4. Use with GitHub Copilot CLI
This repo includes a project-level MCP config (.mcp.json) with a relative path — no machine-specific paths required.
From the cloned repo folder, start Copilot:
copilotCopilot auto-loads .mcp.json when you work in this project. You should see subscriberapi with a green checkmark under MCP Servers.
5. Test it
Inside Copilot:
Use subscriberapi health_check and tell me the result.Or from the shell (one-shot):
copilot -p "Call subscriberapi health_check" --allow-all-toolsMCP tools
Tool | Description |
| Check if the SFMC log endpoint is available |
| Find executions by email (optional source, date range, limit) |
| Get full trace for a |
| List recent errors (optional filters) |
How configuration works
File | Purpose |
| Shared Copilot MCP config (relative |
| Private API credentials (each developer creates their own) |
| Optional global Copilot MCP config (user-specific) |
Recommended: Rely on .mcp.json in the repo. Each developer only needs their own .env.
If you previously added subscriberapi to your global ~/.copilot/mcp-config.json with an absolute path, remove it to avoid duplicates:
copilot mcp remove subscriberapiOptional: global install (any folder)
If you want subscriberapi available outside this repo, register it once from the cloned folder:
Windows (PowerShell):
.\scripts\register-copilot-mcp.ps1macOS / Linux:
./scripts/register-copilot-mcp.shThese scripts read credentials from your .env and register an absolute path on your machine only.
Development
npm run dev # run TypeScript directly (tsx)
npm run build # compile to dist/
npm start # run compiled serverTroubleshooting
Issue | Fix |
Red X on | Run |
| Create |
Path split at space (Windows) | Clone to a path without spaces, or use the register script |
Permission denied in | Add |
Duplicate | Run |
License
ISC
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/soumyaranjansingh-economist/subscriberapi-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server