MCP Client - amitsri/rostyman-releases GitHub Wiki

MCP Client

Rostyman can connect to external MCP servers, letting you access tools and data from services like GitHub, PostgreSQL, Slack, and any other MCP-compatible server — all from within Rostyman's interface.

Opening the MCP Panel

  1. Click the MCP tab in the right panel (or press Ctrl+J to toggle the right panel)
  2. The MCP tab has three sections: Overview, Servers, and Logs

Adding an MCP Server

Click Add Server in the Servers section to connect a new server. There are two transport modes:

Command Mode (stdio)

Use this for MCP servers that run as local processes. Rostyman launches the server command and communicates with it directly.

  • Name: A label for this server (e.g., "GitHub")
  • Command: The executable to run (e.g., npx)
  • Arguments: Command-line arguments (e.g., -y @modelcontextprotocol/server-github)
  • Environment Variables: Key-value pairs passed to the server process (for API keys, tokens, etc.)

URL Mode (HTTP)

Use this for MCP servers running on a remote machine or as a hosted service.

  • Name: A label for this server
  • URL: The server's SSE endpoint (e.g., http://localhost:3100/sse)
  • Bearer Token: Optional authentication token for secured servers

Example: Adding the GitHub MCP Server

  1. Click Add Server
  2. Select Command transport
  3. Fill in:
    • Name: GitHub
    • Command: npx
    • Arguments: -y @modelcontextprotocol/server-github
    • Environment Variables: Add GITHUB_PERSONAL_ACCESS_TOKEN with your GitHub personal access token
  4. Click Save
  5. Rostyman launches the server and shows a green Connected status

You now have access to GitHub tools — create issues, search repositories, read files, and more — directly from Rostyman's AI Assistant.

Example: Adding a PostgreSQL MCP Server

  1. Click Add Server
  2. Select Command transport
  3. Fill in:
    • Name: PostgreSQL
    • Command: npx
    • Arguments: -y @modelcontextprotocol/server-postgres postgresql://user:password@localhost:5432/mydb
  4. Click Save

Once connected, you can query your database, inspect schemas, and run SQL — all through AI-assisted conversations.

Environment Variables and Security

When a server requires API keys or tokens:

  • Add them as Environment Variables in the server configuration
  • Sensitive values are stored encrypted on your machine
  • Variables are only passed to the specific server process that needs them
  • They are never sent anywhere else or logged in plain text

Connection Status

Each server shows one of three states:

Status Meaning
Connected (green) Server is running and responding
Disconnected (grey) Server is stopped or not yet started
Error (red) Server failed to start or lost connection — check the logs for details

You can start, stop, or remove servers from the Servers list at any time.

Using Server Tools in the AI Assistant

Once an MCP server is connected, its tools become available in the AI Assistant:

  1. Open the AI Assistant panel
  2. Ask a question that requires the connected server's tools (e.g., "List my GitHub repos" or "Show tables in my database")
  3. The AI Assistant automatically selects and calls the appropriate MCP tools
  4. Results appear in the conversation

MCP Logs

The Logs section helps you monitor and debug MCP activity:

  • All MCP communication is logged — requests sent, responses received, errors encountered
  • Search across logs to find specific tools, servers, or error messages
  • Verbose mode toggle shows full request/response payloads for debugging
  • Logs are written to date-based log files that rotate automatically

Log File Location

Platform Path
Windows %APPDATA%\rostyman\logs\mcp\
macOS ~/Library/Application Support/rostyman/logs/mcp/
Linux ~/.config/rostyman/logs/mcp/

Log files are named by date (e.g., 2026-04-01.log) so you can easily find logs from a specific day.

Tips

  • You can connect multiple MCP servers at the same time — each server's tools are available independently
  • If a server fails to connect, check that the command is installed and accessible in your PATH
  • For HTTP servers that require authentication, use the Bearer Token field
  • MCP servers run locally on your machine — your data stays private
  • Restart a server by clicking Stop then Start if it becomes unresponsive