Actual Utility Prompt > Review my functions and tell me if we have set an email template via a variable, and if we have it set, call Postmark to verify the template ID is valid.
MCP Super Tools
My Go-To MCP Workbench
I can pull a lot of tools into the chat. A select set stays wired — power tools, not a junk drawer. The rest come and go.
The workbench patterns underneath are what matter. They protect my clients. They keep each setup project-specific. And they let me stay in the AI tooling — see across issues and features — instead of hopping out to five dashboards to reconstruct what just broke.
Behind the gate
The Always-on bench, and how I keep it clean
Subscribe to see which servers stay on, the Cursor JSON I actually run, and how Infisical feeds vars on the fly — so secrets never live in a file the model can trip over, and one client’s keys never bleed into another’s project.
Always on
-
-
Actual Utility Prompt > Call Fly and check the logs to see why the API had two restarts last night, then cross-check which users were impacted in Sentry. If the issues were critical and you can tell from the feature use, help me craft a message to email each of them.
-
Open →Sentry
MCP OfficialWhy: So I can go from a Slack alert to root cause without leaving the chat — Seer, then Cloudflare logs, GitHub history, or Inngest crons.
Actual Utility Prompt > Review the Sentry milestones and tell me which API routes got the most traffic from the React front end.
-
Open →GitHub
MCP OfficialWhy: So I can research front to back from any chat — phone, Cursor, Codex — read the code, spot an issue, open a PR, or do the background research.
Actual Utility Prompt > Check the GitHub repo and tell me how many Sentry Seer issues resulted in GitHub PRs, then cross-reference with PostHog for the accounts that have used the feature changes the most.
-
Actual Utility Prompt > Call Postmark and update the logo we use in the header, and the link to terms and conditions for the new marketing site.
-
Actual Utility Prompt > Call PostHog and tell me the pages this week's users viewed before signup. If we have recordings, tell me about any content hotspots that showed their engagement interest. I want to group these users and adjust the marketing content to test them as a possible marketing segment.
From the LCCTO bench
The Cursor mcp.json for this Always-on list only. Project refs are redacted. Infisical is the loader, not a server in this file.
{
"mcpServers": {
"supabase": {
"type": "stdio",
"command": "bash",
"args": [
".cursor/mcp-with-env.sh",
"npx",
"-y",
"@supabase/mcp-server-supabase@latest",
"--project-ref",
"<project-ref>"
]
},
"fly": {
"type": "stdio",
"command": "bash",
"args": [".cursor/mcp-with-env.sh"]
},
"sentry": {
"type": "stdio",
"command": "bash",
"args": [".cursor/sentry-mcp.sh", "<project>"]
},
"github": {
"type": "stdio",
"command": "bash",
"args": [".cursor/github-mcp.sh"]
},
"postmark": {
"type": "stdio",
"command": "bash",
"args": [
".cursor/mcp-with-env.sh",
"node",
"tools/postmark-mcp/index.js"
]
},
"posthog": {
"type": "stdio",
"command": "bash",
"args": [".cursor/mcp-with-env.sh"]
}
}
}Vars and secrets
Vars and secrets are an issue. Cursor does not honor a .env file for MCP. I used a loader file — .cursor/mcp-with-env.sh — so each server starts through Infisical and pulls vars on the fly. Credentials never sit in the JSON, and they do not depend on Cursor reading a local env file.
Infisical
MCP OfficialWhy: So I can keep secrets in a secure layer — use them locally and on the server without ever dropping them in code. I work across clients; I cannot leak or forget a secret.
Actual Utility Prompt > Call Infisical and determine when we last rotated the Supabase Auth token. Recommend which keys we need to change because we have had them for too long.