gotempsh/temps-mcp-setup
skills/temps-mcp-setup/SKILL.md
Configure the Temps MCP server to enable AI assistants to interact with the Temps platform. Provides tools for listing projects, viewing project details, and managing deployments directly from Claude or other MCP-compatible clients. Use when the user wants to: (1) Set up Temps MCP server, (2) Configure Claude to manage Temps projects, (3) Add Temps tools to their AI assistant, (4) Enable AI-powered deployment management, (5) Connect Claude Desktop to Temps, (6) Use MCP to interact with Temps API. Triggers: "temps mcp", "configure temps tools", "add temps to claude", "temps ai assistant", "mcp server setup".
$ install --global
skillsauthnpx skillsauth add gotempsh/temps temps-mcp-setupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 5, 2026, 1:59 PM11.0s1 file scanned
SKILL.md
- name:
- temps-mcp-setup
- description:
- |
- Configure the Temps MCP server to enable AI assistants to interact with the Temps platform. Provides tools for listing projects, viewing project details, and managing deployments directly from Claude or other MCP-compatible clients. Use when the user wants to:
- (1) Set up Temps MCP server, (2) Configure Claude to manage Temps projects, (3) Add Temps tools to their AI assistant, (4) Enable AI-powered deployment management, (5) Connect Claude Desktop to Temps, (6) Use MCP to interact with Temps API. Triggers: "temps mcp", "configure temps tools", "add temps to claude", "temps ai assistant", "mcp server setup".
Temps MCP Setup
Configure the Temps MCP server to manage projects and deployments from AI assistants.
Installation
Option 1: npx (Recommended)
No installation needed - runs directly:
{
"mcpServers": {
"temps": {
"command": "npx",
"args": ["-y", "@temps-sdk/mcp"],
"env": {
"TEMPS_API_URL": "https://your-temps-instance.com",
"TEMPS_API_KEY": "your-api-key"
}
}
}
}
Option 2: Global Install
npm install -g @temps-sdk/mcp
Configuration by Client
Claude Desktop (macOS)
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"temps": {
"command": "npx",
"args": ["-y", "@temps-sdk/mcp"],
"env": {
"TEMPS_API_URL": "https://your-temps-instance.com",
"TEMPS_API_KEY": "your-api-key"
}
}
}
}
Claude Desktop (Windows)
Edit %APPDATA%\Claude\claude_desktop_config.json:
{
"mcpServers": {
"temps": {
"command": "npx",
"args": ["-y", "@temps-sdk/mcp"],
"env": {
"TEMPS_API_URL": "https://your-temps-instance.com",
"TEMPS_API_KEY": "your-api-key"
}
}
}
}
Claude Code (VS Code)
Add to .vscode/settings.json or user settings:
{
"claude.mcpServers": {
"temps": {
"command": "npx",
"args": ["-y", "@temps-sdk/mcp"],
"env": {
"TEMPS_API_URL": "https://your-temps-instance.com",
"TEMPS_API_KEY": "your-api-key"
}
}
}
}
Environment Variables
| Variable | Required | Description |
|----------|----------|-------------|
| TEMPS_API_URL | Yes | Your Temps instance URL |
| TEMPS_API_KEY | Yes | API key from Temps dashboard |
Getting Your API Key
- Log into your Temps dashboard
- Navigate to Settings > API Keys
- Create a new API key with appropriate permissions
- Copy the key (it's only shown once)
Available Tools
Once configured, these tools become available:
list_projects
List all projects in your Temps instance.
Parameters:
- page (optional): Page number, default 1
- page_size (optional): Items per page, default 20, max 100
get_project
Get details of a specific project.
Parameters:
- project_id (required): The project ID
list_deployments
List deployments for a project.
Parameters:
- project_id (required): The project ID
- page (optional): Page number, default 1
- page_size (optional): Items per page, default 20, max 100
Available Prompts
add_react_analytics
Guided setup for adding Temps analytics to React applications.
Arguments:
- framework (required): nextjs-app, nextjs-pages, vite, cra, remix
- project_id (optional): Your Temps project ID
Verification
After configuration, restart your client and verify:
- Ask: "List my Temps projects"
- The assistant should use
list_projectstool - You should see your projects listed
Troubleshooting
Tools not appearing?
- Restart your MCP client completely
- Verify JSON syntax is valid
- Check that npx is in your PATH
Connection errors?
- Verify TEMPS_API_URL is accessible
- Check API key has correct permissions
- Try accessing the URL in a browser
Permission denied?
- Ensure API key has read permissions for projects
- Check API key hasn't expired
Related Skills
gotempsh/temps-plugin
tools
VerifiedTrustedCommunity
Build external plugins for the Temps deployment platform. Use when the user wants to create, modify, or debug a Temps plugin binary — a standalone Rust process that communicates with Temps over a Unix domain socket. Also use when the user mentions "temps plugin", "external plugin", "plugin binary", "plugin for temps", "plugin UI", or asks about plugin architecture, plugin events, plugin manifest, or plugin SDK. Covers the full lifecycle: project scaffolding, manifest, router, events, SQLite persistence, embedded React UI, build.rs, testing, and deployment into the plugins directory.
381SKILL.mdUpdated Apr 5, 2026
gotempsh/temps-platform-setup
tools
VerifiedTrustedCommunity
Install, configure, and manage the Temps deployment platform and CLI. Covers self-hosted Temps installation, CLI setup (bunx @temps-sdk/cli), initial configuration, user management, and platform administration. Use when the user wants to: (1) Install Temps on their server, (2) Set up the Temps CLI, (3) Configure Temps for the first time, (4) Manage Temps platform settings, (5) Create admin users, (6) Configure DNS providers, (7) Set up TLS certificates. Triggers: "install temps", "setup temps", "temps cli", "configure temps", "temps platform", "self-hosted deployment platform".
381SKILL.mdUpdated Apr 5, 2026
gotempsh/temps-cli
tools
VerifiedTrustedCommunity
Complete command-line reference for managing the Temps deployment platform. Covers all 54+ CLI commands including projects, deployments, environments, services, domains, monitoring, backups, security scanning, error tracking, and platform administration. Use when the user wants to: (1) Find CLI command syntax, (2) Manage projects and deployments via CLI, (3) Configure services and infrastructure, (4) Set up monitoring and logging, (5) Automate deployments with CI/CD, (6) Manage domains and DNS, (7) Configure notifications and webhooks. Triggers: "temps cli", "temps command", "how to use temps", "@temps-sdk/cli", "bunx temps", "npx temps", "temps deploy", "temps projects", "temps services".
381SKILL.mdUpdated Apr 5, 2026
gotempsh/deploy-to-temps
development
VerifiedTrustedCommunity
Deploy applications to the Temps platform with automatic framework detection, Dockerfile generation, and container orchestration. Supports Next.js, Vite, React, Node.js, Python, Go, Rust, Java, and C# applications. Use when the user wants to: (1) Deploy their app to Temps, (2) Set up CI/CD with Temps, (3) Configure deployment settings, (4) Create a Dockerfile for Temps, (5) Deploy a containerized application, (6) Set up automatic deployments from Git. Triggers: "deploy to temps", "temps deployment", "push to temps", "containerize for temps", "temps ci/cd".
381SKILL.mdUpdated Apr 5, 2026