MCP-Server-Agent
Click on "Deploy 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., "@MCP-Server-Agentrestart the backend service and then show me its live status"
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.
My Agent Platform
The dashboard and MCP service for My Agent Platform.
MCP server
The server exposes nine Zod-validated tools over STDIO and Streamable HTTP:
npm run mcpUse the Inspector during local development:
npm run mcp:inspectRemote clients use POST /api/mcp. VS Code can load the STDIO server from .vscode/mcp.json.
Related MCP server: Secure Host MCP
Dashboard and management API
Run the dashboard with:
npm run devOpen /dashboard/mcp for live status, read-only redacted logs, and the approved start, stop, and restart controls. The dashboard receives status changes using server-sent events.
Open /dashboard/terminal for an interactive, admin-only terminal backed by the MCP terminal_execute tool. Every command is authenticated (session, admin role), CSRF-checked, classified into a SAFE / REQUIRES_CONFIRMATION / ADMIN_ONLY / DENIED tier (src/lib/terminal/command-policy.ts), and then run through the same MCP security gateway pipeline used by STDIO/HTTP MCP clients (POST /api/terminal/execute). The tool itself stays disabled until an administrator sets MCP_TERMINAL_ENABLED=true.
Set MCP_MANAGEMENT_TOKEN in every production environment. Management API callers must provide it as a Bearer token. State-changing requests must also send x-mcp-csrf: 1 and a same-origin Origin:
curl -X POST http://localhost:3000/api/mcp/restart \
-H "Authorization: Bearer $MCP_MANAGEMENT_TOKEN" \
-H "x-mcp-csrf: 1"On localhost, controls use a local-only development bootstrap; production requests without a configured token are rejected. The process manager starts only the repository's fixed tsx apps/mcp/src/index.ts command and redacts secrets from emitted logs.
MCP-Server-Agent
This server cannot be deployed
Maintenance
Related MCP Connectors
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Run commands and read/write files on your servers over Termalin's keyless tunnels (hosted MCP).
Official Sevalla MCP — full PaaS API access through just 2 tools.
Remote MCP server exposing 330 production AI-agent services for web/data processing, validation, AI utilities, blockchain/crypto utilities, and x402 pay-per-use access.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceTerminal-first SSH access for MCP clients and AI agents, enabling interactive remote sessions, file uploads, and stateful workflows.6 npm1MIT
- AlicenseNot gradedqualityAmaintenanceExposes a Windows or Linux host terminal to remote MCP clients via Streamable HTTP, enabling command execution, tunnel management, and privileged operations with security features like OAuth and audit logging.36 npm2MIT
- FlicenseNot gradedqualityCmaintenanceEnables agents to connect to remote MCP servers once, access their tools through a compact MCP endpoint, pair a CLI inside sandboxes, and create watches that turn command or tool output into pollable structured events.2-
- AlicenseNot gradedqualityBmaintenanceEnables agent clients to safely connect to tools and execution resources through MCP with authorization, approvals, audit, chat-context isolation, SSH/Docker access, and long-running command session tracking.MIT